菜单
Use when the user wants to create or refine Codex skills, improve skill descriptions, organize skill resources, or follow Codex skill best practices.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use before starting ANY work - hard gate ensuring a GitHub issue exists, creating one if needed through user questioning
Use when receiving UAT feedback, bug reports, user testing results, stakeholder feedback, QA findings, or any batch of issues to investigate. Investigates each item BEFORE creating issues, classifies by type and priority, creates well-formed GitHub issues with proper project board integration.
MANDATORY for all work - the project board is THE source of truth. This skill provides verification functions and gates that other skills MUST call. No work proceeds without project board compliance.
Use for LARGE work requiring feature-level grouping. Creates epic tracking issues, manages related issues under a common label, tracks epic progress, and coordinates with milestones.
Use when the user wants to design Codex agent equivalents (specialized workers/profiles/prompt files), define triggering conditions, or build reusable agent prompts and validation tools.
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.
| name | skill-development |
| description | Use when the user wants to create or refine Codex skills, improve skill descriptions, organize skill resources, or follow Codex skill best practices. |
This skill provides guidance for creating effective Codex skills and aligning with current Codex CLI conventions.
Skills are modular packages that give Codex reusable workflows, domain knowledge, and tooling. Codex uses a skill in two ways:
$skill-name (or uses the /skills picker in supported clients).Codex loads skills from these locations, in precedence order (highest to lowest):
$CWD/.codex/skills$CWD/../.codex/skills (if inside a git repo)$REPO_ROOT/.codex/skills (git repo root)$CODEX_HOME/skills (default ~/.codex/skills)/etc/codex/skillsNotes:
skill-name/
├── SKILL.md (required)
├── scripts/ (optional)
├── references/ (optional)
└── assets/ (optional)
SKILL.md must include YAML frontmatter with:
name: non-empty, <= 100 characters, single linedescription: non-empty, <= 500 characters, single lineExtra keys are ignored by Codex.
Example:
---
name: draft-commit-message
description: Draft a conventional commit message when the user asks for help writing a commit message.
---
Clarify triggers Define concrete user phrases that should activate the skill. Keep the description specific.
Plan reusable resources Decide which scripts, references, or assets will save time. Prefer scripts for deterministic steps.
Create the skill folder Put it in a valid Codex skill path (see scopes above).
Write SKILL.md Keep it lean. Use imperative instructions and link out to references for detailed material.
Add references or scripts
Store long docs in references/ and reusable code in scripts/.
Restart Codex Codex loads skills at startup. Restart to pick up changes.
references/skill-creator-original.md for deeper guidance on structure and progressive disclosure