skill-authoring

Standardize authoring and auditing of COC skill units with SKILL.md frontmatter.

Updated Oct 10, 2025
One-click install
npx skills add https://github.com/FFOO6866/lead2cash --skill skill-authoring-ffoo6866
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-authoring
Source: https://github.com/FFOO6866/lead2cash/tree/main/.claude/skills/skill-authoring
Command: npx skills add https://github.com/FFOO6866/lead2cash --skill skill-authoring-ffoo6866

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It standardizes how skills are authored so they activate reliably via short, failure-mode-focused descriptions and include enough guidance to answer common questions without extra reads.

Core Features & Use Cases

  • Semantic activation guidance: Enforces a ≤200 character description that uses failure-mode language (and avoids keyword-dump patterns that reduce visibility).
  • Authoring conventions: Documents naming alignment, progressive disclosure (80/20 coverage), and how to index sub-files so they’re loaded on demand.
  • Cross-CLI parity: Explains how CLI-specific overlays work and how to keep skill bodies neutral so different readers can interpret them consistently.

Quick Start

Use this skill to audit an existing .claude/skills/<name>/SKILL.md for description-length, progressive-disclosure coverage, and tool-contract accuracy before you add or refactor sub-topics.

Frequently Asked Questions about skill-authoring

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

FAQPage Schema
How do I write skill descriptions that activate correctly across different CLI tools?

Skill descriptions activate correctly when they use failure-mode language within a 200-character limit and maintain neutral cross-CLI prose, avoiding keyword-dump patterns that reduce visibility.

What is progressive disclosure in skill authoring and how does it work?

Progressive disclosure in skill authoring is an 80/20 coverage strategy that indexes sub-files so they load on demand, answering common questions without extra reads.

How do I audit an existing SKILL.md file for frontmatter validation and tool-contract accuracy?

Audit an existing SKILL.md by checking its frontmatter for a valid name and description, verifying progressive-disclosure coverage, and ensuring the tools contract matches all referenced sub-file content.

Why does my skill fail to activate when the description is too long or uses keyword dumps?

Semantic activation fails when the SKILL.md description exceeds 200 characters or uses keyword-dump patterns instead of failure-mode language, reducing its visibility and matching reliability.

Can I use CLI-specific overlays while keeping the skill body neutral for cross-CLI parity?

Cross-CLI parity is maintained by keeping skill bodies neutral so different readers interpret them consistently, while explaining how CLI-specific overlays work for environment-specific interpretation.

What are the limitations of using progressive disclosure for sub-file indexing in skill authoring?

Progressive disclosure limitations require accurate tools contracts matching all referenced sub-file content, meaning incomplete sub-file indexing or mismatched tool references will break on-demand loading.