메뉴
When the user wants to create a new skill for a repeated pattern. When the user says "create a skill for" or "we should formalize this". When the user identifies a repetitive workflow that should be automated.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
When the user wants to add a new feature or capability. When the user says "I want to build" or "I'm thinking about". When requirements are unclear and need to be refined.
When the user says they are ready for review or wants to create a PR. When the user asks to check if code is ready for review. When the task or feature is complete and needs quality validation.
When the user approves a plan and wants to execute it. When the user says "execute the plan" or "let's go" or "start implementation". When a PLAN.md exists and is ready to be executed task-by-task.
When the user is implementing a new feature or fixing a bug. When the user wants to write tests first before writing code. When the user is refactoring and needs to verify behaviour is preserved.
When the user wants to create an implementation plan. When the user says "let's implement this" or "create a plan". When a design has been approved and is ready to be broken into tasks.
Systematic code review workflow — evaluate changes for correctness, style, security, and test coverage before merging. When the user asks to review code or a pull request. When the user says "check code quality" or "look over this diff". When the user requests feedback on changes before merging.
| name | writing-skills |
| description | When the user wants to create a new skill for a repeated pattern. When the user says "create a skill for" or "we should formalize this". When the user identifies a repetitive workflow that should be automated. |
| tools | ["read","edit"] |
Without formalizing repeated workflows as skills, agents re-derive the same process each time — inconsistently and without the hard-won lessons from previous attempts. This skill captures proven patterns as reusable, validated skill files.
Confirm the workflow is worth formalizing — only patterns that recur and benefit from consistency should become skills.
Look for:
Write the skill following the standard format with all required sections:
# Skill: Systematic Code Review
## Purpose
Without a structured review checklist, reviewers miss security issues and inconsistencies that accumulate into technical debt. This skill ensures every review covers correctness, security, and maintainability.
## Auto-Trigger
- User says "review this code" or "check my PR"
- Before merging any feature branch
## Process
### 1. Check correctness
...
## Output
Review report with severity-ranked findings.
## Anti-Patterns
❌ Reviewing only happy-path logic
# Project-specific skill
mkdir -p .clinerules/skills/my-skill && cp SKILL.md .clinerules/skills/my-skill/
# General-purpose skill (after validation)
cp -r my-skill ~/.claude/skills/
A SKILL.md file with score >= 90 from prg skills validate, saved to the appropriate directory.
❌ Creating a skill without testing it first ❌ Vague trigger conditions that activate too broadly ❌ Missing Anti-Patterns section ❌ Placeholder text left in the skill body