本文へ移動
cccskills
無料GitHub で公開

skill-builder

Create Agent Skills with best practices, structure, validation, and testing. Use when designing or refining skills, prompts, references, or supporting files.

インストール方法を見る

含まれるファイル(2)

  • SKILL.md2.2 KB
  • references/skill-builder-guide.md10.4 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Skill Builder

Create, validate, and refine Agent Skills.

Quick Start

  1. Gather the capability, triggers, and required domain knowledge.
  2. Choose a simple single-file skill or a multi-file skill with references.
  3. Write SKILL.md with concise, trigger-focused instructions.
  4. Add reference files only for detail that would otherwise bloat SKILL.md.
  5. Validate YAML frontmatter, file layout, and naming.
  6. Test the skill with the natural language users are likely to say.

Workflow

  • Start with requirements and scope control.
  • Design the structure before writing content.
  • Keep descriptions in third person and include trigger keywords.
  • Use progressive disclosure for long examples, templates, and validation details.

Gates

Follow in order. Pass means a check you can satisfy with concrete artifacts (written bullets, paths, line counts, parsed YAML)—not an internal sense of “done.”

  1. Requirements — Pass: Capability, triggers, and any required domain knowledge (or explicit “none”) are written down or confirmed from the user.
  2. Structure — Pass: Single-file vs SKILL.md + references/ is chosen; heavy detail lives in references, not inlined in SKILL.md.
  3. Draft — Pass: Frontmatter is valid YAML with name and description; SKILL.md is ≤ 500 lines; every relative link from SKILL.md resolves to a path that exists under this skill directory; each allowed-tools entry (if present) is justified.
  4. Trigger check — Pass: At least one natural-language user phrase plausibly matching the description is identified for a quick invocation test.

Validation

  • Keep SKILL.md under 500 lines.
  • Prefer one-level reference links.
  • Avoid time-sensitive guidance.
  • Confirm frontmatter is valid YAML.
  • Check that any allowed-tools entries are necessary and correct.

Advanced Reference

For the full workflow, templates, examples, and validation checklist, see references/skill-builder-guide.md.

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Use when you need to mine a conversation, session transcript, or design discussion for architectural decisions before writing ADRs. Identifies problem-solution pairs, trade-off debates, technology choices, and explicit "[ADR]" tags. Triggers on "what decisions did we make", "extract decisions from this chat", "find the choices in our discussion", or "summarize architectural decisions". Also useful after long planning sessions to capture decisions that were made implicitly. Does NOT write ADR documents — use adr-writing or write-adr for that.

日本語の概要は準備中です。原文の説明を表示しています。

existential-birds/beagle822026年9月16日 更新

Use when writing or formatting an ADR document using the MADR template, applying Definition of Done (E.C.A.D.R.) criteria, or verifying ADR completeness. Triggers on "write the ADR", "format as MADR", "check ADR quality", "mark gaps in ADR". Also triggers when a decision has been extracted and needs to become a document. Does NOT extract decisions from conversations (use adr-decision-extraction) or orchestrate the full extract-confirm-write workflow (use write-adr).

日本語の概要は準備中です。原文の説明を表示しています。

existential-birds/beagle822026年9月16日 更新

Use when auditing an agent codebase against the 12-Factor Agents methodology, reviewing LLM-powered system architecture, or assessing agentic app compliance. Triggers on "analyze agent architecture", "12-factor audit", "how compliant is this agent", or "evaluate this LLM app". Also applies when comparing frameworks or planning agent improvements. Not for quick checklists — this performs deep per-factor codebase analysis with file-level evidence.

日本語の概要は準備中です。原文の説明を表示しています。

existential-birds/beagle822026年9月16日 更新

Vercel AI Elements for workflow UI components. Use when building chat interfaces, displaying tool execution, showing reasoning/thinking, or creating job queues. Triggers on ai-elements, Queue, Confirmation, Tool, Reasoning, Shimmer, Loader, Message, Conversation, PromptInput.

日本語の概要は準備中です。原文の説明を表示しています。

existential-birds/beagle822026年9月16日 更新

Reviews App Intents code for intent structure, entities, shortcuts, and parameters. Use when reviewing code with import AppIntents, @AppIntent, AppEntity, AppShortcutsProvider, or @Parameter.

日本語の概要は準備中です。原文の説明を表示しています。

existential-birds/beagle822026年9月16日 更新

Use when the user wants a cited, structured read of local documents and project knowledge. Triggers on: "analyze these docs", "scan my project for context", "read the docs folder", "summarize what's in .beagle/concepts/", "extract context from docs/", "what's in this folder", "go read everything in X and tell me what's there". Also invoked programmatically by other beagle skills (prfaq-beagle Ignition, brainstorm-beagle reference points, strategy-interview context grounding) via the companion contract. Does NOT trigger on codebase lookups ("find this function", "search the repo"), web research (use web-research), LLM-as-judge evaluation (use llm-judge), or document editing (use humanize-beagle). Produces a written scan plan, parallel-subagent findings, and a cited synthesis report on disk — never inline prose, never unsourced claims.

日本語の概要は準備中です。原文の説明を表示しています。

existential-birds/beagle822026年9月16日 更新

existential-birds のスキルをすべて見る

このスキルの問題を報告する