Revealing AI capability gradually to match user mental models.
Scanned 5/28/2026
Install via CLI
openskills install Owl-Listener/ai-design-skills---
name: progressive-disclosure
description: Revealing AI capability gradually to match user mental models.
---
# Progressive Disclosure
Users don't understand what AI can do. Progressive disclosure is how you reveal capabilities at the right pace — preventing both overwhelm and underuse.
## The Mental Model Gap
Users arrive with mental models shaped by previous technology. They may:
- Treat the AI like a search engine (keyword queries)
- Treat it like a form (expecting rigid structure)
- Underestimate what it can do (asking for less than it offers)
- Overestimate what it can do (expecting perfection)
Progressive disclosure bridges the gap between what users think the AI does and what it actually does.
## Disclosure Strategies
- **On-demand hints**: Show capability suggestions contextually ("Did you know you can also ask me to...")
- **Escalating examples**: Start with simple use cases, reveal complex ones as the user gains confidence
- **Feature graduation**: Unlock advanced features after the user demonstrates comfort with basics
- **Contextual teaching**: When the user attempts something inefficiently, show a better approach
- **Capability boundaries**: Clearly communicate what the AI cannot do, not just what it can
## Layered Capability Revelation
Structure capabilities in layers:
1. **Surface layer**: The most obvious, lowest-risk capabilities. Users discover these immediately.
2. **Intermediate layer**: More powerful features revealed through tooltips, suggestions, or first-use prompts.
3. **Power layer**: Advanced capabilities for experienced users — available but not promoted.
## Pacing
- **Too fast**: Users feel overwhelmed, ignore capabilities, or lose trust
- **Too slow**: Users get bored, think the product is limited, churn
- **Just right**: Each new capability feels like a natural next step
## Design Artefacts
- Capability disclosure maps showing what's revealed when
- Mental model progression diagrams
- First-use experience flows with disclosure triggers
- Capability tier definitions (surface, intermediate, power)
No comments yet. Be the first to comment!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Interview, source-challenge, verify, save, and ADR-gate fuzzy coding requests into Codex-ready implementation specs. Use when a feature, bugfix, refactor, migration, repo-wide change, or architecture task needs user-verified requirements, source-backed decisions, durable architecture decisions, acceptance criteria, validation commands, rollout notes, saved spec/ADR files, and a Codex execution prompt. Do not use when already fully specified or when the user wants direct implementation now.
Use when a repo needs CodeGraph plus ast-grep for Codex MCP setup, exploration, impact analysis, structural search, or safe refactor planning.