schemas
- Repo stars 330
- License MIT
- Author updated Live
- Author repo claude-skill-registry
- Domain
- Data
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 94 / 100 · audit passed
- Author / version / license
- @majiayu000 · MIT
- Token usage
- Lean
- Setup complexity
- Plug-and-play
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: schemas
description: YAML frontmatter schemas for Claude Code agents and commands. Use when creating or validating ag…
category: data
runtime: no special runtime
---
# schemas output preview
## PART A: Task fit
- Use case: YAML frontmatter schemas for Claude Code agents and commands. Use when creating or validating agent/command files. name: agent-name # Required: lowercase-with-hyphens runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Agent Frontmatter / Field Reference / Color Guidelines” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “YAML frontmatter schemas for Claude Code agents and commands. Use when creating or validating agent/command files. name: agent-name # Required: lowercase-with-hyphens runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Agent Frontmatter / Field Reference / Color Guidelines” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source does not require a stable slash command. After installation, invoke the skill by name and describe the task.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “Agent Frontmatter / Field Reference / Color Guidelines”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: schemas
description: YAML frontmatter schemas for Claude Code agents and commands. Use when creating or validating ag…
category: data
source: majiayu000/claude-skill-registry
---
# schemas
## When to use
- YAML frontmatter schemas for Claude Code agents and commands. Use when creating or validating agent/command files. nam…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “Agent Frontmatter / Field Reference / Color Guidelines” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "schemas" {
input -> user goal + target files + boundaries + acceptance criteria
context -> Agent Frontmatter / Field Reference / Color Guidelines
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}Frontmatter Schemas
Agent Frontmatter
---
name: agent-name # Required: lowercase-with-hyphens
description: | # Required: detailed with examples
Use this agent when [scenario]. Examples:
(1) "Task description" - launches agent for X
(2) "Task description" - launches agent for Y
(3) "Task description" - launches agent for Z
model: sonnet # Required: sonnet | opus | haiku
color: purple # Optional: purple | cyan | green | orange | blue | red
tools: TodoWrite, Read, Write # Required: comma-separated, space after comma
skills: skill1, skill2 # Optional: referenced skills
---Field Reference
| Field | Required | Values | Description |
|---|---|---|---|
name |
Yes | lowercase-with-hyphens |
Agent identifier |
description |
Yes | Multi-line string | 3-5 usage examples |
model |
Yes | sonnet, opus, haiku |
AI model to use |
color |
No | See colors below | Terminal color |
tools |
Yes | Tool list | Available tools |
skills |
No | Skill list | Referenced skills |
Color Guidelines
| Color | Agent Type | Examples |
|---|---|---|
purple |
Planning | architect, api-architect |
green |
Implementation | developer, ui-developer |
cyan |
Review | reviewer, designer |
orange |
Testing | test-architect, tester |
blue |
Utility | cleaner, api-analyst |
red |
Critical/Security | (rarely used) |
Tool Patterns by Agent Type
Orchestrators (Commands):
- Must have:
Task,TodoWrite,Read,Bash - Often:
AskUserQuestion,Glob,Grep - Never:
Write,Edit
Planners:
- Must have:
TodoWrite,Read,Write(for docs) - Often:
Glob,Grep,Bash
Implementers:
- Must have:
TodoWrite,Read,Write,Edit - Often:
Bash,Glob,Grep
Reviewers:
- Must have:
TodoWrite,Read - Often:
Glob,Grep,Bash - Never:
Write,Edit
Command Frontmatter
---
description: | # Required: workflow description
Full description of what this command does.
Workflow: PHASE 1 → PHASE 2 → PHASE 3
allowed-tools: Task, Bash # Required: comma-separated
skills: skill1, skill2 # Optional: referenced skills
---Field Reference
| Field | Required | Values | Description |
|---|---|---|---|
description |
Yes | Multi-line | Command purpose and workflow |
allowed-tools |
Yes | Tool list | Tools command can use |
skills |
No | Skill list | Referenced skills |
Validation Checklist
Agent Frontmatter
- Opening
---present -
nameis lowercase-with-hyphens -
descriptionincludes 3+ examples -
modelis valid (sonnet/opus/haiku) -
toolsis comma-separated with spaces - Closing
---present - No YAML syntax errors
Command Frontmatter
- Opening
---present -
descriptionexplains workflow -
allowed-toolsincludes Task for orchestrators - Closing
---present - No YAML syntax errors
Common Errors
Invalid YAML Syntax
# WRONG - missing colon
name agent-name
# CORRECT
name: agent-nameIncorrect Tool Format
# WRONG - no spaces after commas
tools: TodoWrite,Read,Write
# CORRECT
tools: TodoWrite, Read, WriteMissing Examples
# WRONG - too generic
description: Use this agent for development tasks.
# CORRECT
description: |
Use this agent when implementing TypeScript features. Examples:
(1) "Create a user service" - implements service with full CRUD
(2) "Add validation" - adds Zod schemas to endpoints
(3) "Fix type errors" - resolves TypeScript compilation issues
Decide Fit First
Design Intent
How To Use It
Boundaries And Review