Create New Skills

Create new Agent Skills with structured SKILL.md frontmatter and optional resources.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/qdhenry/Foundry-OSS --skill create-new-skills-qdhenry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Create New Skills
Source: https://github.com/qdhenry/Foundry-OSS/tree/main/.agents/skills/meta-skill
Command: npx skills add https://github.com/qdhenry/Foundry-OSS --skill create-new-skills-qdhenry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating new Agent Skills efficiently by codifying best practices, templates, and guidance into a standard Skill structure that Codex can load on demand.

Core Features & Use Cases

  • Structured Skill format: A Skill directory with SKILL.md frontmatter and optional supporting files (scripts, references, assets) that Codex loads progressively.
  • Frontmatter enforcement: Requiring name and description to enable discovery and consistent metadata.
  • Workflow templates: Guided steps to craft, test, and publish new Skills for team reuse.

Quick Start

Create a Skill directory, add SKILL.md with proper frontmatter, and include any optional resources to support the workflow.

Frequently Asked Questions about Create New Skills

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

FAQPage Schema
How do I create a new Agent Skill for Codex?

To create an Agent Skill, set up a Skill directory and add a SKILL.md file with required frontmatter metadata like name and description, then include optional scripts, references, or assets to support the workflow.

What is progressive disclosure in Agent Skills?

Progressive disclosure in Agent Skills is a content organization pattern where Codex loads structured SKILL.md frontmatter and supporting files like scripts, references, and assets on demand to efficiently manage context.

What frontmatter is required for an Agent Skill?

Required frontmatter for an Agent Skill includes the name and description fields, which enable proper discovery and consistent metadata loading by Codex.

What's the best way to structure a Skill directory for team reuse?

The best way to structure a Skill directory for reuse is to codify domain knowledge into a SKILL.md with proper frontmatter, and organize supporting scripts, references, and assets using guided workflow templates.

Can I include optional resources when building a Skill?

Yes, you can include optional resources when building a Skill by adding supporting files such as scripts, references, and assets alongside the mandatory SKILL.md file to enhance the workflow.

Why do I need frontmatter enforcement in SKILL.md?

Frontmatter enforcement in SKILL.md is needed to mandate name and description fields, ensuring consistent metadata structure that enables reliable discovery and on-demand loading by Codex.