Install
$ agentstack add skill-dwarvesf-dwarves-kit-skill-review ✓ 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-review (the promote gate)
skill-curator's background reviewer stages skill drafts under ~/.claude/skill-proposals/. It NEVER writes ~/.claude/skills/. This skill is the human gate that promotes a vetted draft into the live library. bin/skill-review (from lib/skill-curator/, put it on PATH or invoke by its full path) is the only writer of ~/.claude/skills/.
Flow
- List the staged drafts:
``bash skill-review list # tab-separated: \t `` If "(no staged drafts)", stop and say so.
- For each draft, read
~/.claude/skill-proposals//SKILL.mdand vet it. **Run the
superpowers:writing-skills checklist** (this skill does NOT reimplement it , delegate):
- Is the name class-level (not a PR number, error string, codename, or today-only artifact)?
- Is the
descriptiona real trigger (what class of task + when), so a future agent matches it? - Is it a genuine reusable pattern, or environment-dependent / a complaint that will rot into a
refusal? Drop the latter.
- Secret scan: confirm no token / key / credential is in the body.
promotealso refuses a
draft that still contains one, but check first.
- Would this be better as a PATCH to an existing umbrella, or a
references/add, than a new
skill? If so, reject and patch by hand.
- Decide per draft (always show the user the draft and your read before acting):
- Approve ->
skill-review promote(moves it into~/.claude/skills//; refuses to
overwrite a live skill without --force).
- Reject ->
skill-review reject(moves it to_rejected/, recoverable, never deleted).
- Report what was promoted vs rejected, and any draft you left staged for the user to decide.
Rules
- Never promote a draft you have not read and vetted against writing-skills.
- Never
--forceoverwrite a live skill without explicitly confirming with the user first. - Promotion is the ONLY path a draft enters
~/.claude/skills/. The reviewer cannot (it runs with
no write tool). Keep it that way.
- An optional
auto_promoteconfig knob (default OFF) can auto-pass the lowest-risk class only
(a references/ add to an existing umbrella) via skill-review auto; everything else is manual.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: dwarvesf
- Source: dwarvesf/dwarves-kit
- License: MIT
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.