write-a-skill

Create structured ytsejam skill directories with SKILL.md frontmatter and optional resources.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/bketelsen/ytsejam --skill write-a-skill-bketelsen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-skill
Source: https://github.com/bketelsen/ytsejam/tree/main/contrib/skills/write-a-skill
Command: npx skills add https://github.com/bketelsen/ytsejam --skill write-a-skill-bketelsen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Create and maintain well-structured agent skills by defining a standardized skeleton (SKILL.md) with optional resources (scripts, references, assets) and a clear workflow for drafting, reviewing, and deploying new skills.

Core Features & Use Cases

  • Enforces a consistent skill layout including a minimal SKILL.md frontmatter and optional support files.
  • Guides the creation process from drafting to review, with templates and structure for references and scripts.
  • Use cases include teams building new skills for ytsejam, documenting capabilities, and packaging reusable components.

Quick Start

Create a new skill directory named after the capability and include a SKILL.md with name and description.

Frequently Asked Questions about write-a-skill

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

FAQPage Schema
How do I create a well-structured agent skill with proper frontmatter?

To create an agent skill, set up a directory with a SKILL.md file containing required name and description frontmatter, plus optional scripts, references, and assets folders for bundled resources.

What is the required structure for a SKILL.md file?

A SKILL.md file requires frontmatter with a name and description to capture the capability and triggers. Optional directories like scripts, references, and assets can organize support files.

What's the best way to organize scripts and references when building agent skills?

Organize scripts and references into optional dedicated directories within the skill folder. This structure keeps bundled resources separate from the SKILL.md metadata and ensures repeatable packaging.

Can I use templates to guide the skill creation process from drafting to review?

Yes, using a repeatable template for drafting and review ensures the skill metadata captures capabilities, triggers, and organizational structure consistently while packaging reusable components.

Do I need any dependencies to build and maintain agent skills?

No dependencies are required to build agent skills. You only need to define a standardized SKILL.md skeleton with optional support files to establish a clear workflow for drafting and deploying.