AGENT SKILLS · MISSION KIT
Useful agent skills ranked by real adoption
Browse verified skills from public repositories. Compare what each skill does, package contents, install activity, and source evidence before adding it to your agent.
- CATALOG SCOPE
- VERIFIED
- skills
- 22,787
- repositories
- 3507
- last synced
- Nov 1, 2026
owl-listenercard-sort-analysis
Analyse open or closed card sort results into a proposed grouping and label set. Use after running a sort study. For turning that evidence into a full structure, use information-architecture (ux-strategy).
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenercase-study
Craft a portfolio case study with narrative arc, process evidence, and outcomes. Use when telling a project's story to an external audience. For an internal stakeholder deck, use presentation-deck.
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenerclick-test-plan
Design first-click and click tests for findability and navigation. Use when testing whether people can locate something. For full task-based observation, use test-scenario.
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenercompetitive-analysis
Compare UX patterns, features, strengths, and gaps across rival products. Use when you need to know what others actually do. For deliberately adopting their conventions, use jakobs-law (interaction-design).
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenercomponent-spec
Specify one component — props, states, variants, accessibility, and usage rules. Use when defining a library component. For the reusable doc scaffold use documentation-template; for a problem-solution pattern use pattern-library.
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenercontent-strategy
Define what content a product needs, how it is structured, and who owns it. Use when content itself is the problem. For the words in the interface use ux-writing (designer-toolkit); for structural hierarchy use information-architecture.
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenercritique-color
Critique a rendered screen's colour — contrast ratios, palette coherence, and semantic meaning. Use when reviewing one screen. For a product-wide WCAG audit use accessibility-audit (design-systems); for building the palette use color-system (ui-design).
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenercritique-typography
Critique a rendered screen's typography — scale usage, readability, consistency, and token compliance. Use when reviewing type on a screen. For defining the scale itself, use typography-scale (ui-design).
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenercritique-visual-hierarchy
Critique a rendered screen's hierarchy — entry point, eye flow, weight distribution, and emphasis. Use when attention lands in the wrong place. For establishing hierarchy in new work, use visual-hierarchy (ui-design).
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenerdesign-critique
Facilitate a structured team critique — framing, feedback rules, and actionable outcomes. Use when running a session with people in the room. For a solo expert review, use heuristic-evaluation (prototyping-testing).
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenerdesign-debt-audit
Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use design-token-audit (designer-toolkit); for WCAG gaps use accessibility-audit (design-systems).
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenerdesign-negotiation
Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use business-design (ux-strategy).
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenerdesign-qa-checklist
Build a QA checklist for verifying that a build matches the design. Use at implementation review. For the spec engineers build from, use handoff-spec.
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenerdesign-rationale
Write rationale connecting decisions to user needs, business goals, and principles. Use when a decision needs defending in writing. For a live conversation, use design-negotiation.
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenerdesign-sprint-plan
Plan and facilitate a design sprint from challenge framing through prototype testing. Use when compressing discovery into days. For ongoing team cadence, use team-workflow.
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenerdesign-system-governance
Define how the system evolves — contribution model, versioning, deprecation, and change management. Use when multiple teams contribute. For driving uptake use design-system-adoption (designer-toolkit); for design file history use version-control-strategy (design-ops).
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenerdesign-token-audit
Audit token usage across a product for coverage, drift, and hard-coded values. Use when tokens exist and you suspect they are being bypassed. For defining tokens in the first place, use design-token (design-systems).
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenerdiary-study-plan
Design a diary study — prompts, cadence, duration, participant criteria, and analysis frame. Use when behaviour unfolds over days or weeks. For a single-session study, use usability-test-plan.
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenerfitts-law
Apply Fitts's Law — target acquisition time depends on size and distance. Use when sizing and positioning controls, especially for touch. For how many controls to show at once, use hicks-law.
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenergesture-patterns
Design gesture interactions for touch and pointer — swipe, drag, long-press, and their discoverability. Use when input is gestural. For OS-standard gestures on iOS and Android, use platform-conventions (ui-design).
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenerhandoff-spec
Write the implementation handoff — measurements, behaviours, assets, states, and edge cases. Use when engineering picks up the work. For verifying the result afterwards use design-qa-checklist; for reusable library components use component-spec (design-systems).
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenericon-system
Specify an icon system — grid, sizing, stroke weight, naming, categories, and implementation. Use when standardising iconography. For broader illustration, use illustration-style (ui-design).
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenerillustration-style
Define an illustration style guide — visual language, colour usage, and application rules. Use when commissioning or standardising illustration. For icons, use icon-system (design-systems).
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5
owl-listenerinterview-script
Write a structured interview guide — warm-up, core exploration, and wrap-up. Use before running interviews. For analysing what comes back, use summarize-interview.
- 1h installs
- 1
- GitHub stars
- 2.9K
- Updated
- Sep 5