_skills

Define portable Skill Unit frameworks for .claude/skills/ definitions with YAML frontmatter.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/HahyeonJeon/gobbi --skill skills-hahyeonjeon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: _skills
Source: https://github.com/HahyeonJeon/gobbi/tree/main/plugins/gobbi/skills/_skills
Command: npx skills add https://github.com/HahyeonJeon/gobbi --skill skills-hahyeonjeon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reference and guide for creating skill definitions to ensure consistent structure, frontmatter rules, and navigation across .claude/skills/ files.

Core Features & Use Cases

  • Central reference for skill anatomy (SKILL.md), optional child docs, and verification guidance.
  • Guidance on frontmatter fields (name, description, allowed-tools) and the naming conventions.
  • Rules for description-driven loading, hierarchy, and project boundaries, plus Gotcha guidance.
  • Verification patterns and the Expected Output when authoring new skills.

Quick Start

Review this guide to begin authoring a new skill in .claude/skills/.

Frequently Asked Questions about _skills

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

FAQPage Schema
How do I structure a Claude skill definition in .claude/skills/?

Claude skill definitions require a YAML frontmatter containing name, description, and allowed-tools, paired with a flat documentation structure using SKILL.md and optional subdocs to ensure consistent loading and navigation.

What is the required frontmatter for authoring a Claude skill?

Required frontmatter for Claude skill authoring includes the name, description, and allowed-tools fields within a YAML block, which dictates how the skill is discovered and loaded across project boundaries.

How does Claude load optional subdocs and assets within a skill?

Claude uses description-driven loading to fetch optional subdocs and assets directories as needed, maintaining a flat hierarchy within the .claude/skills/ directory to load relevant documentation dynamically.

Are there specific naming conventions or gotchas when creating Claude skills?

Claude skill authoring involves specific naming conventions for frontmatter fields and project boundaries, alongside documented gotchas to prevent common structural errors and ensure proper skill verification.

What verification patterns should I use when reviewing Claude skills?

Skill verification patterns involve checking the expected output against the defined frontmatter and flat documentation structure, ensuring the SKILL.md and optional subdocs conform to the portable Skill Unit framework.

Can I modify existing Claude skill definitions across different projects?

Yes, the Skill Unit framework is portable and applies to creating, reviewing, or modifying any .claude/skills/ definitions across projects, ensuring consistent frontmatter and navigation patterns regardless of the scenario.