Saucebox Registry
← Browse

@infrasity-labs/card-sort-analysis

A

Analyze card sorting results to inform information architecture and navigation structure. Use after conducting open or closed card sort studies.

skillclaude

Install

agr install @infrasity-labs/card-sort-analysis --target claude

Writes 1 file into .claude/skills/, pinned to git-bb57520c.

  • .claude/skills/card-sort-analysis/SKILL.md

Document

name: card-sort-analysis description: Analyze card sorting results to inform information architecture and navigation structure. Use after conducting open or closed card sort studies.

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.

Trustgrade A

  • passBody integrity

    Whether the stored document is plausibly the kind of file the artifact declares, rather than something fetched by mistake.

  • passType matchnot applicable to this artifact type

    Whether the artifact is really the kind of thing its metadata claims it is.

  • passFreshness

    How long since the source repository was last pushed to.

  • passPrompt injection

    Scans the artifact's own text for instructions aimed at your agent rather than at you.

  • passLicense

    Whether the source repository declares an SPDX license permissive enough to redistribute.

How the grade is calculated

Each check contributes 0 points when it passes, 1 when it warns, and 2 when it fails. The total maps to a letter:

  • Aevery check passed
  • Bone warning
  • Ctwo warnings
  • Dprompt injection or body integrity failed, or three warnings
  • Fone of those failed, and something else is wrong

These are automated hygiene checks, not a security audit, and not a dependency or vulnerability scan. A grade of A means nothing was flagged — not that the artifact is safe.

Versions

  • git-bb57520cff182026-07-31