Generate quick-reference cards for any insight-wave plugin. Use this skill whenever the user asks for a cheatsheet, cheat sheet, quick reference, summary of a plugin, "commands for cogni-X", "tldr cogni-X", "what does cogni-X do", "remind me how to use cogni-X", or wants a compact overview of a plugin's capabilities without taking a full course. Also trigger when a user needs a refresher on a plugin they've used before but can't remember the exact commands or concepts.
From cogni-helpnpx claudepluginhub cogni-work/insight-wave --plugin cogni-helpThis skill is limited to using the following tools:
evals/evals.jsonDispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
Generate concise, one-screen reference cards for any insight-wave plugin. Faster than reading docs or taking a course — designed for users who need a quick refresher.
Read the workspace language from .workspace-config.json in the workspace root
(language field — "en" or "de"). Write cheatsheet descriptions, concept
explanations, and pattern guidance in that language.
If the file is missing or unreadable, detect the user's language from their message. If still unclear, default to English.
Keep in English regardless of language setting:
cogni-trends, cogni-narrative, etc.)/cheatsheet, /workflow, etc.)Command, What it does)Identify the plugin from the user's request. Accept plugin names with or
without the cogni- prefix ("tips" = "cogni-trends").
Read the plugin's key files:
<plugin>/README.md — overview, components, data model<plugin>/.claude-plugin/plugin.json — name, description, version<plugin>/skills/*/SKILL.md — skill descriptions (frontmatter only, not full body)<plugin>/commands/*.md — available commands (frontmatter only)Generate the cheatsheet using this exact template:
# <Plugin Name> Cheatsheet (v<version>)
<One-line description>
## Commands
| Command | What it does |
|---------|-------------|
| /command-1 | Brief description |
| /command-2 | Brief description |
## Core Concepts
- **Concept 1**: One-sentence explanation
- **Concept 2**: One-sentence explanation
- **Concept 3**: One-sentence explanation
## Data Model
<Key files/state the plugin creates and where they live>
## Common Patterns
1. Pattern name — when and how to use it
2. Pattern name — when and how to use it
## Related Plugins
- **cogni-X**: How it connects (feeds into / requires / complements)
- **cogni-Y**: How it connects
## Learn More
Full guide: docs/plugin-guide/<plugin-name>.md | Course: /teach <course-number>
docs/plugin-guide/<plugin>.md exists, link to
it. Also include the corresponding /teach course number from the curriculum
(e.g., cogni-trends = Course 4, cogni-portfolio = Course 6).When /cheatsheet is invoked with no argument, list all available plugins with
a one-line description and suggest the user pick one. Use the plugin catalog from
the guide skill (../guide/references/plugin-catalog.md) for the list.