BB dev-guardrails
Universal AI agent development guardrails with five defense layers: instruction gate, project monitoring, delivery reliability, code quality audit, and scope fidelity enforcement. Prevents blind compliance, hallucination, scope creep, unrealistic promises, code quality degradation, and over-engineering. Designed for Claude Code, Codex, Gemini CLI, and any AI coding agent.
Universal AI agent development guardrails with five defense layers: instruction gate, project monitoring, delivery reliability, code quality audit, and scope…
As a process B 71/100 · Nearly there — 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: 7. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 10556 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "agent_created" - note
edit-residuethe text marks something as outdated (lines 753, 754, 864): check that old rules are not kept next to new ones — the full check reads the text for contradictions
Process rating: all ten parameters 71/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 40Execution cost. Instruction body is 10556 tokens: crowds the task out of the window
- 100Tools and files. No external tools needed
- 100Steps. 108 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
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
- +1No license
- +2Single-language instructions
- +3Description length 374: enough signal without eating the budget
- +4Structure: 57 headings
- +3Step-by-step instructions: 108 items
- +4Has examples (26 code blocks)
- +4Reference files are cited in the instructions (3 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 72.