Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From content-seo
content-seo setup wizard. Run /init to see status, or /init [round] to run a setup step. Rounds: project, credentials, strategy.
npx claudepluginhub pcamarajr/content-stack --plugin content-seoHow this skill is triggered — by the user, by Claude, or both
Slash command
/content-seo:initThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Interactive setup wizard for content-seo. Configures the plugin for your project through a guided conversation.
First-run entry point for Agentic SEO that routes new users to project-init or agentic-seo workflows without duplicating process rules.
Guides setup of WordPress, Strapi, Contentful, or Ghost CMS connections; tests them, saves credentials to .env.local, enables SEO analysis with Google Search Console data.
Audits codebase content for marketing: inventories blog posts/guides/cases, assesses SEO health (titles, metas, sitemaps, robots), identifies competitor gaps via web search. Use for content audits or strategy planning.
Share bugs, ideas, or general feedback.
Interactive setup wizard for content-seo. Configures the plugin for your project through a guided conversation.
Arguments: $ARGUMENTS
Parse $ARGUMENTS:
project → Read skills/init/rounds/project.md (relative to plugin root) and follow its instructions completelycredentials → Read skills/init/rounds/credentials.md (relative to plugin root) and follow its instructions completelystrategy → Read skills/init/rounds/strategy.md (relative to plugin root) and follow its instructions completelyproject, credentials, strategyAfter completing any round, always end with a short "What's next?" line pointing to the next incomplete round.
Only runs when $ARGUMENTS is empty.
Try to read .content-seo/config.md → parse YAML frontmatter.
Try to read .content-ops/config.md → note if content-ops is present (display as info, not a requirement).
| Round | Complete when |
|---|---|
| project | gsc_property and content_ops_config are both set in .content-seo/config.md |
| credentials | GSC: gsc_credentials_path points to a readable file OR $GOOGLE_APPLICATION_CREDENTIALS is set and file exists. DataForSEO: $DATAFORSEO_LOGIN and $DATAFORSEO_PASSWORD both non-empty (check with Bash). GSC is required; DataForSEO is optional. |
| strategy | seo_rules has at least one content type key in .content-seo/config.md |
If .content-seo/config.md does not exist: all rounds are incomplete. Credentials are always checked live from the environment.
Use 🔄 (started) when the config file exists but only some required fields for that round are set.
## content-seo — Setup Status
GSC property: [gsc_property from config, or "—"]
Config: .content-seo/config.md ([found | not found])
content-ops: [found | not found]
✅ /seo init project — [one-line summary, e.g. "sc-domain:mysite.com · content-ops linked"]
⬜ /seo init credentials — not started
⬜ /seo init strategy — not started
→ Next: /seo init [first incomplete round]
What each step does:
project — Link content-ops config and set GSC property + credentials path
credentials — Verify GSC service account access and optional DataForSEO credentials
strategy — Define per-content-type SEO rules (meta description length, H1 keyword)