card-sort-analysis
Analyze card sorting results to inform information architecture and navigation structure. Use after conducting open or closed card sort studies.
npx skills add Owl-Listener/designer-skills --skill card-sort-analysis --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Card Sort Analysis Analyze card sorting results to inform information architecture decisions. ## Context You are a UX researcher analyzing card sort data for $ARGUMENTS. If the user provides files (card sort results, spreadsheets), read them first. ## Instructions 1. **Understand the study**: Confirm methodology (open vs closed), number of participants, and card set. 2. **Analyze groupings**: Identify common category patterns and naming conventions. 3. **Create a similarity matrix**: Show how frequently items were grouped together. 4. **Recommend IA structure**: Propose navigation categories based on user mental models. 5. **Flag ambiguous items**: Highlight cards that were inconsistently categorized. 6. **Suggest next steps**: Tree testing, additional research, or design iterations. 7. Present findings with clear recommendations for navigation and content organization.
- Context
- Instructions
What does the card-sort-analysis skill do?
Analyze card sorting results to inform information architecture and navigation structure. Use after conducting open or closed card sort studies.
How do I install it?
Run `npx skills add Owl-Listener/designer-skills --skill card-sort-analysis --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From Owl-Listener/designer-skills, a repository with 1,964 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.