AB geo-content-publisher
End-to-end GEO content publishing and distribution orchestrator. Use this skill whenever the user mentions publishing or distributing GEO-optimized content across multiple channels (blog, docs, landing pages, social, newsletter, app updates, etc.), wants to turn one core piece into many channel-specific variants, or wants to make new or updated content highly visible to AI crawlers and generative engines. Always consider this skill when the user combines content optimization, multi-platform distribution, and AI search visibility in the same request.
As a process B 65/100 · Nearly there — weak spots: inputs and preconditions, consistency, running it twice
How to improve
- 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: 5. 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 65/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 23 mutating operations with no state check
- 40Consistency. Frontmatter name (geo-content-publisher) differs from the folder (geo-content-publisher-2)
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 70Failures and branches. 7 branches
- 85Steps. 132 steps, 3 vague phrases
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 3337 tokens
- medium 3 test cases, all positive: not one "should refuse" or "should ask first"
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)
- -41 reference files, but SKILL.md never points to them: the model will not open them
- -32 of 2 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 555: enough signal without eating the budget
- +4Structure: 15 headings
- +3Step-by-step instructions: 132 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.