create-skill

Create SKILL.md files with YAML frontmatter and optional components.

1|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/ag3nt3154/Driverless_AGI --skill create-skill-ag3nt3154
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/ag3nt3154/Driverless_AGI/tree/main/.dagi/skills/create-skill
Command: npx skills add https://github.com/ag3nt3154/Driverless_AGI --skill create-skill-ag3nt3154

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Creating consistent, reusable SKILL.md entries is tedious without a standard template; this skill automates the creation of correctly structured SKILL.md files so future agents can reuse learned workflows.

Core Features & Use Cases

  • Enforces YAML frontmatter containing at minimum a name and description to enable discovery.
  • Supports both built-in and project-specific skill locations.
  • Detects optional component directories (scripts, references, assets) and records them for loading.

Quick Start

Create a new SKILL.md in the appropriate skills directory using the frontmatter structure shown above.

Frequently Asked Questions about create-skill

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

FAQPage Schema
How do I create a reusable SKILL.md file for future agents?

To create a reusable SKILL.md file, you provide a YAML frontmatter containing at least a name and description, followed by a thorough body. This standardizes how skills are defined and discovered by agents.

What is YAML frontmatter and why is it needed for skill discovery?

YAML frontmatter is a metadata block at the top of a SKILL.md file that must contain at least a name and description. It enables agents to discover, validate, and load skills for reuse.

Can I use optional triggers and components when authoring a SKILL.md file?

Yes, you can use optional triggers in the frontmatter and record optional components like scripts, references, and assets. Components are detected based on their directory presence during skill authoring.

Does skill authoring support both built-in and project-specific locations?

Skill authoring supports both built-in and project-specific skill locations. This allows you to standardize workflows globally or keep generated SKILL.md files scoped to a single project.

What is the best way to standardize how agents discover and load skills?

The best way to standardize skill discovery is generating correctly structured SKILL.md files with validated YAML frontmatter. This ensures future agents can consistently discover, load, and reuse learned workflows.