Agent skill · Audited from source
Close Issue
skill · desplega-ai/agent-swarmMIT licenceAudited 14 Oct 2026 · source 4df377778267
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: Close a GitHub or GitLab issue with a summary comment
Cite
Cite this page
ModelsAtlas. “Close Issue (desplega-ai/agent-swarm)”. Retrieved 14 Oct 2026. https://modelsatlas.com/skills/desplega-ai/close-issue
Trust audit
Audit 0.4.1 · source read 14 Oct 2026
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
| Layer | What we check | Result | Findings |
|---|---|---|---|
L0 Provenance | Repo owner, licence, archive status, activity | WARN | 5 |
L1 Static source | Secrets, path traversal, supply chain, hidden code | NA | 0 |
L2 Instructions | Prompt injection, authority framing, hidden directives | PASS | 0 |
L3 Inventory | The files and declarations match the source | PASS | 0 |
L4 Sandbox | Run in isolation and watch behaviour | SKIPPED why | 0 |
Gates applied: no behavioural pass.
Findings (5)
MEDIUMInventory / provenanceinv.symlink · .agents/skills/dashboard-ui
.agents/skills/dashboard-ui
- Why
- link not followed
- Fix
- —
MEDIUMInventory / provenanceinv.symlink · .agents/skills/swarm-local-e2e
.agents/skills/swarm-local-e2e
- Why
- link not followed
- Fix
- —
MEDIUMInventory / provenanceinv.symlink · .claude/skills/dashboard-ui
.claude/skills/dashboard-ui
- Why
- link not followed
- Fix
- —
MEDIUMInventory / provenanceinv.symlink · .claude/skills/swarm-local-e2e
.claude/skills/swarm-local-e2e
- Why
- link not followed
- Fix
- —
LOWInventory / provenanceinv.symlink · AGENTS.md
AGENTS.md
- Why
- link not followed
- Fix
- —
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/close-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: Close a GitHub or GitLab issue with a summary comment
--- name: close-issue description: Close a GitHub or GitLab issue with a summary comment --- # Close Issue Close a GitHub or GitLab issue with an appropriate closing comment summarizing the resolution. **Provider detection:** Check the URL or remote to determine the VCS provider: - If GitHub → use `gh issue close` / `gh issue comment` - If GitLab → use `glab issue close` / `glab issue note` ## Arguments - `issue-number-or-url`: Either an issue number (e.g., `123`) or a full issue URL ## Workflow 1. **Parse the input** — if given a URL, extract owner, repo, and issue number. If just a number, use the current repo context. 2. **Ensure repo is cloned** to `/workspace/personal/<repo-name>` (clone with `gh repo clone` if needed). 3. **Get issue details** — read the issue title, body, comments, and check for related PRs. 4. **Generate closing comment** — summarize what was done, reference related PRs/commits, note any follow-ups. 5. **Post comment and close:** ```bash gh issue close <issue-number> --comment "Your closing comment" --reason completed ``` ## Closing Reasons - `completed` — The issue was resolved - `not_planned` — Won't fix / out of scope / duplicate ## Tips - Always explain why the issue is being closed - Reference specific PRs or commits when applicable - If closing as "not planned", explain the reasoning
Excerpt, first 1,355 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
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
- !CAUTION B 89 / 100
first audit · source
4df377778267
Similar skills
All automation skills →desplega-ai/agent-swarm
Create a pull request (GitHub) or merge request (GitLab) from the current branch
desplega-ai/agent-swarm
Implement a GitHub issue or GitLab issue and create a PR/MR
desplega-ai/agent-swarm
Investigate and triage a Sentry error issue
desplega-ai/agent-swarm
Respond to a GitHub issue/PR or GitLab issue/MR
desplega-ai/agent-swarm
Review a pull request (GitHub) or merge request (GitLab) and provide detailed feedback
desplega-ai/agent-swarm
Start the Agent Swarm Leader
Questions about Close Issue
What does the Close Issue skill do?
Is Close Issue safe to install?
What can Close Issue access on my machine?
How current is this page?
Sources
- github.com/desplega-ai/agent-swarm/tree/main/plugin/pi-skills/cl — the audited source at commit 4df377778267 and every finding aboveObserved · 14 Oct 2026
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.
- What does the Close Issue skill do?
- Is Close Issue safe to install?
- What can Close Issue access on my machine?