Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add human-avatar/skills-for-humanity --skill s4h-design-user-needsgit clone --depth 1 https://github.com/human-avatar/skills-for-humanityWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/human-avatar/skills-for-humanity/s4h-design-user-needs)<a href="https://agentmods.dev/skills/human-avatar/skills-for-humanity/s4h-design-user-needs"><img src="https://agentmods.dev/badge/skills/human-avatar/skills-for-humanity/s4h-design-user-needs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/human-avatar/skills-for-humanity/s4h-design-user-needs"><img src="https://agentmods.dev/badge/skills/human-avatar/skills-for-humanity/s4h-design-user-needs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00080 | $0.01527 |
| Opus 5 | $0.00040 | $0.00763 |
| Sonnet 5 | $0.00016 | $0.00305 |
| Haiku 4.5 | $0.00008 | $0.00153 |
Grade A, and why
s4h-design-user-needs scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design: User Needs
The most common design failure is building the wrong thing well. People don't articulate needs — they articulate solutions. "I want a faster horse," "I need a bigger inbox," "give me more options." These are requests framed as solutions to problems the user hasn't quite stated. A designer who takes them at face value will build a faster horse, a bigger inbox, more options — and miss the underlying need entirely.
Clayton Christensen's jobs-to-be-done framework makes the shift explicit: people don't buy products, they hire them to do a job. Understanding the job — not the product request — is the designer's actual brief. Don Norman extended this with the distinction between stated needs (what people say), observed needs (what people do), and latent needs (what people don't yet know they need but would recognise immediately if you showed them). All three matter. Only one of them is given to you directly.
This skill works through all three levels, using structured inquiry to separate the real need from the stated proxy and surface the design target that actually matters.
Your Process
Step 1: State the Request Write down exactly what was asked for, in the words it was stated. Preserve the phrasing — the precise language reveals how the person is framing the problem.
Framing check: Confirm the request and the context in which it arose before continuing. State what you've identified — the stated request and the situation it comes from — in one sentence, then use AskUserQuestion:
- Question: "I'm reading this as: [your one-sentence framing of the request and its context]. Is that right?"
- Header: "Framing"
- Options:
- Yes — proceed — framing is correct
- Adjust — one element is off; user will correct it before you continue
- Reframe — different situation than read; incorporate the correction before proceeding
Step 2: Decompose the Job Apply jobs-to-be-done decomposition. For the stated request, identify:
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 120 lines · 80 tokens per session scan A f84b32b25a4c
s4h-design-user-needs is a skill published in the GitHub repository human-avatar/skills-for-humanity (223 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session and 1,527 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
customer-journey-map
Visualize every touchpoint a customer has with a product or service — stages, actions, emotions, pain points, opportunities.
double-diamond
Design problems with two diamond phases: Discover/Define (right problem), Develop/Deliver (right solution).
token-audit
Audit a design system's token definitions for naming violations, missing semantic tiers, and structural debt. This audits how tokens are defined and organised, NOT how they are consumed in code. Trigger when someone says: audit my tokens, token naming review, are my tokens consistent, token health check, review my…
codebase-index
Generate a pre-computed component index from a design system codebase — YAML infrastructure files containing a component inventory, relationship graph, and summary statistics that AI agents and MCP servers consume. This produces machine-readable index files in .ai/index/, NOT a health report or quality assessment.…
prototype
Use when asked to prototype one design question through a cheap logic or UI experiment, including button-driven state-model checks. Not for polished artifacts: use polished-web-prototype.
review-design
Review digital artifacts against the user’s task, creative direction, functional and accessibility requirements, and actual delivery medium. Inspect renders, native files, playback or interaction as appropriate; exercise relevant failure and recovery paths and report evidence-backed findings. Use for design review or…