cm-skill-index

Load skills through three progressive disclosure layers to reduce token usage.

48|23|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/tody-agent/codymaster --skill cm-skill-index
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cm-skill-index
Source: https://github.com/tody-agent/codymaster/tree/main/skills/cm-skill-index
Command: npx skills add https://github.com/tody-agent/codymaster --skill cm-skill-index

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Progressive Disclosure accelerates discovery by avoiding full-skill loads, dramatically reducing token usage during skill selection.

Core Features & Use Cases

  • Layer 1: Skill index (name, domain, triggers, 100-token summary) always loaded for fast matching.
  • Layer 2: Skill summary (description, use cases, integration notes) loaded when context requires a closer look.
  • Layer 3: Full SKILL.md loaded only during execution, enabling full instruction execution with minimal upfront cost.
  • Use Case: A large catalog of skills can be scanned quickly; detailed validation happens only for the chosen candidate.

Quick Start

Start by enabling Layer 1 discovery and progressively enable Layer 2 and Layer 3 as you decide to execute a skill.

Frequently Asked Questions about cm-skill-index

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

FAQPage Schema
How do I reduce token waste when loading a large catalog of LLM skills?

Progressive disclosure reduces token waste by indexing skills in a three-layer system, loading only minimal 100-token summaries for initial discovery instead of full skill files. It scopes discovery to quick matching and defers full loads until execution.

What is progressive disclosure for skill discovery and how does it work?

Progressive disclosure is a layered skill loading mechanism that works by maintaining a Layer 1 index of names and triggers, a Layer 2 summary for context validation, and a Layer 3 full SKILL.md file loaded only at execution time to minimize upfront token cost.

How do I implement layered loading to save LLM memory during skill selection?

Implement layered loading by enabling Layer 1 discovery first, then progressively loading Layer 2 context summaries and Layer 3 full instructions only after choosing a candidate skill. This prevents loading unnecessary execution details during scanning.

Can I scan a large skill catalog without loading the full SKILL.md for every item?

Yes, you can scan a large catalog using Layer 1 data, which requires only about 100 tokens per skill for fast matching. Layer 2 data uses roughly 300 tokens for closer validation, ensuring full SKILL.md files are never loaded until execution.

Does progressive skill indexing work for validating context before execution?

Progressive skill indexing validates context using Layer 2 data, which includes descriptions, use cases, and integration notes. This ensures the chosen candidate matches requirements before loading the Layer 3 full SKILL.md at execution time.

What is the best way to structure skill metadata for token-efficient discovery?

The best way to structure skill metadata for token-efficient discovery is a three-layer format: Layer 1 holds 100-token summaries for indexing, Layer 2 contains 300-token context details, and Layer 3 stores the full SKILL.md for execution.