Agent skill · duc01226
project-skill-protocol
[Utilities] Use when a project needs to add, change, list, or remove its OWN protocol rules layered on top of a framework skill — a named overlay of extra project rules that applies whenever the targeted skill runs, stored with the project rather than in the portable framework. `/project-skill-protocol list` prints every overlay with its target and description; `add` drafts a new overlay and confirms it before writing; `update` applies a surgical change; `delete` removes it. Overlays are ADDITIVE ONLY — they never replace, override, or waive anything the skill already does. Triggers: skill protocol, project protocol, custom protocol for skill, extend a skill, overlay rules, add rules to a skill, project rules for skills, skill protocol overlay.
What it needs
About 11k tokens when loaded.
What this skill does
Quick Summary Goal: Give a project a registry of named protocol overlays — extra project rules layered onto framework skills — with create / read / update / delete over that registry, so a skill picks up this project's conventions on every run without the portable framework being edited. Summary: read-this-if-nothing-else digest — Two files, two jobs. The INDEX (docs/project-reference/skill-protocols-reference.md) holds target + scope + name + description and is what resolution reads. The BODY (docs/project-protocols/<slug>.md) holds the actual rules and is read only for a MATCHED target. Never bulk-read bodies. ADDITIVE ONLY — the rule that governs every other rule. An overlay ADDS rules on top of a skill's protocol; it never replaces, overrides, disables, or reinterprets one. Invariant: removing every overlay returns each skill to exactly its documented behavior. Resolution is specificity-based, not order-based. exact > glob > , winner tier takes all — and that ordering ranks overlays against EACH OTHER, never against the skill. Project payload, not framework. Overlays live under docs/, never .claude/. A rule that stabilizes and generalizes gets PROMOTED to a real skill via /skill-creator. ADD authors the best version, then confirms it. The user's raw wording is raw material, NEVER the artifact. Infer intent, generalize past the incident, draft the body, then run the rules through /prompt-enhance and the prompt-engineering rubric (imperative · observable · decidable · one rule per line · carries its WHY) — an overlay is an AI instruction that fires unattended, so a vague rule is a nondeterministic one. Show what changed and why, and always offer "save my wording verbatim". Three writes, one turn — then the mirror. Body + index row + the CLAUDE.md CK:PROJECT-PROTOCOLS block, then AUTO-RUN the Codex mirror sync (node .claude/skills/sync-codex/scripts/run-codex-sync.mjs) so AGENTS.md never lags behind the block. Report the sync's real outcome. Never commit. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills duc01226/project-skill-protocol--186f41