agentsclimarketplace
Sign in

Cognitive ux health

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

Design and audit health-information, patient-portal, appointment, refill, and care-communication websites using evidence-informed UX. Use when people need to understand care information or manage care; return health-literacy structure, uncertainty/provenance rules, task flows, privacy and escalation design, accessible support, and representative patient/caregiver validation.From its SKILL.md

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

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.7 KB, 459 tokens by cl100k_base, as published. Nobody here has run it

Cognitive UX: Health & Patient

Scope

Use for patient-facing health experiences. It does not create clinical guidance or establish medical, privacy, or legal compliance.

Intake

  • Identify patient/caregiver tasks, health literacy, language, disability, emotional context, and urgency.
  • Identify clinical owner, source/review date, uncertainty, emergency/escalation policy, and privacy constraints.
  • Identify appointment, refill, results, messaging, sharing, proxy access, and support limitations.

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. Start with a plain-language summary; separate factual information, uncertainty, next steps, and emergency/escalation guidance.
  2. Make authorship, clinical review, source, date, and update status visible for consequential health content.
  3. Design results, messages, appointments, refills, and proxy access with clear status and support paths; do not imply a message is monitored in an emergency.
  4. Use accessible language, captions/transcripts, keyboard operation, and alternatives for high cognitive or sensory load.
  5. Require clinical, privacy, legal, and representative patient/caregiver review before release.

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

Required outputs

  • health-literacy and content-provenance model
  • patient task/status/escalation flow
  • privacy/proxy/accessibility checklist
  • clinical-review and uncertainty disclosure plan
  • patient/caregiver comprehension and task study
  • Evidence-to-decision table: decision → mechanism → source → label → limitation → test metric.
  • Accessibility, ethics, and recovery-path checklist.

Guardrails

Do not diagnose, overstate certainty, hide emergency limitations, expose health data unnecessarily, or call UX testing a substitute for clinical validation.

Related skills

Use cognitive-ux-portal, cognitive-ux-booking, and cognitive-ux-forms. 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 326,569. 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.