agentic-seo-skills

Load Agentic SEO's canonical runtime context and route broad, ambiguous, or compound Agentic SEO requests through the right gates and downstream skills.

When the user wants to ingest sources, change brain pages, register decisions, catalog content publications, or lint brain pages for provenance and link integrity.

When the user wants to brief, write, review, optimize, or publish public SEO content. Also use for article outlines, blog posts, landing-page copy, refreshes, and ranking-oriented editorial drafts.

When the user wants to configure, validate, or troubleshoot DataForSEO or another SEO data provider securely. Also use when provider credentials are missing before keyword, SERP, or SEO analysis work.

When the user wants to create, initialize, or prepare one Agentic SEO project with the standard local project structure, blank brain templates, content directories, and initial log entry.

When the user wants to build, refresh, or promote an SEO topic cluster (pillar + satellites) backed by keyword and SERP evidence. Runs in four phases — Pesquisar, Curar, Estruturar, Promover — with the cluster draft kept outside the brain until human approval.

Friendly first-run alias that routes new Agentic SEO users to the canonical agentic-seo and project-init workflow without duplicating process rules.

When the user wants a rigorous iteration loop for an artifact, prompt, briefing, content structure, or Agentic SEO skill. Also use for Karpathy-style experiment runs that need baseline scoring, explicit metrics, stop rules, and keep/reject decisions.

When the user wants backlink, referring-domain, anchor, link-quality, link-gap, link-intersect, anchor-diff, link-velocity, brand-mention, or competitor link-profile analysis for one target domain or URL.

When the user wants to compare domains or URLs against competitors across SEO footprint, share of voice, keyword/content gap, head-to-head pages, off-page link gap (via backlink-analysis), and brand positioning. Orchestrates evidence from serp-extract, keyword-research, backlink-analysis, and topic-cluster without duplicating their work.

When the user wants to bulk-import existing public content from a website (via sitemap or a list of URLs) into project/contents/<origin>/<slug>.md as the starting point for editorial work in this brain.

When the user wants to audit, strengthen, or prepare evidence for Experience, Expertise, Authoritativeness, and Trust. Also use before registering proof entries in `project/brain/log.md` or referencing them in `project/brain/topic-clusters.md`.

When the user wants internal link opportunities, contextual link recommendations, anchor text improvements, or validation before applying internal links.

When the user wants keyword research, keyword expansion, search volume, CPC, competition, long-tail opportunities, or clustering inputs for a market. Also use before topic-cluster or content planning work that needs keyword evidence.

Shared report-page contract for Agentic SEO modules that render editable, human-first Markdown reports in the Web Companion.

When the user wants a keyword SERP analysis with competitor comparison, target page gaps, or player-score interpretation. Also use before topic cluster or content brief work that needs SERP evidence.

When the user wants to create, rewrite, evaluate, or improve an Agentic SEO skill. Also use when planning a skill-loop run or converting a formal contract skill into a narrative self-sufficient skill.

When the user wants to create, port, fork, or review deterministic provider tools for Agentic SEO. Also use when adding tool attribution, registry entries, or provider integration docs.

When the user wants to capture SERP evidence, search result snapshots, competitor URLs, or SERP features for specific keywords without doing SEO analysis.

MUST USE PROACTIVELY before executing a user request with two or more distinct deliverables, downstream skills, Agentic SEO pillars, dependencies, or decision/evidence/check gates. Use for compound requests such as research plus brain updates, technical audit plus content plan, content plus publication review, or any bulleted/numbered request with separate outcomes. Do not use for a single clear task.

When the user wants a deterministic technical SEO audit, page-template validation, JSON audit interpretation, or repair-priority report for a rendered page or site URL.