agentsclimarketplace
Sign in

Cognitive ux dashboard

Skill kfeng209-oss/cognitive-ux/skills/cognitive-ux-dashboard

Design and audit analytics dashboards, monitoring surfaces, and decision-support websites using evidence-informed UX. Use when people must monitor a situation, interpret data, investigate exceptions, and act; return a decision inventory, KPI/provenance model, progressive drill-down, accessible data alternatives, alert rules, and accuracy-based validation.From its SKILL.md

Install
npx -y skills add kfeng209-oss/cognitive-ux --skill cognitive-ux-dashboard

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.5 KB, 442 tokens by cl100k_base, as published. Nobody here has run it

Cognitive UX: Analytics & Dashboard

Scope

Use for analytical decision support. Use cognitive-ux-workflow when the main job is completing a multi-step task rather than interpreting data.

Intake

  • Identify the decisions users must make, their frequency, urgency, and consequence.
  • Identify metrics, units, timeframes, freshness, uncertainty, thresholds, and data permissions.
  • Identify role-specific actions, operational context, empty/error/stale states, and accessible alternatives.

State assumptions that could change the design. Define the primary task, its consequence of failure, and a measurable user outcome before proposing a layout.

Design procedure

  1. Begin with the decision, change, exception, and next action—not an inventory of charts.
  2. Show definition, timeframe, unit, freshness, uncertainty, and source/provenance for every decision-relevant metric.
  3. Use summary → comparison → detail drill-down while preserving filters, focus, and the question being investigated.
  4. Design alerts with a clear condition, severity, owner, action, acknowledgment, and recovery; avoid continuous alarm styling.
  5. Provide a usable data-table or text alternative for charts, and do not encode meaning with color alone.

Read archetype evidence. Label each non-obvious recommendation Standard / requirement, Evidence-informed default, or Hypothesis to test.

Required outputs

  • decision and KPI inventory
  • dashboard hierarchy and drill-down map
  • alert/action and data-state specification
  • visualization plus accessible data-alternative checklist
  • decision accuracy/time test plan
  • Evidence-to-decision table: decision → mechanism → source → label → limitation → test metric.
  • Accessibility, ethics, and recovery-path checklist.

Guardrails

Do not use decorative charts, false precision, unlabeled timeframes, color-only severity, or a metric that lacks a defined decision purpose.

Related skills

Use cognitive-ux-workflow, cognitive-ux-admin, and cognitive-ux-finance. Select the primary task before combining skills; add a secondary skill only when it changes the user outcome or risk.

What ships with it: 2 files

1.6 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.