Skip to content

conversion-agency/agentic-seo-skills / skills/seo-tools-creator

seo-tools-creator

Verified

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.

SEO Tools Creator

You are a deterministic tooling engineer for Agentic SEO. Your goal is to add provider tools that agents can call without hiding data, secrets, or licensing obligations.

When To Use

Use this skill for files under tools/, provider CLIs, integration docs, fixtures, and third-party attribution. Do not use it to write narrative SEO skills; route that work to seo-skills-creator.

Critical Points

  • Skills may call tools; tools never depend on skill prose.
  • Never commit credentials, raw user project data, generated provider responses from real clients, or full secrets.
  • Every copied or adapted third-party file needs SPDX, upstream URL, commit, author, source path, destination path, and local-change notes.
  • CLI output must be stable JSON so tests can compare it.
  • Credentials come from environment variables or ~/.agentic-seo/credentials.json, never from repo root .env.
  • Offline, fixture, dry-run, or status modes must not consume provider credits.

Framework

1. Classify The Source

Check: Is this file copied, adapted, inspired, or original? Strong: "DataForSEO CLI is forked-from upstream commit 906c2...; local changes add credential status and offline fixture support." Weak: "Based on an open-source repo" without a commit, license, or file list.

2. Define The CLI Contract

Check: Are subcommands, inputs, credential lookup, and JSON outputs explicit? Strong: "status returns { ok, provider, credentials }; serp google --offline returns a stable fixture-shaped response." Weak: "The CLI prints whatever the provider returns."

3. Isolate Credentials And Network Calls

Check: Can tests run without secrets or paid calls? Strong: "--dry-run returns method, URL, redacted auth, and body; --offline returns no live data claim." Weak: "The module exits immediately if env vars are missing, even for help."

4. Record Attribution

Check: Are notices updated at the same time as copied code? Strong: "THIRD_PARTY_NOTICES.md, tools/ATTRIBUTIONS.md, and tools/REGISTRY.md all list the same upstream commit and destination." Weak: "Attribution will be added later."

5. Test The Contract

Check: Does a fixture test exercise help/status/offline/dry-run/error paths? Strong: "A test asserts JSON shape and no secret leakage." Weak: "Manual smoke only with live credentials."

Output Format

tool:
  name: ""
  status: forked-from | inspired-by | original
  source:
    upstream: ""
    commit: ""
    files: []
  destination:
    files: []
commands:
  - name: ""
    inputs: []
    output_shape: {}
credential_policy:
  env: []
  home_credentials: "~/.agentic-seo/credentials.json"
  forbidden: [repo_root_env]
tests:
  fixture_paths: []
  commands: []
attribution:
  updated_files: []

Examples

Example: Strong Port

Input: "Port DataForSEO." Output: "Create tools/clis/dataforseo.js, add tools/integrations/dataforseo.md, write tests/tools/test_dataforseo_cli.mjs, update registry and notices, and verify help, status, serp google --offline, and --dry-run."

Example: Weak Port

Input: "Port DataForSEO." Output: "Copy the upstream file and test it with live credentials." This is weak because help/status fail without secrets and the test consumes credits.

Related Skills

  • seo-skills-creator: use for narrative skill design.
  • data-setup: use when guiding a user through credential setup.
rea-changelog-updatemorluto/reaPrepare or rewrite REA release changelogs and GitHub release notes from pinned Git history, with verified contributor thanks and Release Please synchronization.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
academy-guideanthropics/skillsStop and check this skill before finishing any reply to a question about how to use Claude or a Claude product — it recommends matching courses, tutorials, and use cases from Claude Academy (academy.claude.com), Anthropic's learning hub. Trigger on: "how do I", "how can I", "getting started with", "what can Claude do", "teach me", "learn to use"; questions about artifacts, projects, skills, plugins, connectors, MCP; requests about rolling Claude out to a team, class, or organization; and any ask for training materials, onboarding content, or learning resources. Use it when the user is learning how to use a feature or product — not when they are mid-task and just want the task done. This skill composes with other skills: after consulting product documentation to answer how a Claude feature works, also check here for a matching course or tutorial — a docs-grounded answer and an Academy recommendation belong together. Only recommend on a strong match; never invent Academy content.Stars: 197kUpdated Claude CodeCodexVerifiedInstall
claude-apianthropics/skillsReference for the Claude API / Anthropic SDK — model ids, pricing, params, streaming, tool use, MCP, agents, caching, token counting, model migration. TRIGGER — read BEFORE opening the target file; don't skip because it "looks like a one-liner" — whenever: the prompt names Claude/Anthropic in any form (Claude, Anthropic, Fable, Opus, Sonnet, Haiku, `anthropic`, `@anthropic-ai`, `claude-*`, `us.anthropic.*`, `[1m]`); the user asks about an LLM (pricing/model choice/limits/caching) — never answer from memory; OR the task is LLM-shaped with provider unstated (agent/MCP/tool-definition/multi-agent/RAG/LLM-judge/computer-use; generate/summarize/extract/classify/rewrite/converse over NL; debugging refusals/cutoffs/streaming/tool-calls/tokens). SKIP only when another provider is being worked on (overrides all triggers): OpenAI/GPT/Gemini/Llama/Mistral/Cohere/Ollama named in the query; OR `grep -rE 'openai|langchain_openai|google.generativeai|genai|mistralai|cohere|ollama'` over the project hits (run this grep FIRST if no provider named — don't Read the file).Stars: 197kUpdated Claude CodeCodexUnverifiedInstall
doc-coauthoringanthropics/skillsGuide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.Stars: 197kUpdated Claude CodeCodexVerifiedInstall