메뉴
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".
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 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 | distribute |
| description | 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". |
Read .agents/content-context.md first (if it exists).
Orchestrate the full publishing workflow: QA — publish each platform — update state.
Check .content-ops-state.json (in article's directory) for in-progress publishes.
If article was partially published, skip completed platforms and resume.
{
"article-slug": {
"devto": "published",
"hashnode": "failed",
"twitter": "pending",
"bluesky": "pending",
"mastodon": "pending",
"linkedin": "pending"
}
}
--skip-qa specified):
Run deterministic QA via content_qa.py first:
python3 ${CLAUDE_PLUGIN_ROOT}/tools/content_qa.py "$ARTICLE_PATH" --format text
2 (block): stop — show hard failures, do not publish.1 (review): show issues, ask user: "QA flagged issues. Publish anyway? (yes/no)"0 (pass): proceed to publishing.--skip-qa flag is provided: skip this step entirely (explicit opt-out).Platform | Status | URL
----------|---------|-----
dev.to | OK | https://dev.to/...
Hashnode | OK | https://hashnode.dev/...
Twitter/X | OK | https://x.com/...
Bluesky | OK | https://bsky.app/profile/.../post/...
Mastodon | OK | https://mastodon.social/@.../...
LinkedIn | OK | https://www.linkedin.com/feed/update/...
HN | Link | https://news.ycombinator.com/submitlink?...
| Platform | Command | Env vars |
|---|---|---|
| dev.to | publish-devto | DEVTO_API_KEY |
| Hashnode | publish-hashnode | HASHNODE_TOKEN, HASHNODE_PUBLICATION_ID |
| Twitter/X | publish-twitter | X_API_KEY, X_API_KEY_SECRET, X_ACCESS_TOKEN, X_ACCESS_TOKEN_SECRET |
| Bluesky | publish-bluesky | BLUESKY_HANDLE, BLUESKY_APP_PASSWORD |
| Mastodon | publish-mastodon | MASTODON_ACCESS_TOKEN, MASTODON_INSTANCE_URL |
| publish-linkedin | LINKEDIN_ACCESS_TOKEN, LINKEDIN_PERSON_URN | |
| HN | publish-hn | (human-in-loop, no credentials needed) |