BD lqs-skill
LQS Skill — prompt/schema/template driven artifact generator for the LQS codebase. Manual-run only: users paste free-text requirement or exported document text; the Skill guides prompt-driven generation of RequirementDraft → Spec → RenderPlan → Preview Diff. This Skill does NOT execute code, run migrations, or fetch external documents automatically.
As a process D 46/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Secrets in code
secret-high-entropy-tokenexamples/article.render_plan.json:60High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)"class_name": "Migr…les",
fixturequoted
Files scanned: 34. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "activation" - note
frontmatter-keyunknown frontmatter key "entry_prompts" - note
frontmatter-keyunknown frontmatter key "examples" - note
frontmatter-keyunknown frontmatter key "notes"
Process rating: all ten parameters 46/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
- 20When it triggers. No condition that starts the skill
- 50Steps. 2 steps
- 100Tools and files. No external tools needed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 129 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)
- +4Structure: 1 headings, hard to scan
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 351: enough signal without eating the budget
Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.