capability-audit
SolidUse when evaluating, comparing, installing, or recommending a Claude Code plugin, Agent Skill, MCP server, agent toolkit, or GitHub-hosted AI extension, especially when popularity is weak evidence or the candidate requests shell, network, filesystem, or credential access.
Install
Quality Score: 82/100
Skill Content
Details
- Author
- Rtur2003
- Repository
- Rtur2003/Claude-Code-Promts-Skills
- Created
- 8 months ago
- Last Updated
- 4 days ago
- Language
- Python
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
capability-auditor
Audit capability artifacts for static safety, evidence coverage, duplication, context cost, prompt contracts, dependencies, and install risk. Use capability-evaluation for behavioral baselines and portfolio architect for structural change.
repo-audit
Security audit of any third-party repo, package, skill, plugin, or MCP server BEFORE it is installed or executed. Use this skill whenever the user asks "is this safe?", "audit/vet/check this repo", "should I install X", pastes a GitHub/npm/PyPI/marketplace link with intent to install, or whenever you yourself are about to recommend or install third-party code, even if nobody says the word "audit". Covers maintainer reputation, typosquatting, install-time hooks, obfuscation, exfiltration and secrets-harvesting patterns, dependency and CI risks, and prompt injection in agent-facing files (skills, agent configs, MCP tool descriptions). Produces a SAFE / SAFE-WITH-CONDITIONS / UNSAFE verdict with evidence, transparent red flags, and conditions such as version pinning.
skill-security-audit
Audit installed Claude Code skills for prompt-injection and supply-chain risk, and report which are safe and which are not. Use when the user asks to check, audit, review, or vet their skills/plugins for security, prompt injection, hidden instructions, or malicious content — e.g. "are my skills safe", "scan my skills", "which skills can be trusted".