content-ops

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.

Use when the user wants to announce a product launch or new feature. Triggers: "HN Show post", "announce feature", "product launch post", "announce on HN", "write launch announcement", "post on HN", "Product Hunt post", "IndieHackers post", "GitHub launch".

Use when the user wants to plan and execute a multi-platform launch. Triggers: "launch plan", "launch sequence", "launch checklist", "multi-platform launch", "coordinate launch", "launch timeline".

Use when the user wants to convert a blog article into a newsletter email. Triggers: "newsletter from article", "email version", "convert to newsletter", "article to email", "newsletter variant".

Use when the user wants to turn a technical artifact into a blog post. Triggers: "README to post", "release notes to blog", "docs to article", "turn changelog into post", "write post from my PR description", "blog post from commit messages".

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".

Use when the user wants to promote an article on social media. Triggers: "Twitter thread", "LinkedIn post", "Bluesky post", "Mastodon toot", "LinkedIn carousel", "social variants", "tweetstorm from article", "social media post", "share on Twitter".