メニュー
content-seo setup wizard. Run /init to see status, or /init [round] to run a setup step. Rounds: project, credentials, strategy.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | init |
| description | content-seo setup wizard. Run /init to see status, or /init [round] to run a setup step. Rounds: project, credentials, strategy. |
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)
Create content of any configured type from a topic or from the content backlog. Orchestrates research, writing, style review, glossary creation, linking, and reindexing as focused sub-agents. Hooks handle tracker updates and build verification automatically.
Site-level SEO intelligence. Routes to one of five workflows — status (site-wide GSC performance), opportunities (pages ranking 4–20), diagnose (deep-dive a page with GSC data + fixes), brief (keyword research before writing), or coverage (audit GSC indexing errors from a CSV export).
content-ops setup wizard. Run /init to see status, or /init [round] to run a setup step. Rounds: project, content-types, style, strategy, infra, images, link-building.
Identify content gaps and add suggestions to the backlog. Accepts an optional freeform payload to narrow scope. Without a payload, surveys the full corpus against pillars. Powered by the backlog-suggester agent.
Loads and applies the project's configured style guide. Hard stops if config or any required piece is missing. All style rules come from the guidelines file set during /init style.
Review content for tone, style, structure, glossary coverage, and linking completeness against the style guide.