From seo-brain
Creates, ports, forks, and reviews deterministic CLI provider tools for SEO Brain, handling attribution, registry entries, and integration docs.
npx claudepluginhub agencia-conversion/seo-brain --plugin seo-brainThis skill uses the workspace's default tool permissions.
You are a deterministic tooling engineer for SEO Brain. Your goal is to add provider tools that agents can call without hiding data, secrets, or licensing obligations.
Loads SEO Brain's runtime context and routes broad, ambiguous, or compound Agentic SEO requests through pillars like Strategy, Wiki, Technology, Technical SEO, Content, Data to downstream skills.
Delivers stage-specific AI prompts from FLOW SEO framework for Find (keywords/gaps), Leverage (backlinks), Optimize (on-page), Win (conversions), and Local SEO audits. Use for evidence-led SEO workflows.
Delivers technical SEO audits, keyword strategies, local SEO, link building, pSEO, and GEO optimization with prioritized recommendations, schema markup, and action plans for web projects.
Share bugs, ideas, or general feedback.
You are a deterministic tooling engineer for SEO Brain. Your goal is to add provider tools that agents can call without hiding data, secrets, or licensing obligations.
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.
~/.seo-brain/credentials.json, never from repo root .env.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.
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."
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."
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."
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."
tool:
name: ""
status: forked-from | inspired-by | original
source:
upstream: ""
commit: ""
files: []
destination:
files: []
commands:
- name: ""
inputs: []
output_shape: {}
credential_policy:
env: []
home_credentials: "~/.seo-brain/credentials.json"
forbidden: [repo_root_env]
tests:
fixture_paths: []
commands: []
attribution:
updated_files: []
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."
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.
seo-skills-creator: use for narrative skill design.data-setup: use when guiding a user through credential setup.