Install
$ agentstack add skill-bcgen-skills-skill-auditing ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Skill Auditing
Find what has gone stale in a set of skills — on two independent layers, reported separately so the user knows which findings are format and which are facts.
Step 1 — Pick the target
Default to the current project's installed skills (.claude/skills/, .agents/skills/, or the repo's skills/). Accept any directory path the user names, including a collection repo's own skills/.
Step 2 — Format layer (offline)
For each skill, check against the authoring conventions in [skill-writing's references/conventions.md](../skill-writing/references/conventions.md) when available (the single source of truth), else the same rules inline: frontmatter shape and name == directory; description is a capability sentence + "Use when ..." ≤1024 chars; body ≤100 lines with detail in references/; references links resolve; English only. Report each violation with file and line.
Step 3 — Content layer (live)
Extract the concrete factual claims a skill makes — commands, flags, API calls, config keys, file paths, version numbers — and verify each against current official documentation (web search / doc fetch; for library docs prefer the docs tooling). Classify each:
- confirmed — matches current docs.
- outdated — current docs contradict it; cite the doc as the source.
- unverifiable — cannot confirm or deny from available sources; say so,
never guess.
Step 4 — Report and route fixes
Two sections, format then content. Each finding: the skill, the location, the severity, and the evidence or source. Then, for approved fixes, route to the skill-writing skill when installed; if it is not installed, print the exact proposed edit for manual use and mention the install option at most once.
Principles
| Principle | Meaning | | --- | --- | | Two layers, never merged | Format (offline, convention) and content (live, factual) are reported separately. | | Cite sources | Every "outdated" finding names the doc that contradicts the skill. | | Honesty over coverage | What can't be verified is listed as unverifiable, not guessed. | | Diagnose, don't mutate | The audit reports and proposes; skill-writing performs the edits. |
The repo's own CI lint stays the enforcement gate; skill-auditing is the user-facing, any-directory diagnostic that also checks content facts CI cannot.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: BCGen
- Source: BCGen/skills
- License: MIT
- Homepage: https://skills.sh/BCGen/skills
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.