BC improve-hn-karma
Generate daily batch of Hacker News comments in founder's expertise areas. Trigger phrases: "draft HN comments", "generate HN karma", "write HN posts", "HN comment batch", "build HN karma", "compose HN replies".
Generate daily batch of Hacker News comments in founder's expertise areas.
As a process C 51/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
name-missingSKILL.md: frontmatter has no `name` - warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 1, column 14: description: Generate daily batch of Hacker News comments in founder's expertis… ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value
Process rating: all ten parameters 51/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 85Steps. 18 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1579 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 211: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 49.