AB newsletter-seo-pipeline
8-step SEO content production workflow for newsletters and blogs. Runs SERP analysis, builds an optimized outline, writes in your newsletter's voice, screens for AI patterns, applies quality gates, validates SEO metadata, formats, and generates a paste-ready publish doc — all in one pipeline. Use when writing a newsletter issue, an evergreen SEO post, or any long-form article that needs to rank in search. Triggers on: 'write issue', 'write newsletter', 'write evergreen post', 'write SEO post', 'run the pipeline', 'produce issue', 'newsletter pipeline', 'write article', 'write blog post'. Pairs with newsletter-launch for full automation. NOT for: social posts, email subject lines, short-form copy, keyword research only. Requires: serp-analysis, seo-content-engine, article-writing, markdown-formatter. Optional: de-ai-ify (auto-installed by newsletter-launch).
As a process B 68/100 · Nearly there — weak spots: inputs and preconditions, running it twice, 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: 6. 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 68/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 65Failures and branches. 3 branches
- 100Steps. 18 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1080 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (5 tags): a typed call is more reliable
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
- +3Description length 869: 120–800 characters recommended
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 13 headings
- +3Step-by-step instructions: 18 items
- +3Output format is stated explicitly
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 95.