progressive-disclosure

progressive-disclosure is a skill for Claude Code from oborchers/fractional-cto. It costs 60 tokens per session (686 once invoked), scanned A, original, MIT.

A set of design guidance for revealing product features gradually during onboarding and other first-use screens. It explains how to keep simple tasks clear while making advanced options available later.

In plain words
What is it for?
Use it to design or review onboarding flows, empty states, progress checklists, signup forms, product tours, and first-run experiences.
Why use it?
It helps prevent new users from being overwhelmed by too many choices at once. It also addresses common first-run problems such as long signup forms and slow time to value.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the saas-design-principles plugin — 13 skills, 1 command, 1 agent shipped together

Good fit Use it to design or review onboarding flows, empty states, progress checklists, signup forms, product tours, and first-run experiences.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/oborchers/fractional-cto/progressive-disclosure
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add oborchers/fractional-cto --skill progressive-disclosure
Clone the repo
git clone --depth 1 https://github.com/oborchers/fractional-cto

Made for: Claude Code.

Or install saas-design-principles, the plugin that ships this one along with the rest of its 13 skills, 1 command, 1 agent.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for progressive-disclosure

README.md
[![agentmods](https://agentmods.dev/badge/skills/oborchers/fractional-cto/progressive-disclosure/github.svg)](https://agentmods.dev/skills/oborchers/fractional-cto/progressive-disclosure)
Your own site
<a href="https://agentmods.dev/skills/oborchers/fractional-cto/progressive-disclosure"><img src="https://agentmods.dev/badge/skills/oborchers/fractional-cto/progressive-disclosure/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for progressive-disclosure

Your own site · 80×15
<a href="https://agentmods.dev/skills/oborchers/fractional-cto/progressive-disclosure"><img src="https://agentmods.dev/badge/skills/oborchers/fractional-cto/progressive-disclosure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 686 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00060 $0.00686
Opus 5.5 $0.00024 $0.00274
Sonnet 5.5 $0.00012 $0.00137
Haiku 4.5 $0.00006 $0.00069

Measured 5d ago against content hash 4ca3223edc8d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

progressive-disclosure scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

saas-design-principles/skills/progressive-disclosure/SKILL.md · 69 lines

How it starts

The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Reveal Complexity Progressively

Nielsen defined progressive disclosure in 2006: defer advanced or rarely used features to a secondary screen, making applications easier to learn and less error-prone. This improves learnability, efficiency of use, and error rate.

The Two-Level Limit

Never go beyond two levels of disclosure. Usability drops rapidly at three or more levels because users get lost navigating between them. If a settings panel requires three levels of nesting, the design needs simplification, not more progressive disclosure.

Linear's philosophy: "Simple first, then powerful." Intercom's principle: "Simple and opinionated by default, progressively reveal power and flexibility."

Onboarding

Onboarding is progressive disclosure applied to time. The data is stark: 40–60% of signup users never return after their first experience. Every extra minute in time-to-value lowers conversion by approximately 3%.

Signup

  • Limit to 3 fields maximum — every extra field costs roughly 7% conversion
  • Frame additional questions as personalization, not interrogation
  • Example: Notion asks "What will you use this for?" to customize the experience

Product Tours

  • 3–5 steps maximum
  • Always include a skip button
  • Focus on one critical action rather than explaining every feature
  • Users are 4.5x more likely to complete a second tour if they complete the first one — make the first tour excellent and brief

Checklists

Checklists work because of the Zeigarnik effect — the psychological need to complete unfinished tasks.

Rules:

  • Start the progress bar at 20%, not 0%
  • Keep checklists to 3–5 items
  • Nest them directly in the product, not floating on top
  • Tie items to real user actions that demonstrate value, not arbitrary feature exploration

Empty States

Empty states are the most underrated onboarding surface. Notion fills its empty first-use state with educational content that doubles as a checklist.

Every empty state needs three things:

  1. Context explaining why it is empty
  2. A single clear call-to-action
  3. Reassurance that nothing is broken

Read the full file on GitHub · 69 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 69 lines · 60 tokens per session scan A 4ca3223edc8d

Subscribe to this mod's changes

progressive-disclosure is a skill published in the GitHub repository oborchers/fractional-cto (32 stars, last pushed 5d ago), licensed MIT. It adds 60 tokens to every session and 686 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-13.

Related

Other skills, from other repositories

Art

Static visual content across 20+ formats — diagrams, mermaid, infographics, D3 dashboards, comics, icons, wallpaper — via Nano Banana Pro (default), Nano Banana, and Flux. USE WHEN art, illustration, diagram, flowchart, infographic, header image, blog social thumbnail, visualize, generate image, mermaid, architecture…

danielmiessler/LifeOS · 124 tokens

Webdesign

Design and integrate web interfaces via three paths: DirectDesign (write design inline with Anthropic frontend-design philosophy — the default workhorse), native /design + /design-sync Claude Code commands (preferred for code integration and design-system sync), or ClaudeDesign (drive claude.ai/design through…

danielmiessler/LifeOS · 134 tokens

ApertureOscillation

3-pass scope oscillation that holds a question constant while shifting zoom — narrow/tactical, wide/strategic, then synthesis — to surface design tensions, scope recommendations, and coherence assessments invisible at any single zoom level. USE WHEN aperture oscillation, oscillate scope, zoom in and out, tactical vs…

danielmiessler/LifeOS · 102 tokens

Tldraw

Read, create, and edit tldraw .tldr canvas files deterministically — sketch hand-drawn-register diagrams (boxes, arrows, sticky notes, frames, text) directly into a canvas file the user opens in any tldraw surface, and read a rough canvas back as structured data to organize it. USE WHEN tldraw, .tldr file, whiteboard…

danielmiessler/LifeOS · 156 tokens

learn

Runs a six-phase research workflow from source bundle to publish-ready output. Use when researching an unfamiliar domain or compiling materials into one reference. Not for quick lookups or single-file reads.

tw93/Waza · 39 tokens

build-product-and-tool-interfaces

A guide for designing and building complete interfaces for products and professional tools that people use repeatedly to change objects and reach checkable results. It covers workbenches, task workflows, editing tools, analysis tools, monitoring consoles, and file or asset processors.

EverMind-AI/Raven · 147 tokens