BD delegate_app_dev
Triggers whenever the user asks to build a feature, fix a bug, create a screen, or modify the mobile app.
Triggers whenever the user asks to build a feature, fix a bug, create a screen, or modify the mobile app.
As a process D 37/100 · Unfinished process — weak spots: result and completion, inputs and preconditions, failures and branches
GeneratorSoftware developmentInfrastructureAI and agentstype and topics are labelled automatically from the skill text
How to improve
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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - note
frontmatter-keyunknown frontmatter key "requires"
Process rating: all ten parameters 37/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 40Consistency. Frontmatter name (delegate_app_dev) differs from the folder (appdev)
- 50Steps. 2 steps
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 100Execution cost. Instruction body is 166 tokens
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 105: 120–800 characters recommended
- +4Structure: 2 headings, hard to scan
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
Quality base 70; lint remarks subtract, signals add up to 100. Result: 62.