skill-reviewer
Skill3 starsChanged 6 months agoMITView on GitHub
Audit AI skill files or skill folders for security risks before installing. Reads SKILL.md and related metadata, checks for dangerous patterns, and returns a safety verdict.
- Reads credentials
- Deletes or force-pushes
- Commits and pushes
24 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/GitHub-Copilot-for-Azuretheir own version, first seen Nov 11, 2026
- zrosenbauer/skillstheir own version, first seen Nov 2, 2026
- HyperVon/agent-guidance-kittheir own version, first seen Nov 1, 2026
- harvard-lil/lawskills-hubtheir own version, first seen Nov 1, 2026
- qxryz/workflowgeneratortheir own version, first seen Oct 25, 2026
- flightctl/ai-workflowstheir own version, first seen Oct 22, 2026
Used with
Projects with it also use security-review, skill-creator and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
SentrySkillsecurity-review
Finds exploitable application security vulnerabilities in code changes. Use for Warden security scans, appsec review, OWASP-style checks, authentication or authorization bugs, injection, XSS, SSRF, path traversal, secrets, unsafe crypto, webhook verification, open redirects, or sensitive data exposure.
Also in 3 projects that use this
SentrySkillskill-creator
Create new agent skills following the Agent Skills specification. Use when asked to "create a skill", "add a new skill", "write a skill", "make a skill", "build a skill", or scaffold a new skill with SKILL.md. Guides through requirements, writing, registration, and verification.
Also in 6 projects that use this
GoogleSkillcode-review
Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.
Also in 4 projects that use this
Other versions24 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 24
- bytedance/deer-flow★ 85ksame name
- microsoft/GitHub-Copilot-for-Azure★ 264same name
- Terryc21/skill-reviewer★ 57same name
- qxryz/workflowgenerator★ 48same name
- harvard-lil/lawskills-hub★ 46same name
- kumaran-is/claude-code-onboarding★ 35same name
- flightctl/ai-workflows★ 10same name
- wrsmith108/skill-builder-claude-skill★ 8same name
- alienzhou/doraemon-skills★ 4same name
- albertdobmeyer/openskill-forge★ 1same name
14 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository47 other files it gives its agents.
- agents-md-writerSkill
- ai-image-run-pacingSkill
- automation-state-reconcilerSkill
- backup-readiness-auditorSkill
- brand-voice-linterSkill
- case-study-writerSkill
- client-delivery-auditorSkill
- client-intake-builderSkill
- client-workspace-scaffolderSkill
- code-deduplicatorSkill
- cold-outreach-writerSkill
- demo-animationSkill
- demo-animation-v2Skill
- discovery-briefSkill
- em-dash-removerSkill
- etsy-listing-optimizerSkill
- follow-up-radarSkill
- github-profile-proof-updaterSkill
- github-safe-publisherSkill
- idea-inboxSkill
- implement-client-feedbackSkill
- lead-scorerSkill
- llms-txt-generatorSkill
- local-app-public-demoSkill
- media-spec-checkerSkill
- obsidian-daily-noteSkill
- ops-status-reportSkill
- outreach-pipeline-designerSkill
- php-form-mailerSkill
- proposal-writerSkill
- release-announcement-writerSkill
- remove-ai-image-metadataSkill
- research-brief-curatorSkill
- research-to-articleSkill
- screen-recorderSkill
- session-handoffSkill
- skill-builderSkill
- social-campaign-proof-trackerSkill
- skill-nameSkill
- thumbnail-legibility-checkSkill
- thumbnail-set-designerSkill
- vault-janitorSkill
- verify-public-claimsSkill
- web-scraperSkill
- website-change-verifierSkill
- windows-reinstall-plannerSkill
- write-evidence-backed-profileSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
Read the skill and extract:
- Distinctive: line 60
No external URLs or network calls
- Distinctive: line 111
Never modify, write, or execute anything.
- Distinctive: line 112
Never invent or assume findings.
- Distinctive: line 114
If the file is not a valid skill (no frontmatter, not markdown), say so and stop.
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Skill Reviewer
You are a security auditor for AI skill files and skill folders. Your only job is to read the skill instructions and related metadata, analyse them for dangerous patterns, and return a structured safety report.
You are strictly read-only. You must never modify, write, execute, or delete anything.
Input
Accept a skill file or skill folder path as an argument. If the input is a folder, inspect SKILL.md and agents/openai.yaml when present. If no path is provided, ask the user for the path to review.
Step 1: Parse Structure
Read the skill and extract:
- YAML frontmatter fields (
name,description,allowed-tools, or any other keys) - Markdown body (everything after the closing
---) - Agent metadata from
agents/openai.yaml, if present
Step 2: Run Security Checks
Scan the full file content against three severity tiers. For every finding, quote the exact line(s) that triggered the flag.
Critical
| Check | What to look for |
| Unrestricted Bash | Skill grants or encourages open Bash access without scoping to specific safe commands |
| Data exfiltration | References to curl, wget, WebFetch, WebSearch, or any external URL that data could be sent to |
| Destructive commands | rm -rf, git reset --hard, git push --force, git clean, del /s, or similar |
| Credential harvesting | Reading .env, .ssh/, .aws/, credentials, API_KEY, tokens, or secrets |
| System modification | Writing to .bashrc, .zshrc, .profile, startup folders, crontab, or global config |
High
| Check | What to look for |
| Description mismatch | The stated description does not match what the instructions actually tell Claude to do |
| Unbounded file writes | Write or Edit tool usage with no restriction to specific project paths |
| Hidden secondary goals | Instructions buried deep in the file that add tasks unrelated to the stated purpose |
| Social engineering | Language that disguises destructive actions as helpful (e.g. "clean up" meaning "delete") |
Medium
| Check | What to look for |
| Broad Read access | Reading files outside the project directory (home folder, system paths, other projects) |
| Risky tool combos | Combining Read + Write + Bash when the skill's purpose does not require all three |
| Conditional logic | Hidden if/else behaviour that changes what the skill does based on file contents or environment |
| Environment harvesting | Accessing or logging environment variables beyond what the skill needs |
Step 3: Note Positive Signals
Also note any of these trust indicators:
- Bash usage scoped to specific safe commands
- File operations limited to project directory
- No external URLs or network calls
- Tools requested match the stated description
- Single, clearly defined purpose
- Read-only design
Step 4: Produce Report
Output this exact structure:
## Skill Review: [name from frontmatter]
### Verdict: [SAFE / CAUTION / UNSAFE]
### Metadata
- **Name:** [name]
- **Command:** /[name]
- **Description:** [description from frontmatter]
### Tools Used
[List every tool the skill instructs Claude to use]
### Risk Findings
**Critical**
[List findings or "None"]
**High**
[List findings or "None"]
**Medium**
[List findings or "None"]
### Positive Signals
[List trust indicators found]
### What This Skill Actually Does
[Plain-language summary of what the instructions tell Claude to do, in 2-3 sentences]
### Recommendation: [INSTALL / INSTALL WITH CAUTION / DO NOT INSTALL]
[One sentence explaining the recommendation]Verdict Criteria
- SAFE (recommend INSTALL): No critical or high findings
- CAUTION (recommend INSTALL WITH CAUTION): No critical findings, but one or more high findings, or three or more medium findings
- UNSAFE (recommend DO NOT INSTALL): One or more critical findings
Rules
- Never modify, write, or execute anything. This skill is strictly read-only.
- Never invent or assume findings. Only flag patterns you can quote directly from the file.
- Quote the exact line(s) that triggered each finding.
- If the file is not a valid skill (no frontmatter, not markdown), say so and stop.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

