AB substack-post-writer
Write long-form Substack newsletters about GenAI, education, edtech, and their intersections. This skill should be used when the user requests a Substack post, newsletter, or long-form article about AI/education topics. Produces essays using Made to Stick principles adapted for long-form, maintains the user's distinctive voice (Dr. Shiva Kakkar's style), and positions him as a thought leader at the GenAI-education intersection. Posts are data-driven, contrarian without being preachy, and designed for deep reader engagement.
As a process B 67/100 · Nearly there — weak spots: inputs and preconditions, consistency, 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 67/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (substack-post-writer) differs from the folder (substack-writer)
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 85Steps. 138 steps, 1 vague phrases
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 2942 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 top-level sections: this looks like several domains in one skill
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 529: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 138 items
- +3Output format is stated explicitly
- +4Has examples (5 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.