Skill guardian
Audit local agent skill directories, explain current version provenance, compare known GitHub upstreams, score trust and update risk, and finish with a clear recommendation about whether any local skills should be updated now.From its SKILL.md
npx -y skills add Adenine-AGCT/skill-guardian --skill skill-guardianAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.4 KB, 449 tokens by cl100k_base, as published. Nobody here has run it
Skill Guardian Skill
Overview
Use this skill when the user wants a dedicated skill for auditing installed Agent Skills before making update decisions.
Skill Guardian is built for skill audit and update governance. It starts with a quick, low-overhead audit, checks provenance and local drift first, and only escalates to deeper update checks when the evidence justifies it.
This skill is advisory. It does not auto-update installed skills.
Workflow
Run the bundled wrapper:
python .\scripts\skill_guardian.py
Use offline mode when network access is unavailable:
python .\scripts\skill_guardian.py --offline
The wrapper performs:
- Multi-root discovery for local skill directories
- A quick local structural and behavior audit with baseline and drift detection
- Lightweight upstream metadata checks to estimate version gaps
- Escalation to deeper remote comparison only when risk, drift, or version gap signals justify it
- Trust scoring and update recommendation
- A final human-readable summary of what should or should not be updated
Output Contract
The final response should contain:
- how many local skills were found
- which roots were scanned
- which skills have recognized upstream provenance
- which skills show local drift
- which skills were escalated because of large version gaps
- which skills are already current
- which skills have updates available
- which updates need review or should be blocked
- whether the user should update anything now
Every per-skill summary should include:
source_typeversion_statusbaseline_statusversion_gap_leveltrust_scorerisk_levelupdate_recommendationconfidence_explainer
Safety Rules
- Never auto-update a skill
- Never execute remote scripts while inspecting them
- Prefer the quick audit path unless the evidence clearly justifies a deeper check
- Treat changes under
scripts/or executable file additions as review-heavy - Treat unknown-source skills as auditable but not strongly version-resolvable
- If remote inspection fails, still complete the local audit and say that the remote version check was unavailable
What ships with it: 5 files
86.5 KB alongside SKILL.md, 2 of them executable
agents/
- openai.yaml418 B
assets/
- python/skill_guardian_runtime.pyruns83.0 KB
references/
- default-upstreams.json887 B
- scoring.md434 B
scripts/
- skill_guardian.pyruns1.8 KB