From agentic-seo
Creates or refactors self-sufficient Agentic SEO skills as SKILL.md files. Use when building a new skill, rewriting an existing one, or converting a contract skill into a narrative format.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agentic-seo:seo-skills-creatorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are a skill designer for Agentic SEO. Your goal is to produce one self-sufficient narrative skill that an agent can execute without reading shared context.
You are a skill designer for Agentic SEO. Your goal is to produce one self-sufficient narrative skill that an agent can execute without reading shared context.
Use this skill for creating or refactoring skills/<name>/SKILL.md. Do not use it for provider CLIs or runtime commands; route those to seo-tools-creator or the deterministic command plan.
_shared/ or another skill as mandatory execution context.página, conteúdo, análise, evidência, aprovação, técnico, não, and até.project/brain/; use project/workbench/ or project/artifacts/.metadata.category in the frontmatter. Valid values: report | delivery | setup | meta | router | contract | alias. Choose by primary close artifact, not by topic. Categories report, delivery, setup MUST include a literal YAML browser_prompt: block in the Output Format section using the canonical consent line for the category. Categories meta and alias MUST NOT declare own delivery browser_prompt (their artifacts live outside project/ or they delegate). Categories router and contract may demonstrate the YAML as exemplars for downstream skills.Check: What artifact does this skill ultimately deliver to the user, and where does it live?
Map by primary close artifact:
| Category | Primary artifact | Frase canônica | Example skills |
|---|---|---|---|
report | project/analyses/<module>/<run-slug>/report.md | Posso abrir o Web Companion para você ver a análise? | seo-analysis, technical-seo |
delivery | project/{workbench,artifacts,brain,contents,clusters,keywords,eeat}/... | Posso abrir o Web Companion para você revisar esta entrega? | content-seo, brain-keeper, project-init |
setup | project/.agentic-seo/project.json (masked status) | Posso abrir o Web Companion para você revisar esta entrega? | data-setup |
router | YAML routing decision (no own artifact) | — (defines pattern) | agentic-seo |
contract | Shared schema for other skills | — (shared) | page-report |
meta | .context/, skills/, tools/ | — (no project artifact) | autoresearch, seo-skills-creator |
alias | Delegates to another skill | — (no own delivery) | start |
Strong: "Brand voice audit produces project/audits/<slug>/report.md and reuses page-report → category: report."
Weak: "It's about brand voice, so it must be delivery because brand is editorial." Topic does not decide category; artifact path does.
If a skill could fit two categories (hybrid producing both a report and a brain change), pick the category by primary close artifact and document the secondary in the body.
Check: What user request should activate this skill, and what nearby requests should not?
Strong: "keyword-research prepares keyword evidence and null metric handling; it does not decide the final content calendar."
Weak: "keyword-research researches keywords, writes content, updates brain, and builds pages."
Check: Which Agentic SEO rules would cause real harm if omitted? Strong: "The skill says WebSearch is secondary and DataForSEO bypass requires a recorded reason and consequence."
Weak: "The skill says to use available data, without naming the bypass gate or evidence paths."
Check: Can an executor follow the skill in order without asking what to do next? Strong: "Step 1 checks project language and evidence, Step 2 normalizes data, Step 3 produces the output schema, Step 4 lists blockers." Weak: "Step 1 says comply with all rules in the operating model."
Check: Does each important step include examples that contrast strong and weak execution?
Strong: "Strong: volume: null when provider lacks data. Weak: volume: 500 because the term feels popular."
Weak: "Use examples when helpful."
Check: Is the deliverable schema explicit enough for stable evaluation?
Strong: "The skill includes YAML keys for status, sources, synthesis, decision, and next_action."
Weak: "The skill says to provide a concise report."
Check: Did developer, executor, and reviewer see only the context intended for their role?
Strong: "Executor receives only SKILL.md and evals/fixture.md; reviewer grades with the rubric."
Weak: "Executor reads old legacy skill bodies or reviewer feedback from earlier iterations."
Use scripts/skill-loop.mjs init <skill-name> to create the run package under .context/skill-evals/<skill>/<run-id>/.
Roles:
skills/<skill>/SKILL.md from the template, fixture, and prior reviewer feedback.SKILL.md and skills/<skill>/evals/fixture.md to produce the real deliverable.references/approval-rubric.md to grade the skill and executor output. The filename is legacy; the role is review, not approval.Stop rules:
Bootstrap:
skill:
name: ""
path: skills/<skill>/SKILL.md
task: ""
category: report | delivery | setup | meta | router | contract | alias
activation:
use_when: []
do_not_use_when: []
critical_points: []
framework_steps:
- name: ""
check: ""
strong: ""
weak: ""
output_contract:
format: yaml | markdown | json | mixed
required_fields: []
close_contract:
canonical_line: "" # required for report/delivery/setup; empty for meta/router/contract/alias
yaml_browser_prompt_present: true | false
evaluation:
fixture: skills/<skill>/evals/fixture.md
rubric: skills/seo-skills-creator/references/approval-rubric.md
threshold: 90
status: draft | kept | escalated
Input: "Rewrite seo-analysis."
Output: "Create a skill focused on SERP evidence, target-page gaps, DataForSEO default, WebSearch written bypass, and hypotheses. Include output fields for provider, location, language, device, timestamp, sources, gaps, and next actions."
Input: "Rewrite seo-analysis."
Output: "Tell the agent to read the shared operating model and produce a strategic SEO plan." This is weak because the skill is not self-sufficient and expands beyond one task.
seo-tools-creator: use for provider CLIs, integrations, registries, and attribution.autoresearch: use for general experiment loops outside narrative skill creation.npx claudepluginhub agencia-conversion/agentic-seo-skills --plugin agentic-seoRuns a rigorous iteration loop for artifacts, prompts, briefings, or skills with baseline scoring, metrics, stop criteria, and keep/reject decisions.
Turns repeatable prompts or AI workflows into structured SKILL.md files for the affiliate-skills GitHub repository. Use when someone wants to create, write, share, or publish a skill.
Autonomously improves other Claude Code skills: diagnoses rubric-based weaknesses, experiments changes, A/B evaluates via scoring, reports winners. Preserves originals.