메뉴
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".
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 | post-from-artifact |
| description | 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". |
Read .agents/content-context.md first (if it exists) for audience and style.
Convert a developer artifact (README, CHANGELOG, PR description, commit messages, docs) into a publishable blog post. This is the core content-ops workflow — ship in public by writing about what you already built.
---
title: "..."
description: "..." # 1 sentence, under 160 chars
date: YYYY-MM-DD
tags: [...]
lang: en
---
content/posts/slug.md? Confirm path.Developer-to-developer. First person. Show don't tell — code snippets over abstract descriptions. Assume smart reader who skims.