skill-progressive-disclosure-design SKILL.md skillA
skill-progressive-disclosure-design from samber/cc-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add samber/cc-skills/skill-progressive-disclosure-design@v1.0.1Pins v1.0.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- samber/cc-skills
- Path
skills/skill-progressive-disclosure-design/SKILL.md- Versions recorded
- 2
- Latest version
- v1.0.1, committed Sep 2, 2026
- First version recorded
- Apr 30, 2026
- Size
- 17,095 bytes
- Repository stars
- 242
- License
- MIT
Decide how to split skill content between SKILL.md and reference files for context efficiency and reliable triggering. Use this whenever creating a new Claude skill, refactoring an existing one, or when a SKILL.md is growing past 300-400 lines. Also trigger when the user mentions "progressive disclosure", "reference files", "splitting skills", "skill bundling", "context window for skills", "SKILL.md too long", "what goes in references/", "skill structure", or expresses any uncertainty about…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Skill Progressive Disclosure Design Each section that recommends a direction includes explicit pros and cons. The decisions in this skill are trade-offs, not rules. The model using this skill should reason from the trade-offs to the user's specific situation rather than apply rules blindly. ## Triggering vs. disclosure: separate these first Two problems get conflated and need separating before any splitting decision. **Triggering** is whether Claude invokes the skill at all. Driven entirely by the YAML `description`. File splitting does not affect triggering. If the question is "my skill doesn't trigger reliably", do not split files, fix the description (use `run_loop.py` from the `skill-creator` skill). **Progressive disclosure** is what loads after the skill activates. SKILL.md body always loads. `references/*` only loads when SKILL.md tells the model to read a specific file. `scripts/*` executes without loading into context at all. This is where context protection happens. If the user is asking about splitting because of triggering issues, surface the confusion first and redirect. ## Default: do not split A monolithic SKILL.md beats a split one until proven otherwise. …
Read the whole file at its exact version.
How to install
mdr add samber/cc-skills/skill-progressive-disclosure-design@sha256:3184d1f636e20b4dThe line at the top of this page pins the label v1.0.1, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_z62l5hvjzxzronik)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Apr 30, 2026 and Sep 2, 2026, about one every 125 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.1 latest | 2026-09-02 | f866b80 | 17,095 B | A | view · diff |
| v1.0.0 | 2026-04-30 | 75f2f00 | 17,101 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (17095 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
samber/cc-skills · 242 stars · license MIT · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_z62l5hvjzxzronik GET https://markdownregistry.com/api/v1/resolve?ref=samber/cc-skills/skill-progressive-disclosure-design GET https://markdownregistry.com/api/v1/blob/3184d1f636e20b4d113ffc35941e7fe317af92df7aee5156666220b4ed8c79b9
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.