agentleFS
Sign inStart free
podopodo/design-agent-skills/skills/design-impact-reporting/SKILL.md

design-impact-reporting

Skill32 starsChanged 6 months agoMITView on GitHub

Communicate design’s contribution to user and business outcomes in stakeholder terms. Metrics framework, scorecard / before-after / A-B / portfolio report formats.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Create a free account to mount
Files
SKILL.md

design-impact-reporting

Catalogue stub — full skill: Owl-Listener/designer-skills

<!-- das:install:start — generated from stub.yaml by `npm run generate`; edit stub.yaml, not this block -->

Decision tree

  1. 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 as design-impact-reporting, invoke it and proceed
    • pointer → go to step 2

  2. Detect scope, then install:

    [ -e ~/.agents/skills/design-impact-reporting ] && echo "global" || echo "project"

    Global:

    npx skills add Owl-Listener/designer-skills --skill design-impact-reporting -g -y

    Project:

    npx skills add Owl-Listener/designer-skills --skill design-impact-reporting -y

    Claude Code: send a command as a chat message starting with ! to run it without leaving the conversation.

Heads-up

  • License: MIT
<!-- das:install:end -->

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-skills or deanpeters-pm-skills
  • Picking which design metrics to track → use metrics-definition from designer-skills

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free