メニュー
Use when the user wants SEO help for a technical article. Triggers: "SEO audit", "keyword for article", "optimize for search", "is this SEO-ready", "meta description", "should I add keywords".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the user wants to set up or update their content profile. Also use when the user says "my blog is about", "content profile", "set up content context", or "who am I writing for". Stores context as .agents/content-context.md — read by all other content-ops skills first.
Use when the user wants content ideas or a backlog. Triggers: "content ideas", "what to write next", "build backlog", "ideas from changelog", "what should I post about", "content calendar".
Use before publishing any article. Triggers: "check article", "preflight", "validate post", "is this ready to publish", "QA my post", "pre-publish check". Run this before distribute or any publish command.
Use when the user wants feedback on marketing copy, headlines, or landing page text. Triggers: "edit landing page", "improve headline", "copy feedback", "review this copy", "is this headline good", "landing page copy review".
Use when the user wants to publish an article to multiple platforms at once. Triggers: "publish article", "distribute to platforms", "send to devto and hashnode", "cross-post", "publish everywhere", "distribute my post".
Use when the user wants to write a welcome sequence or email drip campaign. Triggers: "welcome sequence", "newsletter drip", "onboarding emails", "email series", "welcome email". Note: generates drafts only — no sending, no API.
| name | seo-for-devs |
| description | Use when the user wants SEO help for a technical article. Triggers: "SEO audit", "keyword for article", "optimize for search", "is this SEO-ready", "meta description", "should I add keywords". |
Read .agents/content-context.md first (if it exists).
Lightweight SEO checklist for developers who don't think of themselves as marketers. Not keyword stuffing — just making good technical content findable.
Run through references/checklist.md. For each item, check the article and report: OK / Fix / Missing.
Ask: what would someone type to find this article? Verify that phrase appears naturally in title + first paragraph.
Produce a short report:
Do NOT recommend keyword density targets or schema markup — that's over-engineering for a dev blog.
