A skill can be safe on the day you install it and silently different a
week later. SkillScan by
RakTikoo has a change watch for exactly that question:
--pin records a fingerprint of a scanned folder, and
--check-pin later re-scans and reports a plain diff of what
changed.
python3 -m skillscan <path-to-skill-folder> --pin pin.json
The pin records a hash of every entry in the folder, the verdict, the findings, and the rule-set version. A real run looks like this:
Pinned 3 entries from .../my-skill (verdict PASS) -> pin.json
The fingerprint covers every entry — regular files of every
type (not only the ones the scanner reads, because a change can arrive as
a file the scanner does not parse), directories, special files, the
permission bits on files, and symlinks. Nothing is skipped, not even
.git or __pycache__.
Keep the pin outside the folder it fingerprints: a pin inside
it can be rewritten by the same hand that changed the folder, and
--pin warns when asked to write one there.
python3 -m skillscan <path-to-skill-folder> --check-pin pin.json
If nothing changed, the answer is one line and exit code 0:
No changes: every entry in the folder is identical to the pin (pin.json), and the scan result is the same (verdict PASS).
If files changed but the scan result did not, the changed entries are named and the exit code is 1:
Files changed on disk — same scan result (verdict and findings identical).
Added files (1):
+ notes.txt
Findings are compared by what they say, not by line number: inserting a comment above a flagged line is a files-changed (1), not a scan-result change.
| Exit code | Meaning |
|---|---|
| 0 | No entry changed. (A rule-set version difference alone is reported, not failed — the scanner changed, not the skill.) |
| 1 | Files changed, but the scan result (verdict + findings) is identical. |
| 2 | The scan result changed — review before trusting this skill again. |
| 3 | The pin cannot be used. |
New to SkillScan? Start with How to check if an agent skill is safe before installing.