Schemas

Organization

MadAppGang

schemas

YAML frontmatter schemas for Claude Code agents and commands. Use when creating or validating agent/command files.

Overview

Publisher	MadAppGang
Repository	`claude-code`
Skill name	`schemas`
Stars	281
Forks	26
Bundled files	Instructions only
License	MIT
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by MadAppGang on GitHub. Read the source before you install it.

Installation

Install the Schemas AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/MadAppGang/claude-code.git /tmp/claude-code
mkdir -p .claude/skills
cp -r /tmp/claude-code/plugins/agentdev/skills/schemas .claude/skills/schemas

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Schemas in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Schemas on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Schemas is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

plugin: agentdev updated: 2026-01-20

Frontmatter Schemas

Agent Frontmatter

yaml
---
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: TaskCreate, TaskUpdate, TaskList, TaskGet, 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, TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Bash
Often: AskUserQuestion, Glob, Grep
Never: Write, Edit

Planners:

Must have: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write (for docs)
Often: Glob, Grep, Bash

Implementers:

Must have: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write, Edit
Often: Bash, Glob, Grep

Reviewers:

Must have: TaskCreate, TaskUpdate, TaskList, TaskGet, Read
Often: Glob, Grep, Bash
Never: Write, Edit

Command Frontmatter

yaml
---
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

Command Frontmatter

Opening --- present
description explains workflow
allowed-tools includes Task, TaskCreate, TaskUpdate, TaskList, TaskGet for orchestrators
Closing --- present
No YAML syntax errors

Common Errors

Invalid YAML Syntax

yaml
# WRONG - missing colon
name agent-name

# CORRECT
name: agent-name

Incorrect Tool Format

yaml
# WRONG - no spaces after commas
tools: TaskCreate, TaskUpdate, TaskList, TaskGet,Read,Write

# CORRECT
tools: TaskCreate, TaskUpdate, TaskList, TaskGet, Read, Write

Missing Examples

yaml
# 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

Frequently asked questions

What does the Schemas AI skill do?

YAML frontmatter schemas for Claude Code agents and commands. Use when creating or validating agent/command files.

Why use Schemas on TypingMind?

Because you install it once and use it with any model. Schemas is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Schemas in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/MadAppGang/claude-code/tree/main/plugins/agentdev/skills/schemas. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Schemas?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Schemas?

As many as you like. As long as a model supports skills, you can use Schemas with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Schemas AI skill free?

Yes. It is published on GitHub by MadAppGang under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Brainstorming

obra

CommunityPopular

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Executing Plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Using Superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

Loop Me

Grill me about specs for the workflows I want to build, within this workspace.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Frontmatter Schemas

Agent Frontmatter

Field Reference

Color Guidelines

Tool Patterns by Agent Type

Command Frontmatter

Field Reference

Validation Checklist

Agent Frontmatter

Command Frontmatter

Common Errors

Invalid YAML Syntax

Incorrect Tool Format

Missing Examples

Frequently asked questions

Related AI Skills

Set up your own AI workspace now