AB prompt-library-builder
Build a personal library of reusable prompts for the things you ask AI again and again — so you stop rewriting the same request from scratch. Use when asked help me build a prompt library, save my best prompts, I keep writing the same prompts, or organize my AI prompts. Produces a captured set of your recurring AI tasks turned into reusable, parameterized prompt templates, an organization scheme so you can find them, guidance on what makes a prompt reusable (clear role, inputs, output format), and how to store and improve them — turning ad-hoc prompting into a personal toolkit that compounds.
Build a personal library of reusable prompts for the things you ask AI again and again — so you stop rewriting the same request from scratch.
As a process B 70/100 · Nearly there — weak spots: when it triggers, failures and branches, progress reporting
How to improve
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 70/100
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Tools and files. No external tools needed
- 100Steps. 32 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1058 tokens
- 100Running it twice. No mutating operations
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)
- +1No license
- +2Single-language instructions
- +3Description length 599: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 32 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.