Hi @hesreallyhim — saw the "update in progress" header on the README and figured an issue is the right route until the new TOC lands. When you're ready to take additions, here's one for the security-/tooling-adjacent section:
SkilLock — pin approved Claude Code skill behavior; flag drift in PR review.
One-line description (drop into the new format when ready):
[SkilLock](https://github.com/skills-lock/skil-lock) — Pins approved Claude Code skill behavior into a committed skills.lock and runs a capability-delta PR review on drift. SARIF output for the Security tab; supports both Claude Code and Codex SKILL.md formats.
The wedge versus other "skills lockfile" projects (Vercel skills-lock.json, pcomans/skills-lock, etc.) is that we pin behavior (observed shell / network / file surface) rather than content hash — adding a new curl to a skill triggers review, even if the file hash matches a prior approved version.
Closing this issue is the expected outcome when the new TOC lands and it's been added (or you decide to skip). Thanks for maintaining the list.
Hi @hesreallyhim — saw the "update in progress" header on the README and figured an issue is the right route until the new TOC lands. When you're ready to take additions, here's one for the security-/tooling-adjacent section:
SkilLock — pin approved Claude Code skill behavior; flag drift in PR review.
One-line description (drop into the new format when ready):
The wedge versus other "skills lockfile" projects (Vercel
skills-lock.json,pcomans/skills-lock, etc.) is that we pin behavior (observed shell / network / file surface) rather than content hash — adding a newcurlto a skill triggers review, even if the file hash matches a prior approved version.Closing this issue is the expected outcome when the new TOC lands and it's been added (or you decide to skip). Thanks for maintaining the list.