Swarma
glitch-rabin/swarma
Agent teams that run growth experiments and build their own playbook.
Communicate design's contribution to business and user outcomes in stakeholder language.
Install Design Impact Reporting
$ npx skills add Owl-Listener/designer-skills --skill design-impact-reporting -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/designer-skills design-impact-reporting --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/design-ops/skills/design-impact-reporting .claude/skills/design-impact-reporting && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "design-impact-reporting" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/design-impact-reporting into .claude/skills/design-impact-reporting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-impact-reporting", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/design-impact-reportingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/designer-skills --skill design-impact-reporting -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/designer-skills design-impact-reporting --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/design-ops/skills/design-impact-reporting .agents/skills/design-impact-reporting && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "design-impact-reporting" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/design-impact-reporting into .agents/skills/design-impact-reporting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-impact-reporting", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill design-impact-reporting -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/designer-skills design-impact-reporting --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/design-ops/skills/design-impact-reporting .cursor/skills/design-impact-reporting && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "design-impact-reporting" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/design-impact-reporting into .cursor/skills/design-impact-reporting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-impact-reporting", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/designer-skills.git --path design-ops/skills/design-impact-reporting--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/designer-skills --skill design-impact-reporting -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/designer-skills design-impact-reporting --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/design-ops/skills/design-impact-reporting .gemini/skills/design-impact-reporting && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "design-impact-reporting" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/design-impact-reporting into .gemini/skills/design-impact-reporting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-impact-reporting", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/designer-skills design-impact-reportingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/designer-skills --skill design-impact-reporting -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/design-ops/skills/design-impact-reporting .github/skills/design-impact-reporting && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "design-impact-reporting" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/design-impact-reporting into .github/skills/design-impact-reporting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-impact-reporting", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/designer-skills --skill design-impact-reporting -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/designer-skills design-impact-reporting --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/design-ops/skills/design-impact-reporting .opencode/skills/design-impact-reporting && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "design-impact-reporting" agent skill from https://github.com/Owl-Listener/designer-skills/tree/main/design-ops/skills/design-impact-reporting into .opencode/skills/design-impact-reporting/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "design-impact-reporting", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
design-impact-reporting- GitHub stars
- 2.9k
- Used in
- 1 other repo
- Token cost
- ~1.2k tokens
- SKILL.md length
- 616 words
- Files
- 1
- Skills in repo
- 107
- Repo updated
- First seen
- Licence
- MIT
At a glance
Communicate design's contribution to business and user outcomes in stakeholder language.
- Works in 5 steps: Context: what was the problem, and why… → Intervention: what did design do? → Evidence: what changed in user behavior… → …
- Reporting results upward
- SKILL.md covers What You Do, Why This Is Hard, Metrics Framework and Reporting Structures, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Design Impact Reporting is an agent skill from Owl-Listener/designer-skills. Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use metrics-definition (ux-strategy).
Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering Product metrics. The repository describes itself as: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery. The licence is MIT.
When your agent uses it
- Reporting results upward
- Tasks that involve Product metrics
Example prompts
- “/design-impact-reporting”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Context: what was the problem, and why did it matter?
- Intervention: what did design do?
- Evidence: what changed in user behavior or product metrics?
- Business value: what does that change mean in revenue, cost, or risk terms?
- What's next: what are we working on now, and what do we expect it to achieve?
What it can do on your machine
Read from SKILL.md and the folder at commit 9a6930c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Design Impact Reporting loads about 1.2k tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 616 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Owl-Listener/designer-skills at commit 9a6930c, republished under its MIT licence (© Owl-Listener). 616 words, ~1,197 tokens.
Download SKILL.mdSave it as
.claude/skills/design-impact-reporting/SKILL.md (or your agent's skills folder).- name
- design-impact-reporting
- description
- Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use `metrics-definition` (ux-strategy).
Design Impact Reporting
You are an expert in measuring and communicating the value of design work to leadership, cross-functional partners, and the broader organization.
What You Do
You build the evidence and narrative that connects design decisions to measurable outcomes — so design is treated as a strategic investment, not a cost center or aesthetic layer.
Why This Is Hard
Design impact is often diffuse, lagged, and shared with other functions. A better onboarding flow increases conversion — but so does a marketing campaign and a pricing change that launched the same quarter. Design impact reporting requires:
- Isolating design's contribution where possible
- Acknowledging shared outcomes honestly where isolation isn't possible
- Building a portfolio of evidence over time, not just one-off wins
Metrics Framework
Connect design work to three levels:
User Metrics (leading indicators)
What users do as a result of the design:
- Task completion rate and time-on-task
- Error rate and recovery rate
- System Usability Scale (SUS) or similar satisfaction scores
- Net Promoter Score, CSAT, or in-product feedback
- Activation rate (first meaningful action after sign-up)
- Feature adoption and retention
Product Metrics (mid-level)
What the product achieves:
- Conversion rate (sign-up, trial-to-paid, checkout)
- Onboarding completion rate
- Support ticket volume for designed flows (reduction = design improvement)
- Accessibility compliance score
- Time spent in key flows
Business Metrics (lagging, shared)
What the business achieves:
- Revenue attributed to redesigned flows (use A/B test data where available)
- Churn reduction in redesigned areas
- Cost savings (reduced support, engineering rework avoided)
- Time-to-market for design-system-enabled features
Reporting Structures
The Design Scorecard
A recurring (quarterly) snapshot of key metrics across active design work:
- 3–5 metrics per major initiative
- Baseline vs current vs target
- Status: on track / at risk / achieved
- Brief narrative on what drove change
Before/After Case
For significant shipped work:
- Metric before (baseline, with date)
- Design change described in one sentence
- Metric after (with date and sample size)
- Caveat if other factors were in play
- Business value: revenue, cost, time
A/B Test Summary
When controlled experiments are available:
- Hypothesis
- Variants and sample sizes
- Primary metric result (with statistical significance)
- Secondary metric results
- Decision and rationale
Portfolio Summary (annual)
For leadership and headcount conversations:
- Projects shipped with their impact metrics
- Cumulative impact across the year
- Investment: design team time, tooling cost
- ROI framing: "Design team investment returned X in conversion improvement"
Show full SKILL.md (239 more words)Show less
Qualitative Evidence
Quantitative metrics alone are incomplete. Pair them with:
- User quotes from research that predicted the outcome
- Usability test clips showing the problem and the improvement
- Design debt that was resolved (showing risk reduction)
- Accessibility improvements (compliance + expanded user reach)
Common Mistakes
- Reporting outputs (screens designed, components shipped) instead of outcomes
- Attributing metric improvements to design without acknowledging co-factors
- Only reporting wins — teams that report failures build more credibility over time
- Reporting with a one-month lag — tie reporting cadence to business review cycles
- Using design jargon ("improved hierarchy", "cleaner layout") without connecting to user behavior
Structuring the Narrative
Every impact report needs:
- Context: what was the problem, and why did it matter?
- Intervention: what did design do?
- Evidence: what changed in user behavior or product metrics?
- Business value: what does that change mean in revenue, cost, or risk terms?
- What's next: what are we working on now, and what do we expect it to achieve?
Best Practices
- Define success metrics before shipping, not after — retrospective metric-picking is unconvincing
- Partner with data/analytics to get access to the metrics that matter, not just the ones design can self-report
- Build relationships with finance and product to understand how they measure value — translate into their language
- Publish a simple, consistent format; stakeholders who see the same structure quarterly start to anticipate it
- Use impact reporting as a team ritual — it builds the team's evidence-gathering habits over time
© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in design-ops/skills/design-impact-reporting of Owl-Listener/designer-skills.
Open the folder on GitHubat commit 9a6930c
Used in 1 other repository
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Owl-Listener/designer-skills, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Design Impact Reporting next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Design Impact Reporting this skillOwl-Listener/designer-skills | 2.9k | 1 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Swarmaglitch-rabin/swarma | 173 | — | ~4.4k | Automated safety check: Notes | MIT | |
| Prdjuanandresgs/claude-ctrl | 193 | — | ~2.9k | Automated safety check: Pass | None | |
| AI Product Strategy InterviewerPrepLabsAI/InterviewMentor | 112 | — | ~4.5k | Automated safety check: Pass | MIT | |
| Investigate MetricPostHog/posthog | 40k | — | ~1.9k | Automated safety check: Pass | Custom licence | |
| Weekly Creative Reportreal-simple-labs/parker-brain | 102 | — | ~4.7k | Automated safety check: Pass | Custom licence |
Similar skills
Prd
juanandresgs/claude-ctrl
Write structured feature specifications with problem statements, user journeys, use cases, functional requirements, and success metrics.
AI Product Strategy Interviewer
PrepLabsAI/InterviewMentor
A VP of Product interviewer that simulates a product strategy interview focused on AI-native products.
- Official
Investigate Metric
PostHog/posthog
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Weekly Creative Report
real-simple-labs/parker-brain
Build the brand's weekly creative report, a polished, shareable page an agency can send straight to the brand's CMO and team.
North Star
andreaskelm/pm-brain
Define, sharpen, or audit a North Star metric and its input metrics tree, and decide which product metrics actually matter (leading vs.
More from Owl-Listener/designer-skills
All 107 skills in this repoA B Test Design
Owl-Listener/designer-skills
Design an A/B experiment — hypothesis, variants, primary metric, and sample size.
Accessibility Test Plan
Owl-Listener/designer-skills
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.
Aesthetic Usability
Owl-Listener/designer-skills
Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.
Affinity Diagram
Owl-Listener/designer-skills
Cluster many qualitative data points into themes and insight statements.
Animation Principles
Owl-Listener/designer-skills
Apply animation principles — easing, staging, follow-through — to one specific UI motion.
Business Design
Owl-Listener/designer-skills
Read financials, map competitive landscapes, and argue design decisions in the language of value.
Related
Questions about Design Impact Reporting
What does Design Impact Reporting do?
Communicate design's contribution to business and user outcomes in stakeholder language. Design Impact Reporting is an agent skill from Owl-Listener/designer-skills. Communicate design's contribution to business and user outcomes in stakeholder language.
When should I use Design Impact Reporting?
Design Impact Reporting fits situations like: reporting results upward; tasks that involve Product metrics.
How do I install Design Impact Reporting in Claude Code?
Run `npx skills add Owl-Listener/designer-skills --skill design-impact-reporting -a claude-code`. Or copy the skill folder (design-ops/skills/design-impact-reporting in Owl-Listener/designer-skills) into .claude/skills/design-impact-reporting in your project. Claude Code loads it when a task matches its description.
How do I install Design Impact Reporting in Codex?
Run `npx skills add Owl-Listener/designer-skills --skill design-impact-reporting -a codex`. Or copy the skill folder (design-ops/skills/design-impact-reporting in Owl-Listener/designer-skills) into .agents/skills/design-impact-reporting in your project. Codex loads it when a task matches its description.
Can I use Design Impact Reporting in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designer-skills --skill design-impact-reporting -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/design-impact-reporting, .gemini/skills/design-impact-reporting, .github/skills/design-impact-reporting and .opencode/skills/design-impact-reporting in your project.
What does Design Impact Reporting need to run?
SKILL.md names no scripts, command-line tools or credentials: Design Impact Reporting is instructions for the agent only.
Does Design Impact Reporting access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Design Impact Reporting safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Design Impact Reporting use?
Design Impact Reporting is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Design Impact Reporting use?
About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Design Impact Reporting?
Skills that share tags, products or a category with Design Impact Reporting: Swarma (glitch-rabin/swarma, 173 stars), Prd (juanandresgs/claude-ctrl, 193 stars), AI Product Strategy Interviewer (PrepLabsAI/InterviewMentor, 112 stars) and Investigate Metric (PostHog/posthog, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Design Impact Reporting?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,871 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on September 5, 2026.
Source: Owl-Listener/designer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.