skill-creator

Generates SKILL.md frontmatter and standard directory structure for AI skill projects.

1|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/phar-dev/phardev.dot --skill skill-creator-phar-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/phar-dev/phardev.dot/tree/main/opencode/.config/opencode/skills/skill-creator
Command: npx skills add https://github.com/phar-dev/phardev.dot --skill skill-creator-phar-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the scaffolding of new AI agent skills by generating SKILL.md frontmatter and standard directory structure, enabling consistent creation across projects.

Core Features & Use Cases

  • Template-driven SKILL.md: Produces complete frontmatter and structured guidance for new skills.
  • Project scaffolding: Creates the standard directory layout (skills/{skill-name}, assets/, references/) for quick onboarding.
  • Policy and convention enforcement: Ensures naming, licensing, metadata, and structure align with the Agent Skills spec.

Quick Start

Create a new skill named "my-skill" and run the skill-creator workflow to generate SKILL.md and its supporting folders.

Frequently Asked Questions about skill-creator

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

FAQPage Schema
How do I scaffold new AI agent skills with standard directory structures?

Scaffolding new AI agent skills involves generating a standardized SKILL.md file with complete frontmatter and a consistent directory layout. This approach creates the necessary folders for assets and references to ensure quick onboarding across multiple projects.

What is the best way to enforce frontmatter completeness and metadata rules across multiple projects?

Enforcing frontmatter completeness relies on template-driven generation that aligns with the Agent Skills spec. This method ensures naming, licensing, and metadata conventions are automatically satisfied during project scaffolding.

Do I need to manually create the folders for assets and references when creating project structures?

Manually creating folders for assets and references is unnecessary when using project scaffolding automation. The workflow automatically generates the standard directory layout, including the specific skill folder and its supporting subdirectories.

Can I use template-driven scaffolding to ensure licensing and naming conventions align with the Agent Skills spec?

Template-driven scaffolding ensures licensing and naming conventions align with the Agent Skills spec by applying policy enforcement. This standardizes metadata generation and validates structural completeness for every new skill created.