메뉴
Template Agent Skill for ACS. Replace with a real skill name (must match this directory) and a description that states what the skill does and when to use it, including trigger keywords.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | example-skill |
| description | Template Agent Skill for ACS. Replace with a real skill name (must match this directory) and a description that states what the skill does and when to use it, including trigger keywords. |
| license | MIT |
This body is Markdown instructions loaded after discovery. Follow the Agent Skills specification for front matter and naming rules.
name field so they match (lowercase, hyphens, no leading or trailing hyphen, no --).description (what + when) for reliable activation.scripts/, references/, or assets/ beside this file if needed.Reviews root AGENTS.md for agents.md style plus ACS discoverability. Use when editing AGENTS.md or when user asks if the entry contract is complete. Triggers on AGENTS.md, entry contract, or agents.md alignment.
Audits this repository for ACS v0.1 self-consistency—AGENTS.md discovery, .ai/index completeness, skill packages, and verify script. Use before releases or when user asks if the repo is compliant. Triggers on audit, compliance, self-check, or verify repo.
Edits normative Sections 1–10 of spec/ACS-v0.1.md. Use for BCP 14 keyword fixes, compliance wording, Section 10 reference table updates, or new MUST/SHOULD rules. Triggers on normative spec, BCP14, compliance, Section 10, or RFC 2119.
Creates or edits Agent Skills packages under .ai/skills/, templates/.ai/skills/, or examples. Validates directory name, SKILL.md front matter, and index links. Use for skill structure or YAML fixes. Triggers on SKILL.md, skill package, agentskills, or new skill directory.
Aligns templates/ and examples/ with spec ACS-v0.1 after layout or taxonomy changes. Use when publisher docs or Sections 5–8 paths change. Triggers on templates, examples, parity, or publisher-layout.
Adds or updates automated tests when code behavior changes. Use after implementing features, fixing bugs, refactoring public APIs, or when the user asks for test coverage. Triggers on keywords such as tests, coverage, unit test, and regression.