AB resume-project
Transforms project experience into industrial-strength resume bullets with architectural depth. Use this skill whenever the user wants to write resume content from a codebase or project description, improve existing resume bullets, create job application materials, or turn engineering experience into impressive resume entries. Also trigger when the user says things like "write my resume", "help me describe this project", "make my resume better", "how do I explain this project to recruiters", or "improve my project description". Works with both code repositories (auto-scans) and pasted descriptions.
As a process B 78/100 · Nearly there — weak spots: inputs and preconditions
How to improve
- 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: 4. 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 78/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 4008 tokens
- 100Tools and files. No external tools needed
- 100Steps. 58 steps
- 100Failures and branches. 1 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
- medium 3 test cases, all positive: not one "should refuse" or "should ask first"
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
- +4Description does not say when NOT to use the skill (false activations)
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 605: enough signal without eating the budget
- +4Structure: 36 headings
- +3Step-by-step instructions: 58 items
- +3Output format is stated explicitly
- +4Has examples (6 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.