From seo-codebase-auditor
Use when the user wants to turn an existing codebase SEO audit's action plan into a Google Sheet — a shared project tracker with task priorities, assignees, and status. Triggers on "export the SEO action plan to a Google Sheet", "make a Google Sheet from the audit", "put the SEO tasks in a sheet", "create a tracker for the SEO fixes", "assign the SEO tasks to my team". Runs AFTER the audit skill has produced reports/codebase-seo-evidence.json (or reports/codebase-seo-action-plan.md). Requires a Google service-account key; never invents assignees.
How this skill is triggered — by the user, by Claude, or both
Slash command
/seo-codebase-auditor:sheetThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Turn the action plan from a codebase SEO audit into a formatted, shared Google
Turn the action plan from a codebase SEO audit into a formatted, shared Google Sheet: a Summary tab (counts by priority/status/assignee, category grades) and a Task Tracker tab (one row per task, with Assignee and Status dropdowns). Tasks, priorities, and scores come only from the audit reports — this skill never invents tasks, and assignees come only from a roster the user provides.
This skill does not run the audit. It consumes the audit's output. If the
reports are missing, tell the user to run the audit first (the audit skill in
this plugin, e.g. "run a codebase SEO audit on this repo").
reports/codebase-seo-evidence.json
(preferred — it carries the structured actionPlan array) or
reports/codebase-seo-action-plan.md in the project being worked on.SEO_SHEET_SA_KEY
(or GOOGLE_APPLICATION_CREDENTIALS) must point to a service-account JSON key
with the Google Sheets API and Drive API enabled. One-time setup is documented
in docs/google-sheets-setup.md in this plugin.Use Glob to find reports/codebase-seo-evidence.json (and
reports/codebase-seo-action-plan.md) under the current project. If neither
exists, stop and tell the user to run the audit first. Note the path — you pass
it to the script as --input.
Check whether SEO_SHEET_SA_KEY or GOOGLE_APPLICATION_CREDENTIALS is set:
[ -n "$SEO_SHEET_SA_KEY" ] || [ -n "$GOOGLE_APPLICATION_CREDENTIALS" ] && echo "creds: set" || echo "creds: missing"
docs/google-sheets-setup.md, and offer a --dry-run instead
(builds a local CSV + payload preview, no Google calls, no creds needed).Ask the user for (these cannot be inferred from the codebase):
Ana <[email protected]>, Ravi <[email protected]>. Optional; if omitted, the
Assignee column is left blank (no dropdown).round-robin (distribute tasks across the roster, highest
priority first) or none (leave Assignee blank for manual fill). Default
none when no roster is given.SEO Action Plan — <project>.Never guess assignees. If the user gives no roster, proceed with Assignee blank.
Run the bundled script (it has zero npm dependencies):
node "${CLAUDE_PLUGIN_ROOT}/scripts/build-sheet.mjs" \
--input "reports/codebase-seo-evidence.json" \
--title "Acme SEO Action Plan" \
--roster "Ana <[email protected]>,Ravi <[email protected]>" \
--assign round-robin \
--share-with "[email protected]"
Adjust flags to the user's answers. Omit --roster/--assign if no roster was
given. For a no-credentials preview, add --dry-run (writes
reports/codebase-seo-tasks-preview.csv and a payload JSON; makes no network
calls).
The script:
actionPlan array (falls back to parsing
codebase-seo-action-plan.md if that array is absent).--share-with and prints the URL (also saved to
reports/codebase-seo-sheet-url.txt).Give the user:
reports/codebase-seo-sheet-url.txt).audit skill first; do not
fabricate tasks.docs/google-sheets-setup.md; offer
--dry-run.docs/google-sheets-setup.md (enable the APIs; for quota errors use a
Shared Drive or OAuth).--share-with omitted → warn that the sheet was created but is only
reachable via the printed URL until it is shared.Searches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.
npx claudepluginhub zeshanamindev-hub/seo-codebase-auditor --plugin seo-codebase-auditor