skill-authoring-template

新しいSkillを作るときの必須セクション(入力/出力/禁止/検証/根拠)テンプレ。skill-builder が新規Skillを生成するときに参照する。

⭐2stars🔀0forks📁View on GitHub🕐Updated Dec 20, 2025⬇️1downloads

When & Why to Use This Skill

This Claude skill provides a standardized framework and mandatory template for authoring new skills. It ensures consistency across agent capabilities by enforcing specific sections such as Inputs, Outputs, Forbidden actions, Verification, and Evidence. By following these structured guidelines, developers and automated skill-builders can create reliable, well-documented, and high-performing skills that adhere to naming conventions and best practices for agentic workflows.

Use Cases

  • Standardizing Skill Development: Use the template to ensure all custom skills within a project follow a uniform structure, making them easier to maintain and debug.
  • Automated Skill Generation: Serve as a reference for 'skill-builder' agents to automatically generate valid SKILL.md files that meet all architectural requirements.
  • Quality Assurance and Safety: Implement the 'Forbidden' and 'Verification' sections to define strict operational boundaries and testing protocols for new AI capabilities.
  • Improving Agent Contextual Accuracy: Utilize the 'Evidence' section to mandate that agents cite specific repository files or data sources, reducing hallucinations during execution.
nameskill-authoring-template
description新しいSkillを作るときの必須セクション(入力/出力/禁止/検証/根拠)テンプレ。skill-builder が新規Skillを生成するときに参照する。

Skill Authoring Template

YAML frontmatter (MUST)

SKILL.md は必ず YAML フロントマターから始める。

最低限:

  • name
  • description(「何をする」+「いつ使う」+「キーワード」)

禁止: description: | のようなマルチライン構文は使用しないこと。

Required sections (MUST)

  • Inputs
  • Outputs
  • Forbidden
  • Verification
  • Evidence (which files/dirs informed this)

Naming (MUST)

  • 小文字/数字/ハイフンのみ、64文字以内
  • 予約語や紛らわしい語を避ける(例: anthropic / claude を含めない)
  • 推奨: 一貫した命名パターン(公式は gerund: 動名詞形 “verb-ing” を推奨)

例(gerund):

  • testing-code
  • writing-documentation
  • managing-migrations

Guidance

  • 手順は「誰がやっても同じ」粒度で具体的に
  • 検証コマンドは repo に実在するものだけを書く