BC agentsop-conventions-pinning
SOP for writing, loading, and evolving a project-level convention file (CONVENTIONS.md / CLAUDE.md / .cursor/rules / .clinerules / AGENTS.md) so that a coder-agent reliably respects your codebase's style choices every session. Tool-agnostic; covers the four load mechanics (read-only attachment, ancestor-walk auto-load, glob-scoped rules, agent backstory) and the conflict resolution between pinned conventions and the existing code.
SOP for writing, loading, and evolving a project-level convention file (CONVENTIONS.md / CLAUDE.md / .cursor/rules / .clinerules / AGENTS.md) so that a…
As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, execution cost
How to improve
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 8565 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "domain" - note
frontmatter-keyunknown frontmatter key "audience" - note
frontmatter-keyunknown frontmatter key "trigger_keywords" - note
frontmatter-keyunknown frontmatter key "when_not_to_use" - note
edit-residuethe text marks something as outdated (lines 174, 279, 372, 388): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 52/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Execution cost. Instruction body is 8565 tokens: crowds the task out of the window
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, write, python, node) that frontmatter does not declare
- 60Failures and branches. 2 branches
- 100Steps. 76 steps
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- -4Absolute local paths (C:\Users, /home/…): not portable
- -42 reference files, but SKILL.md never points to them: the model will not open them
- +1No license
- +2Single-language instructions
- +3Description length 434: enough signal without eating the budget
- +4Structure: 41 headings
- +3Step-by-step instructions: 76 items
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.