AF auto-content-blog
Full end-to-end SEO + GEO content creation pipeline for crypto/Web3 teams. Trigger this skill when the user wants to: write a blog post or article, research keywords, generate a content brief or outline, mine community comments for UGC insights, optimize content for SEO or AI search engines (GEO), score or audit an existing article, or check if writing sounds AI-generated. Also trigger automatically at the start of every new session to scan X for trending topics relevant to the user's project spec — propose hot keywords before the user asks. Accepts a project spec .md file as primary input. Also works with plain keyword or topic. Run all stages in sequence when starting from scratch. Enter mid-pipeline if user provides an existing draft or only asks for one stage.
Full end-to-end SEO + GEO content creation pipeline for crypto/Web3 teams.
As a process F 63/100 · Will not run — References files that are not bundled: references/scoring-rubrics.md, references/ai-patterns-blacklist.md, references/output-templates.md
How to improve
- The text references files that are not there: add them or drop the references.
- 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
missing-refreference to a missing file: references/scoring-rubrics.md - warning
missing-refreference to a missing file: references/ai-patterns-blacklist.md - warning
missing-refreference to a missing file: references/output-templates.md - warning
missing-refreference to a missing file: references/example-run.md
Process rating: all ten parameters 63/100
- 0Tools and files. 4 referenced file(s) missing: references/scoring-rubrics.md, references/ai-patterns-blacklist.md, references/output-templates.md
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (auto-content-blog) differs from the folder (cook-a-skill-content-blog-social)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 92 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 3869 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 12 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 774: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 92 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.