Agent skill

YAML Agent Format

by MadAppGang in MadAppGang/claude-code

YAML format for Claude Code agent definitions as alternative to markdown.

MITAuto-check passedDocuments & Office

Install YAML Agent Format

skills CLI
$ npx skills add MadAppGang/claude-code --skill yaml-agent-format -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install MadAppGang/claude-code yaml-agent-format --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/MadAppGang/claude-code.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/agentdev/skills/yaml-agent-format .claude/skills/yaml-agent-format && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
yaml-agent-format
GitHub stars
285
Token cost
~4.8k tokens
SKILL.md length
721 words
Files
1
Skills in repo
69
Repo updated
First seen
Licence
MIT

At a glance

YAML format for Claude Code agent definitions as alternative to markdown.

  • Works in 4 steps: Extract frontmatter YAML as base → Parse XML-style tags to nested objects → Convert numbered lists to arrays → …
  • Creating agents with YAML
  • SKILL.md covers Overview, YAML Agent Schema, YAML vs Markdown Comparison and Conversion Patterns, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

YAML Agent Format is an agent skill from MadAppGang/claude-code. YAML format for Claude Code agent definitions as alternative to markdown. Use when creating agents with YAML, converting markdown agents to YAML, or validating YAML agent schemas. Trigger keywords - "YAML agent", "agent YAML", "YAML format", "agent schema", "YAML definition", "convert to YAML".

Its SKILL.md is about 4.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Documents & Office, covering Markdown. The repository describes itself as: claude code plugins marketplace. The licence is MIT.

When your agent uses it

  • Creating agents with YAML
  • Converting markdown agents to YAML
  • Validating YAML agent schemas
  • Keywords - YAML agent

Example prompts

  • “YAML agent”
  • “agent YAML”
  • “YAML format”
  • “/yaml-agent-format”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Extract frontmatter YAML as base
  2. Parse XML-style tags to nested objects
  3. Convert numbered lists to arrays
  4. Flatten markdown formatting to plain strings

What it can do on your machine

Read from SKILL.md and the folder at commit 6097ad4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml, markdown, typescript, bash and json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

YAML Agent Format loads about 4.8k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 721 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~78
When it runs · the whole SKILL.md, loaded when a task matches
~4.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from MadAppGang/claude-code at commit 6097ad4, republished under its MIT licence (© MadAppGang). 721 words, ~4,843 tokens.

Download SKILL.mdSave it as .claude/skills/yaml-agent-format/SKILL.md (or your agent's skills folder).
name
yaml-agent-format
description
YAML format for Claude Code agent definitions as alternative to markdown. Use when creating agents with YAML, converting markdown agents to YAML, or validating YAML agent schemas. Trigger keywords - "YAML agent", "agent YAML", "YAML format", "agent schema", "YAML definition", "convert to YAML".
version
0.1.0
tags
agentdev, yaml, agent, format, schema, definition
keywords
yaml, agent, format, schema, definition, conversion, validation, frontmatter
plugin
agentdev
updated
2026-01-28

YAML Agent Format

Overview

Why YAML for Agents?

YAML provides an alternative format for defining Claude Code agents with several advantages:

Benefits:

  • Machine-parseable: Easy to validate, transform, and generate programmatically
  • Less verbose: No markdown headers, cleaner structure
  • Schema validation: Strong typing with JSON Schema or Zod
  • Tooling support: Better IDE autocomplete, linting, formatting
  • Data-first: Natural for configuration management

Trade-offs:

  • Less readable: Markdown is better for long-form documentation
  • Indentation-sensitive: YAML whitespace can be error-prone
  • No rich formatting: Can't use markdown tables, code blocks in descriptions
When to Use YAML vs Markdown

Use YAML when:

  • Generating agents programmatically
  • Agent definitions are data-heavy (many examples, tools, rules)
  • You need strong schema validation
  • Agent is simple and concise
  • Working in automation/CI pipelines

Use Markdown when:

  • Agent has extensive documentation needs
  • You want rich formatting (tables, diagrams, code examples)
  • Agent is tutorial-like with explanations
  • Human readability is priority
  • Agent includes narrative instructions
Compatibility with Claude Code

YAML agents are fully compatible with Claude Code:

  • Placed in agents/ directory with .agent.yaml extension
  • Registered in plugin.json identically to markdown agents
  • Loaded and executed the same way
  • Can mix YAML and markdown agents in same plugin

YAML Agent Schema

Complete Schema Definition
yaml
# Required fields
name: string                    # Agent name (kebab-case)
description: string             # Brief description (1-2 sentences)
version: string                 # Semver version (e.g., "1.0.0")

# Optional but recommended
role:
  identity: string              # Agent's role/identity
  expertise: string[]           # List of expertise areas
  mission: string               # Primary mission statement

tools: string[]                 # Available tools (Read, Write, Edit, Bash, etc.)

instructions:
  constraints: string[]         # Critical constraints/rules
  workflow:                     # Step-by-step workflow
    - phase: string             # Phase name
      objective: string         # Phase objective
      steps: string[]           # List of steps

knowledge:                      # Knowledge base entries
  - topic: string               # Knowledge topic
    content: string             # Knowledge content

examples:                       # Usage examples
  - name: string                # Example name
    user: string                # User message
    assistant: string           # Assistant response

formatting:
  style: string                 # Communication style
  templates:                    # Output templates
    success: string
    error: string
Field Details

Required Fields:

  • name: Agent identifier (must match filename without extension)
  • description: Shown in agent list, used for agent selection
  • version: Semver for tracking changes

Role Section:

  • identity: Who the agent is (e.g., "React Component Builder")
  • expertise: Array of skills (e.g., ["React 19", "TypeScript", "Testing"])
  • mission: What the agent does (e.g., "Build production-ready React components")

Tools Array: Standard Claude Code tools:

yaml
tools:
  - Read
  - Write
  - Edit
  - Bash
  - Glob
  - Grep

Workflow Structure:

yaml
instructions:
  workflow:
    - phase: "Phase 1: Discovery"
      objective: "Find relevant files"
      steps:
        - "Use Glob to find components"
        - "Use Grep to search for patterns"
        - "Read existing implementations"

YAML vs Markdown Comparison

Simple Agent: Side-by-Side

Markdown (simple-agent.md):

markdown
---
name: simple-agent
description: A simple example agent
version: 1.0.0
---

<role>
  <identity>Code Formatter</identity>
  <mission>Format code files according to standards</mission>
</role>

<instructions>
  1. Read the file
  2. Format using appropriate tool
  3. Write back to file
</instructions>

YAML (simple-agent.agent.yaml):

yaml
name: simple-agent
description: A simple example agent
version: 1.0.0

role:
  identity: Code Formatter
  mission: Format code files according to standards

instructions:
  workflow:
    - phase: Format
      steps:
        - Read the file
        - Format using appropriate tool
        - Write back to file
Complex Agent: Side-by-Side

Markdown (react-builder.md):

markdown
---
name: react-builder
description: Build React components with tests
version: 2.1.0
---

<role>
  <identity>React Component Builder</identity>
  <expertise>
    - React 19 with TypeScript
    - React Testing Library
    - Component patterns
  </expertise>
</role>

<instructions>
  <workflow>
    <phase number="1" name="Create Component">
      <steps>
        <step>Create component file with TypeScript types</step>
        <step>Implement component logic</step>
      </steps>
    </phase>
  </workflow>
</instructions>

<examples>
  <example name="Button Component">
    <user>Create a button component</user>
    <assistant>I'll create Button.tsx with props...</assistant>
  </example>
</examples>

YAML (react-builder.agent.yaml):

yaml
name: react-builder
description: Build React components with tests
version: 2.1.0

role:
  identity: React Component Builder
  expertise:
    - React 19 with TypeScript
    - React Testing Library
    - Component patterns

instructions:
  workflow:
    - phase: "Phase 1: Create Component"
      steps:
        - Create component file with TypeScript types
        - Implement component logic

examples:
  - name: Button Component
    user: Create a button component
    assistant: I'll create Button.tsx with props...

Key Difference: YAML is ~30% shorter for structured data.


Conversion Patterns

Markdown to YAML Conversion

Conversion Rules:

  1. Extract frontmatter YAML as base
  2. Parse XML-style tags to nested objects
  3. Convert numbered lists to arrays
  4. Flatten markdown formatting to plain strings

Example Conversion:

Input (Markdown):

markdown
---
name: test-agent
version: 1.0.0
---

<role>
  <identity>Tester</identity>
  <expertise>
    - Unit testing
    - Integration testing
  </expertise>
</role>

<instructions>
  <constraints>
    - Always write tests first
    - Use TypeScript
  </constraints>
</instructions>

Output (YAML):

yaml
name: test-agent
version: 1.0.0

role:
  identity: Tester
  expertise:
    - Unit testing
    - Integration testing

instructions:
  constraints:
    - Always write tests first
    - Use TypeScript
YAML to Markdown Conversion

Conversion Rules:

  1. Create frontmatter from top-level fields
  2. Convert nested objects to XML-style tags
  3. Convert arrays to markdown lists
  4. Wrap in appropriate markdown structure

Example Conversion:

Input (YAML):

yaml
name: docs-agent
version: 1.0.0
role:
  identity: Documentation Writer
  mission: Create comprehensive docs

Output (Markdown):

markdown
---
name: docs-agent
version: 1.0.0
---

<role>
  <identity>Documentation Writer</identity>
  <mission>Create comprehensive docs</mission>
</role>
Automated Conversion Tools

TypeScript Conversion Function:

typescript
import yaml from 'yaml';
import { z } from 'zod';

// Convert markdown agent to YAML
function markdownToYaml(markdownPath: string): string {
  const content = fs.readFileSync(markdownPath, 'utf-8');

  // Extract frontmatter
  const frontmatterMatch = content.match(/^---\n([\s\S]*?)\n---/);
  const frontmatter = yaml.parse(frontmatterMatch?.[1] || '');

  // Parse XML-like tags
  const role = extractRoleSection(content);
  const instructions = extractInstructionsSection(content);

  const agent = {
    ...frontmatter,
    role,
    instructions
  };

  return yaml.stringify(agent);
}

// Convert YAML agent to markdown
function yamlToMarkdown(yamlPath: string): string {
  const content = fs.readFileSync(yamlPath, 'utf-8');
  const agent = yaml.parse(content);

  const { name, description, version, role, instructions, ...rest } = agent;

  let md = `---\n${yaml.stringify({ name, description, version })}---\n\n`;

  if (role) {
    md += `<role>\n${objectToXml(role)}</role>\n\n`;
  }

  if (instructions) {
    md += `<instructions>\n${objectToXml(instructions)}</instructions>\n\n`;
  }

  return md;
}

Validation

Schema Validation with Zod

Define Zod Schema:

typescript
import { z } from 'zod';

const AgentSchema = z.object({
  name: z.string().regex(/^[a-z0-9-]+$/),
  description: z.string().min(10).max(200),
  version: z.string().regex(/^\d+\.\d+\.\d+$/),

  role: z.object({
    identity: z.string(),
    expertise: z.array(z.string()).optional(),
    mission: z.string()
  }).optional(),

  tools: z.array(z.enum([
    'Read', 'Write', 'Edit', 'Bash', 'Glob', 'Grep'
  ])).optional(),

  instructions: z.object({
    constraints: z.array(z.string()).optional(),
    workflow: z.array(z.object({
      phase: z.string(),
      objective: z.string().optional(),
      steps: z.array(z.string())
    })).optional()
  }).optional(),

  examples: z.array(z.object({
    name: z.string(),
    user: z.string(),
    assistant: z.string()
  })).optional()
});

// Validate YAML agent
function validateAgent(yamlPath: string): boolean {
  const content = fs.readFileSync(yamlPath, 'utf-8');
  const agent = yaml.parse(content);

  try {
    AgentSchema.parse(agent);
    return true;
  } catch (error) {
    console.error('Validation failed:', error);
    return false;
  }
}
Common Validation Errors

1. Invalid Name Format:

yaml
# BAD
name: "My Agent"  # Spaces not allowed

# GOOD
name: my-agent

2. Missing Required Fields:

yaml
# BAD - missing version
name: test-agent
description: Test agent

# GOOD
name: test-agent
description: Test agent
version: 1.0.0

3. Invalid Semver:

yaml
# BAD
version: "1.0"  # Not semver

# GOOD
version: "1.0.0"

4. Invalid Tool Names:

yaml
# BAD
tools:
  - ReadFile  # Wrong name

# GOOD
tools:
  - Read
  - Write

5. Incorrect Array Format:

yaml
# BAD
expertise: Unit testing, Integration testing

# GOOD
expertise:
  - Unit testing
  - Integration testing
Validation Tools

CLI Validator:

bash
# Create validation script
cat > validate-agent.ts <<'EOF'
#!/usr/bin/env bun
import { AgentSchema } from './agent-schema';
import yaml from 'yaml';

const file = process.argv[2];
const content = await Bun.file(file).text();
const agent = yaml.parse(content);

const result = AgentSchema.safeParse(agent);
if (result.success) {
  console.log('✓ Valid agent definition');
} else {
  console.error('✗ Validation errors:');
  result.error.issues.forEach(issue => {
    console.error(`  - ${issue.path.join('.')}: ${issue.message}`);
  });
  process.exit(1);
}
EOF

chmod +x validate-agent.ts

# Usage
./validate-agent.ts agents/my-agent.agent.yaml

File Naming

YAML Agent Naming Convention

Format: {agent-name}.agent.yaml

Examples:

  • code-reviewer.agent.yaml
  • react-builder.agent.yaml
  • test-generator.agent.yaml

Rules:

  • Use .agent.yaml extension (not .yaml or .yml)
  • Name must match the name field in YAML
  • Use kebab-case for names
  • Place in agents/ directory
Show full SKILL.md (283 more words)Show less
Directory Structure
plugin-name/
├── agents/
│   ├── builder.agent.yaml       # YAML agent
│   ├── reviewer.md              # Markdown agent
│   └── tester.agent.yaml        # YAML agent
├── plugin.json
└── README.md
Plugin.json Registration

Register YAML agents identically to markdown agents:

json
{
  "name": "my-plugin",
  "version": "1.0.0",
  "agents": [
    {
      "name": "builder",
      "file": "agents/builder.agent.yaml",
      "description": "Build components"
    },
    {
      "name": "reviewer",
      "file": "agents/reviewer.md",
      "description": "Review code"
    }
  ]
}

Note: Claude Code detects format from file extension.


Best Practices

Do
  • Use YAML for data-heavy agents with many examples
  • Validate YAML syntax before committing
  • Keep descriptions concise (YAML has no rich formatting)
  • Use consistent indentation (2 spaces recommended)
  • Add comments for complex sections
  • Version agents with semver
  • Test agent loading after creation
Don't
  • Don't mix tabs and spaces in YAML
  • Don't use YAML for agents with extensive documentation
  • Don't forget required fields (name, description, version)
  • Don't use complex YAML features (anchors, aliases) - keep it simple
  • Don't embed long code examples (use markdown for that)
  • Don't use special characters in names without quoting
When YAML is Better

YAML excels for:

  • Agents with many structured examples
  • Programmatic agent generation
  • Configuration-heavy agents
  • Agents used in automation
  • Simple, data-focused agents
  • Agents needing strong validation

Example use case:

yaml
# API endpoint agent with 20+ examples
name: api-endpoint-generator
examples:
  - name: GET endpoint
    user: Create GET /users
    assistant: "..."
  - name: POST endpoint
    user: Create POST /users
    assistant: "..."
  # 18 more examples...
When Markdown is Better

Markdown excels for:

  • Agents with extensive tutorials
  • Agents with rich formatting needs
  • Agents requiring code examples with syntax highlighting
  • Agents with diagrams or tables
  • Human-focused documentation
  • Narrative instructions

Example use case:

markdown
## Complex Workflow Explanation

This agent follows a sophisticated workflow...

| Phase | Duration | Tools |
|-------|----------|-------|
| Discovery | 5 min | Grep, Glob |

```typescript
// Example implementation
const component = buildComponent();

---

## Examples

### Example 1: Simple Code Formatter

**File:** `agents/formatter.agent.yaml`

```yaml
name: formatter
description: Format code files according to project standards
version: 1.0.0

role:
  identity: Code Formatter
  mission: Ensure consistent code formatting across the project

tools:
  - Read
  - Write
  - Bash

instructions:
  constraints:
    - Always backup files before formatting
    - Use project-specific formatter configuration
    - Preserve file permissions

  workflow:
    - phase: Read and Analyze
      objective: Understand file and detect language
      steps:
        - Read the target file
        - Detect programming language from extension
        - Check for project formatter config

    - phase: Format
      objective: Apply formatting
      steps:
        - Run appropriate formatter (prettier, black, gofmt)
        - Capture formatted output

    - phase: Write
      objective: Save formatted file
      steps:
        - Write formatted content back to file
        - Report formatting changes

formatting:
  style: Concise and direct
  templates:
    success: "Formatted {file} ({changes} changes)"
    error: "Failed to format {file}: {reason}"
Example 2: Complex React Component Builder

File: agents/react-builder.agent.yaml

yaml
name: react-builder
description: Build production-ready React components with TypeScript and tests
version: 2.1.0

role:
  identity: React Component Architect
  expertise:
    - React 19 with TypeScript
    - React Testing Library
    - Component composition patterns
    - Accessibility (a11y)
    - Performance optimization
  mission: Create maintainable, tested, accessible React components

tools:
  - Read
  - Write
  - Edit
  - Bash
  - Glob
  - Grep

instructions:
  constraints:
    - Always use TypeScript strict mode
    - Export component as named export
    - Include JSDoc comments for props
    - Follow project naming conventions
    - Add accessibility attributes

  workflow:
    - phase: "Phase 1: Discovery"
      objective: Understand existing patterns
      steps:
        - Use Glob to find similar components
        - Use Grep to search for patterns
        - Read component examples

    - phase: "Phase 2: Create Component"
      objective: Write component file
      steps:
        - Define TypeScript props interface
        - Implement component with hooks
        - Add error boundaries if needed
        - Include accessibility attributes

    - phase: "Phase 3: Create Tests"
      objective: Write comprehensive tests
      steps:
        - Create test file with RTL
        - Test rendering
        - Test user interactions
        - Test accessibility

    - phase: "Phase 4: Validate"
      objective: Run quality checks
      steps:
        - Run TypeScript compiler
        - Run tests
        - Check formatting

examples:
  - name: Button Component
    user: Create a button component with loading state
    assistant: |
      I'll create a Button component with TypeScript props and loading state.
      Creating Button.tsx with type-safe props and Button.test.tsx with RTL tests.

  - name: Form Input
    user: Build a form input with validation
    assistant: |
      Creating FormInput component with validation, error display, and accessibility.
      Including tests for validation logic and error states.

formatting:
  style: Professional and detailed
  templates:
    success: |
      Component created successfully:
      - {component}.tsx ({lines} lines)
      - {component}.test.tsx ({tests} tests)
      All quality checks passed.
Example 3: Conversion from Markdown

Before (Markdown):

markdown
---
name: test-generator
description: Generate tests for existing code
version: 1.0.0
---

<role>
  <identity>Test Generator</identity>
</role>

<instructions>
  1. Read source file
  2. Generate test cases
  3. Write test file
</instructions>

After (YAML):

yaml
name: test-generator
description: Generate tests for existing code
version: 1.0.0

role:
  identity: Test Generator

instructions:
  workflow:
    - phase: Generate Tests
      steps:
        - Read source file
        - Generate test cases
        - Write test file

Summary

YAML agents provide a cleaner, more structured alternative to markdown for agent definitions:

Key Benefits:

  • Machine-parseable with schema validation
  • Less verbose for structured data
  • Better tooling support (autocomplete, linting)
  • Ideal for programmatic generation

Use YAML when:

  • Agent is data-heavy (many examples, rules)
  • You need strong validation
  • Agent is simple and concise
  • Working in automation pipelines

Use Markdown when:

  • Agent has extensive documentation
  • You need rich formatting
  • Human readability is priority

Both formats are fully compatible with Claude Code and can be mixed within the same plugin.

© MadAppGang, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/agentdev/skills/yaml-agent-format of MadAppGang/claude-code.

Open the folder on GitHubat commit 6097ad4

Compare with similar skills

YAML Agent Format next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

YAML Agent Format compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
YAML Agent Format this skillMadAppGang/claude-code285—~4.8kAutomated safety check: PassMIT
Fix Broken Linkschef/chef-web-docs143—~3.2kAutomated safety check: PassCustom licence
Dile Docs PagesPolydile/dile-components106—~2.8kAutomated safety check: PassMIT
Write Documentdigital-go-jp/design-system-example-components-html115—~3.1kAutomated safety check: PassMIT
Markdown FixerCommunity-Access/accessibility-agents423—~1.6kAutomated safety check: PassMIT
Publish Skillglebis/claude-skills391—~4.1kAutomated safety check: PassMIT

Similar skills

  • Fix Broken Links

    chef/chef-web-docs

    Run linkchecker against a locally served site, a deployed URL, or a local HTML build output, parse the errors, map each broken link back to its Markdown source file, suggest replacement URLs, and…

    143 GitHub stars~3.2k tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • Dile Docs Pages

    Polydile/dile-components

    A skill your agent uses when creating or updating a Markdown documentation page of the Dile Components Eleventy site under docs/ — especially component pages in docs/components/.md, but also…

    106 GitHub stars~2.8k tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • Write Document

    digital-go-jp/design-system-example-components-html

    コンポーネントのMDXドキュメントを作成・更新する

    115 GitHub stars~3.1k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed
  • Markdown Fixer

    Community-Access/accessibility-agents

    Internal helper: apply approved markdown fixes, surface judgment calls.

    423 GitHub stars~1.6k tokensUpdated 17 days ago
    Documents & OfficeAuto-check passed
  • Publish Skill

    glebis/claude-skills

    This skill should be used when publishing a new or updated skill to the claude-skills-site Astro website.

    391 GitHub stars~4.1k tokensUpdated 2 days ago
    Documents & OfficeAuto-check passed
  • Fern Components

    ai-dynamo/dynamo

    Knowledge of Fern's built-in MDX component library (accordions, callouts, cards, steps, tabs, code blocks, API-reference snippets, and more) for authoring docs pages.

    8.3k GitHub stars~2.8k tokensUpdated today
    Documents & OfficeAuto-check passed

More from MadAppGang/claude-code

All 69 skills in this repo
  • Content Brief

    MadAppGang/claude-code

    Content brief template and creation methodology for SEO-optimized content.

    285 GitHub starsUsed in 1 repo~959 tokens
    Auto-check passed
  • Context Detection

    MadAppGang/claude-code

    A skill your agent uses when detecting project technology stack from files/configs/directory structure, auto-loading framework-specific skills, or analyzing multi-stack fullstack projects (e.g…

    285 GitHub stars~5.4k tokensUpdated 6 mo ago
    Auto-check passed
  • Content Optimizer

    MadAppGang/claude-code

    On-page SEO optimization techniques including keyword density, meta tags, heading structure, and readability.

    285 GitHub starsUsed in 1 repo~694 tokens
    Auto-check passed
  • Keyword Cluster Builder

    MadAppGang/claude-code

    Techniques for expanding seed keywords and clustering by topic and intent.

    285 GitHub starsUsed in 1 repo~674 tokens
    Auto-check passed
  • Serp Analysis

    MadAppGang/claude-code

    SERP analysis techniques for intent classification, feature identification, and competitive intelligence.

    285 GitHub starsUsed in 1 repo~1k tokens
    Auto-check passed
  • Agent Coordination Discipline

    MadAppGang/claude-code

    A skill your agent uses when deciding whether to launch an agent, selecting which agent to use, or coordinating multiple agents.

    285 GitHub stars~3.8k tokensUpdated 6 mo ago
    Auto-check passed

Questions about YAML Agent Format

What does YAML Agent Format do?

YAML format for Claude Code agent definitions as alternative to markdown. YAML Agent Format is an agent skill from MadAppGang/claude-code. YAML format for Claude Code agent definitions as alternative to markdown.

When should I use YAML Agent Format?

YAML Agent Format fits situations like: creating agents with YAML; converting markdown agents to YAML; validating YAML agent schemas; keywords - YAML agent.

How do I install YAML Agent Format in Claude Code?

Run `npx skills add MadAppGang/claude-code --skill yaml-agent-format -a claude-code`. Or copy the skill folder (plugins/agentdev/skills/yaml-agent-format in MadAppGang/claude-code) into .claude/skills/yaml-agent-format in your project. Claude Code loads it when a task matches its description.

How do I install YAML Agent Format in Codex?

Run `npx skills add MadAppGang/claude-code --skill yaml-agent-format -a codex`. Or copy the skill folder (plugins/agentdev/skills/yaml-agent-format in MadAppGang/claude-code) into .agents/skills/yaml-agent-format in your project. Codex loads it when a task matches its description.

Can I use YAML Agent Format in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add MadAppGang/claude-code --skill yaml-agent-format -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/yaml-agent-format, .gemini/skills/yaml-agent-format, .github/skills/yaml-agent-format and .opencode/skills/yaml-agent-format in your project.

What does YAML Agent Format need to run?

SKILL.md names no scripts, command-line tools or credentials: YAML Agent Format is instructions for the agent only.

Does YAML Agent Format access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is YAML Agent Format safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does YAML Agent Format use?

YAML Agent Format is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does YAML Agent Format use?

About 4.8k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to YAML Agent Format?

Skills that share tags, products or a category with YAML Agent Format: Fix Broken Links (chef/chef-web-docs, 143 stars), Dile Docs Pages (Polydile/dile-components, 106 stars), Write Document (digital-go-jp/design-system-example-components-html, 115 stars) and Markdown Fixer (Community-Access/accessibility-agents, 423 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains YAML Agent Format?

MadAppGang (a GitHub organization) maintains it in MadAppGang/claude-code, which has 285 GitHub stars. The repository holds 69 skills in this directory. The repository was last updated on March 15, 2026.

Source: MadAppGang/claude-code on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.