create

Create reusable Claude Code skills and agents with YAML frontmatter metadata.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/mgsystemsdev/POD --skill create-mgsystemsdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create
Source: https://github.com/mgsystemsdev/POD/tree/main/agent-system-base/.claude/skills/create
Command: npx skills add https://github.com/mgsystemsdev/POD --skill create-mgsystemsdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines capturing repeatable workflows as reusable skills and agents, enabling faster automation and consistent outcomes across projects.

Core Features & Use Cases

  • Decision-driven creation: automatically choose between Skill or Agent based on conversational signals.
  • Global vs Project scope: assign artifacts to global user space or project-specific namespaces and tooling.
  • Metadata-first workflow: generate YAML frontmatter, structured descriptions, and trigger rules for easy discovery and reuse.
  • Output validation: ensures SKILL.md contains required fields and conforms to the Skill Unit definition.

Quick Start

Define a new skill or agent by populating SKILL.md with frontmatter (name, description) and a descriptive body.

Frequently Asked Questions about create

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create reusable skills and agents for Claude Code?

You create reusable Claude Code skills and agents by defining a SKILL.md file with structured YAML frontmatter and a descriptive body. This process analyzes conversational context to automatically decide whether to generate a skill or an agent, enforcing metadata standards for consistent automation outcomes.

What is the difference between a global scope and project scope when generating Claude Code agents?

Global scope assigns generated artifacts and tooling to the global user space, while project scope confines them to project-specific namespaces. The creation workflow determines this scope automatically based on conversational signals and context to ensure proper tool availability.

How does YAML frontmatter validation work for Claude Code skills?

YAML frontmatter validation ensures your SKILL.md file contains required fields like name, description, and allowed-tools, conforming to the Skill Unit definition. It generates and validates these structured metadata fields to enable easy discovery and reuse across automation workflows.

Do I need to manually specify allowed-tools when creating a skill?

You do not need to manually specify allowed-tools when creating a skill. The workflow determines required tools based on conversational context, automatically generating and validating the allowed-tools field within the YAML frontmatter for your SKILL.md file.

What is the best way to capture repeatable workflows as reusable automation?

The best way to capture repeatable workflows as reusable automation is using a metadata-first workflow that generates structured YAML frontmatter, descriptions, and trigger rules. This streamlines consistent outcomes by orchestrating skill and agent structures directly from conversations.

Why does my SKILL.md file fail validation during agent creation?

SKILL.md validation fails during agent creation when required YAML frontmatter fields like name, description, or allowed-tools are missing or non-compliant. The creation process enforces these standards to ensure your artifact conforms to the Skill Unit definition for proper discovery.