BC Prompt Version Control
Git-like version control for AI prompts: track changes, A/B test variants, measure metrics, rollback with confidence.
Git-like version control for AI prompts: track changes, A/B test variants, measure metrics, rollback with confidence.
As a process C 54/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, consistency
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
- 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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 3, column 14: description: Git-like version control for AI prompts: track changes, A/B test v… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "slug"
Process rating: all ten parameters 54/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 26 mutating operations with no state check
- 40Consistency. Frontmatter name (Prompt Version Control) differs from the folder (prompt-version-control)
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web, git) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 53 steps
- 100Execution cost. Instruction body is 3327 tokens
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (12 tags): a typed call is more reliable
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)
- +3Description length 117: 120–800 characters recommended
- +2Single-language instructions
- +4Structure: 31 headings
- +3Step-by-step instructions: 53 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
- +3All 1 scripts are documented
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 60.
External checks
ClawHub: suspicious
The skill is not malware, but its documentation overstates important evaluation and sync features in ways that could mislead users managing production prompts.
LLM: suspicious (medium) · VirusTotal: · 18 Jun 2026