create-skill

Guide developers in creating structured QoderWork Skills with SKILL.md templates.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/FeatherHunter/StudyNotes --skill create-skill-featherhunter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/FeatherHunter/StudyNotes/tree/main/.qoder/skills/create-skill
Command: npx skills add https://github.com/FeatherHunter/StudyNotes --skill create-skill-featherhunter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams to consistently craft well-structured Agent Skills for QoderWork by enforcing a standard SKILL.md frontmatter and a repeatable file layout.

Core Features & Use Cases

  • Provides a clear template for SKILL.md frontmatter (name, description, version) and recommended directory structure (SKILL.md, optional scripts/references/assets).
  • Documents best practices for progressive disclosure, one-level deep references, and concise, third-person descriptions to improve discoverability and reusability.
  • Supports a step-by-step Skill creation workflow (Discovery, Design, Implementation, Verification) to help new and existing skills stay aligned with standards.

Quick Start

Follow the SKILL.md guidelines to create a new Skill by defining its name, description, and directory structure.

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 well-structured SKILL.md template for QoderWork?

To create a SKILL.md template for QoderWork, define standard frontmatter fields like name, description, and version, then establish a repeatable directory structure with optional scripts, references, and assets to ensure consistency across teams.

What is progressive disclosure in skill design and when should I use it?

Progressive disclosure in skill design is a best practice that structures SKILL.md content to reveal complexity incrementally. Use it to improve discoverability and reusability by keeping descriptions concise and limiting references to one level deep.

What's the best way to structure a skill creation workflow for a development team?

The best way to structure a skill creation workflow is to follow a four-step process: Discovery, Design, Implementation, and Verification. This ensures new and existing skills stay aligned with frontmatter standards, directory layouts, and validation guidelines.

Do I need frontmatter validation guidelines when building new skills?

Yes, frontmatter validation guidelines are required when building new skills. Enforcing the presence of fields like name and description ensures that skills remain discoverable, properly structured, and compatible with QoderWork standards.

Can I use optional components like scripts and references in a skill repository layout?

Yes, you can include optional components such as scripts, references, and assets in your skill repository layout. These components support the SKILL.md file and extend functionality without violating the prescribed directory structure standards.

Why does my skill discovery fail when descriptions are not written in third person?

Skill discovery fails when descriptions are not concise or written in third person because the system relies on standardized metadata for indexing. Adhering to the recommended third-person format improves searchability and ensures proper alignment with best practices.