Agent skill · Audited from source

Implement Issue

skill · desplega-ai/agent-swarmMIT licenceAudited 14 Oct 2026 · source 4df377778267

★ 882pushed today
!CAUTIONGrade B · 89/100 · 5 findings · 4df3777
882repo stars · whole desplega-ai/agent-swarm

Is it safe? With care — CAUTION, grade B (89/100). We read this skill's source at commit 4df377778267 and found no filesystem, network or shell access and no hard-coded secrets. The audit raised 5 findings, 0 critical or high. What it does: Implement a GitHub issue or GitLab issue and create a PR/MR

Ask an AI about this pageGChatGPTCClaudePPerplexityGeGeminiXGrok
More
Cite

Cite this page

ModelsAtlas. “Implement Issue (desplega-ai/agent-swarm)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/desplega-ai/implement-issue

Trust audit

Audit 0.4.1 · source read 14 Oct 2026

Trust score89/100!CAUTION B
0 critical0 high4 medium1 low0 info

CAUTION means the audit found things worth knowing before you trust this skill. Grade B is shared by 13,985 of 14,816 audited skills.

What the source does

  • FilesystemNone observedNo reads or writes in the source
  • NetworkNone observedNo outbound calls in the source
  • ShellNone observedNo commands run in the source
  • DependenciesPinnedNothing floats
  • SecretsNone foundNo keys in source

Five audit layers

LayerWhat we checkResultFindings
L0 ProvenanceRepo owner, licence, archive status, activityWARN5
L1 Static sourceSecrets, path traversal, supply chain, hidden codeNA0
L2 InstructionsPrompt injection, authority framing, hidden directivesPASS0
L3 InventoryThe files and declarations match the sourcePASS0
L4 SandboxRun in isolation and watch behaviourSKIPPED why0

Gates applied: no behavioural pass.

Findings (5)

Audit 0.4.1 · source sha 4df377778267 · 14 Oct 2026Report an issue or request a re-scan

Provenance

Who published it, and what the verdict is pinned to

  • Publisherdesplega-ai GitHub organizationOwner of the repository this skill is read from
  • Source folderdesplega-ai/agent-swarm/plugin/pi-skills/implement-issueThe exact folder we audited
  • LicenceMITAs the repository states it
  • Commit pinned for this verdict4df377778267A new audit runs when the source changes
  • Repository statusNot archivedPushed today
  • Sandboxed runNot runSkills are read, not executed; layer L4 is skipped

What it tells the agent

Full source on GitHub ↗

Its description: Implement a GitHub issue or GitLab issue and create a PR/MR

---
name: implement-issue
description: Implement a GitHub issue or GitLab issue and create a PR/MR
---

# Implement Issue

Read a GitHub or GitLab issue, implement the requested changes, and create a PR/MR.

**Provider detection:** Check the URL or remote:
- If GitHub → use `gh issue view` / `gh pr create`
- If GitLab → use `glab issue view` / `glab mr create`

## Arguments

- `issue-number-or-url`: Either an issue number (e.g., `123`) or a full URL

## Workflow

### 1. Parse and Fetch

If given a URL, extract owner, repo, and issue number. Fetch issue details (title, body, labels, comments). Understand what's being requested, acceptance criteria, and any technical constraints.

### 2. Setup

- Ensure repo is cloned to `/workspace/personal/<repo-name>` (clone with `gh repo clone` if needed)
- Fetch origin, checkout main, pull latest
- Create a feature branch: `fix/issue-<number>-<short-description>`

### 3. Implement

1. **Understand the codebase** — explore relevant files and existing patterns
2. **Plan your approach** — consider using `/planning` for complex changes
3. **Write the code** — implement the requested functionality
4. **Test your changes** — run existing tests, add new tests if appropriate
5. **Verify it works** — manual verification where possible

Keep changes focused on what the issue requests. Avoid scope creep.

### 4. Quality Checks, Commit, and Push

1. **Run PR checks (MANDATORY)** — Run ALL checks from the "PR Checks" section of your Repository Guidelines. Fix any failures before proceeding. If no guidelines are defined, check the project's CLAUDE.md for a pre-PR checklist.
2. **Commit** with a message referencing the issue (e.g., `Fix #123: <description>`). Use conventional commit style if the repo uses it.
3. **Push** with `git push -u origin HEAD`.

### 5. Create the PR

Create the PR with a descriptive title and a body that follows the repository's PR template and conventions (see `/skill:create-pr`, steps 5 and 6). If the repo defines none, include: summary of changes, key changes list, and testing done. Always include `Fixes #<issue-number>` to auto-close the issue on merge.

After creating the PR, check CI status with `gh pr checks` (GitHub) or `glab mr view --json pipelines` (GitLab). If CI fails, fix the issues, push, and re-check until green.

### 6. Report Back

Provide the PR URL, summary of changes, and any caveats. Optionally comment on the original issue linking the PR.

## Tips

- Read the issue thoroughly before starting — misunderstanding wastes time
- Check for related issues or existing PRs
- One issue = one PR
- If the issue is too large, break it into smaller PRs
- If unclear, use `/skill:respond-github` to ask for clarification

Excerpt, first 2,721 characters of SKILL.md, verbatim from the audited commit. It is text from someone else’s repository, quoted so you can judge it before your agent reads it.

Install

Pinned to the audited commit 4df3777

Download folder ↗
git clone https://github.com/desplega-ai/agent-swarm
git -C agent-swarm checkout 4df377778267

The author documents no install command, so this uses the repository directly. Our verdict covers commit 4df377778267 only.

Works in

The author has not said which agents this skill supports, and we have not tested it in any.

Audit history

Every audit, every source change

  1. !CAUTION B 89 / 100

    first audit · source 4df377778267

Questions about Implement Issue

What does the Implement Issue skill do?
Your Company Agentic Operating System
Is Implement Issue safe to install?
With care. The audit graded it B (89/100) and found 5 things worth knowing before you trust this skill, listed below with the exact line each was found on.
What can Implement Issue access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (4df377778267), read on 2026-10-14. The repository is watched, and a new audit runs when it changes — this is the first audit.

Sources

Spotted something wrong? Report a correction · Methodology

Keep going in your AI

Opens with this page as the source. We add nothing else to the prompt.