القائمة
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".
التثبيت باستخدام 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 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".
| name | content-ideas |
| description | 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". |
Read .agents/content-context.md first (if it exists).
Generate a content backlog from existing artifacts. Every project has latent content — shipped features, solved problems, interesting trade-offs. Surface them.
Ask what artifacts to mine (can select multiple):
For each artifact, extract content hooks:
Output as a prioritized backlog table:
| Title idea | Type | Source artifact | Estimated effort |
|---|---|---|---|
| ... | Tutorial | CHANGELOG v0.4 | Medium |
| ... | Decision post | GitHub issue #23 | Low |
content-backlog.md file?Prioritize: (1) things users asked about in issues, (2) non-obvious technical decisions, (3) results with concrete numbers. Deprioritize: announcements without substance, ideas with no concrete code to show.