design-impact-reporting
Catalogue stub — full skill: Owl-Listener/designer-skills
Decision tree
-
Is the full skill already installed?
- Global:
f=~/.agents/skills/design-impact-reporting/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer" - Project:
f=.agents/skills/design-impact-reporting/SKILL.md; [ -f "$f" ] && ! grep -q "^das:" "$f" && echo "installed" || echo "pointer" installed→ the skill is installed asdesign-impact-reporting, invoke it and proceedpointer→ go to step 2
- Global:
-
Detect scope, then install:
bash[ -e ~/.agents/skills/design-impact-reporting ] && echo "global" || echo "project"Global:
bashnpx skills add Owl-Listener/designer-skills --skill design-impact-reporting -g -yProject:
bashnpx skills add Owl-Listener/designer-skills --skill design-impact-reporting -yClaude Code: send a command as a chat message starting with
!to run it without leaving the conversation.
Heads-up
- License: MIT
Invoke after install
- Skill name:
design-impact-reporting - Trigger phrases: "design impact reporting", "design ROI", "design scorecard"
What it does
Owl-Listener's design-impact skill: connect design work to user metrics → product metrics → business metrics, with honest attribution of shared outcomes. Provides concrete report structures (design scorecard, before/after case, A/B summary, annual portfolio) plus narrative structure and qualitative-evidence pairing. It is aimed at reporting results upward; for choosing the metrics in the first place, upstream points to its metrics-definition skill (ux-strategy), which is part of the same Owl-Listener/designer-skills repo (see the designer-skills stub).
When NOT to use
- Portfolio case-study storytelling → use a case-study/portfolio skill
- PM-level product metrics only → use
pm-skillsordeanpeters-pm-skills - Picking which design metrics to track → use
metrics-definitionfromdesigner-skills


