skill-design

Defines/enforces a Skill Design blueprint for creating, evaluating and reusing AI skills.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/chkim-su/skillmaker --skill skill-design-chkim-su
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-design
Source: https://github.com/chkim-su/skillmaker/tree/main/skills/skill-design
Command: npx skills add https://github.com/chkim-su/skillmaker --skill skill-design-chkim-su

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Designing effective AI skills can be complex, leading to inefficient context usage, unreliable execution, or poor discoverability. This Skill provides a comprehensive guide to building high-quality, production-ready skills that are robust, efficient, and easy to use.

Core Features & Use Cases

  • Skill Anatomy & Types: Understand the structure of a skill, including scripts/, references/, and assets/, and choose between Knowledge, Hybrid, or Tool skills based on task complexity and fragility.
  • Progressive Disclosure: Optimize context usage by structuring SKILL.md and leveraging references for on-demand information loading.
  • Tool Restrictions & Trigger Phrases: Learn to define appropriate tool access and craft effective trigger phrases for automatic skill activation.
  • Use Case: When creating a new skill for "PDF processing," use this skill to determine whether it should be a "Tool Skill" (due to deterministic file manipulation), how to structure its scripts/ and references/ directories, and what trigger phrases to include in its description.

Quick Start

To get best practices for structuring a new skill, ask: Explain the different types of skills and when to use scripts, references, or assets.

Frequently Asked Questions about skill-design

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

FAQPage Schema
What's the best way to structure a new AI skill for consistent quality?

Structure skills using a standard blueprint: YAML front matter, a concise SKILL.md (<500 words), and optional scripts/, references/, and assets/ directories. This ensures scalable, composable skills that use context efficiently and execute reliably across Knowledge, Hybrid, Tool, and Expert skill types.

How do I choose between Knowledge, Hybrid, and Tool skills?

Select skill type based on task complexity and fragility. Knowledge skills handle static information; Hybrid skills combine information with scripting; Tool skills manage deterministic file manipulation or external integrations. Match the type to your task's data dependencies and execution requirements.

How does progressive disclosure optimize context usage in skills?

Progressive disclosure structures SKILL.md with essential content inline and loads detailed information on-demand via references. This reduces upfront context overhead while keeping advanced details accessible, improving both performance and user experience.

What's the purpose of trigger phrases in skill design?

Trigger phrases enable automatic skill activation by matching user intent. Craft them to reflect the core task vocabulary—file formats, operations, and workflows—so the skill activates when users need it without manual selection.

How do I define tool restrictions for a skill?

Map allowed tools in the skill's configuration to control what external integrations and file operations are available. This prevents unintended access, reduces execution risks, and ensures the skill operates safely within intended boundaries.

What artifacts are required to build a production-ready skill?

Production skills require YAML front matter for metadata, SKILL.md documentation (core sections under 500 words), tool-permission mapping, cross-linking conventions, and optional scripts, references, and assets. This standardized blueprint ensures discoverability and reusability.