authoring-skills

Structure SKILL.md files with progressive disclosure and discovery principles.

3|Updated Jan 30, 2026
One-click install
npx skills add https://github.com/lidessen/moniro --skill authoring-skills-lidessen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: authoring-skills
Source: https://github.com/lidessen/moniro/tree/main/skills/authoring-skills
Command: npx skills add https://github.com/lidessen/moniro --skill authoring-skills-lidessen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps authors design efficient, discoverable Agent Skills by enforcing progressive disclosure, concise explanations, and clear discovery signals.

Core Features & Use Cases

  • Provides the three core principles (Progressive Disclosure, Respect Intelligence, Enable Discovery) and how to apply them to SKILL.md, references, and tests.
  • Guides naming conventions, file organization, and testing strategies to improve discoverability and token efficiency.
  • Offers templates, patterns, and references for structuring multi-file skills or single-file SKILL.md.

Quick Start

To start, draft a concise SKILL.md frontmatter with name and description, place core workflow in SKILL.md, and move details to one or more reference files (one level deep). Keep SKILL.md under 500 lines and ensure references are clearly linked from SKILL.md.

Frequently Asked Questions about authoring-skills

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

FAQPage Schema
How do I structure an Agent Skill for token efficiency and predictable behavior?

Structure an Agent Skill by placing core workflows in SKILL.md and moving details to reference files one level deep. Keep SKILL.md under 500 lines and link references clearly to maximize token efficiency.

What is progressive disclosure in skill authoring and when should I apply it?

Progressive disclosure in skill authoring separates concise high-level logic from detailed references. Apply it by drafting a brief frontmatter and core workflow in SKILL.md, then moving granular details to linked reference files.

What are the best practices for naming and organizing multi-file skills?

Best practices for organizing multi-file skills involve using clear naming conventions, keeping SKILL.md concise with frontmatter, and storing details in one-level-deep reference files linked directly from the main SKILL.md.

Can I test Agent Skills to ensure discoverability and robust workflows?

Yes, you can test Agent Skills. The skill authoring guide specifies testing strategies to validate discoverability, clear discovery signals, and predictable Claude behavior within your structured SKILL.md and references.

Are there limitations to how much content I should put in a SKILL.md file?

Yes, SKILL.md files should be kept under 500 lines. Exceeding this limit reduces token efficiency and hinders predictable Claude behavior, so you must move excess details into linked reference files.