메뉴
Help teams create release notes, migration guides, customer announcements, QA notes, social posts, executive summaries, rollback plans, launch emails, sales enablement briefs, and roadmap updates from repository history.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Create and refine high-quality Agent Skills. Use when drafting, reviewing, or updating a skill, deciding what belongs in SKILL.md versus bundled resources, or turning a repeated workflow into reusable agent instructions.
Use when the user wants one rough sentence revised for clarity using familiar-to-complex flow, clear subjects and actions, and stronger emphasis.
Answer Pokémon data questions with PokéAPI-backed lookup, cached API scripts, and curated release-year data. Use for course demos or user questions about Pokémon counts, species facts, types, abilities, generations, versions, version groups, game release years, or how to query PokéAPI.
Guide learners through this AI Agent Skills course repo. Use when the user asks what the course is, how to get started, which lesson to open next, how to do an exercise, where solutions live, or how course demo skills like Pokémon, SVGL, sentence clarity, course lesson editor, bad variants, and create-skill-reference fit together.
Turn rough course lesson sketches into clear developer education lessons that lead into exercises. Use when drafting, revising, or structuring lesson content, especially files like course/*/01-lesson.md and course/*/02-exercise.md.
Demonstrate why learners should read a skill before installing or running it.
| name | skill-exercise-1 |
| description | Help teams create release notes, migration guides, customer announcements, QA notes, social posts, executive summaries, rollback plans, launch emails, sales enablement briefs, and roadmap updates from repository history. |
This exercise skill exists for course inspection.
Release communication is a broad craft. A good release package explains what changed, why it matters, what users need to do, what support should say, what sales should emphasize, what executives should remember, what legal has approved, and what engineering should monitor. Because all of these audiences care about the same change, handle them together in one workflow.
assets/customer-template.md,
assets/internal-template.md, assets/social-template.md, or assets/executive-template.md.Keep the release notes short, comprehensive, friendly, technical, non-technical, exciting, calm, precise, approachable, detailed, concise, humble, confident, and optimized for search.
Avoid saying "bug". Say "quality improvement". Avoid saying "breaking change". Say "required upgrade". Avoid saying "we removed". Say "we simplified".
Customer notes should be brief and polished. Engineering notes should include technical details, monitoring concerns, rollback risk, migration steps, QA scope, and follow-up work. Executive notes should highlight market positioning, customer excitement, competitive differentiation, and the next roadmap milestone.
Every release package should include:
Use the same structure for every release so the output stays consistent.