design-impact-reporting

design-impact-reporting is a skill for Claude Code from Infrasity-Labs/dev-gtm-claude-skills. It costs 22 tokens per session (952 once invoked), scanned A, a copy of design-impact-reporting, MIT.

A way to measure and explain how design work affects user behavior and business results. It connects design decisions with metrics such as task completion, errors, activation, satisfaction, and revenue while acknowledging other causes.

In plain words
What is it for?
It helps define relevant metrics, gather evidence, assess design changes, and report results to leadership and other teams.
Why use it?
It helps design teams show the value of their work with evidence instead of relying on subjective opinions or claiming credit for every outcome.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Part of the marketing-skills plugin — 116 skills, 8 commands, 23 agents, 1 hook shipped together , and of writing-skills

Good fit It helps define relevant metrics, gather evidence, assess design changes, and report results to leadership and other teams.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/infrasity-labs/dev-gtm-claude-skills/design-impact-reporting
Install

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.

Any agent
npx skills add Infrasity-Labs/dev-gtm-claude-skills --skill design-impact-reporting
Clone the repo
git clone --depth 1 https://github.com/Infrasity-Labs/dev-gtm-claude-skills

Made for: Claude Code.

Or install marketing-skills, the plugin that ships this one along with the rest of its 116 skills, 8 commands, 23 agents, 1 hook.

Wrote 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.

agentmods badge for design-impact-reporting

README.md
[![agentmods](https://agentmods.dev/badge/skills/infrasity-labs/dev-gtm-claude-skills/design-impact-reporting/github.svg)](https://agentmods.dev/skills/infrasity-labs/dev-gtm-claude-skills/design-impact-reporting)
Your own site
<a href="https://agentmods.dev/skills/infrasity-labs/dev-gtm-claude-skills/design-impact-reporting"><img src="https://agentmods.dev/badge/skills/infrasity-labs/dev-gtm-claude-skills/design-impact-reporting/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.

agentmods 80×15 button for design-impact-reporting

Your own site · 80×15
<a href="https://agentmods.dev/skills/infrasity-labs/dev-gtm-claude-skills/design-impact-reporting"><img src="https://agentmods.dev/badge/skills/infrasity-labs/dev-gtm-claude-skills/design-impact-reporting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 952 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 95% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00022 $0.00952
Opus 5 $0.00011 $0.00476
Sonnet 5 $0.00004 $0.00190
Haiku 4.5 $0.00002 $0.00095

Measured 9d ago against content hash 32fa9e361b6e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

design-impact-reporting 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 9d 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.

Origin

This is a copy

95% identical to design-impact-reporting — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/design-impact-reporting/SKILL.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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

Read the full file on GitHub · 89 lines

Changes

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.

  1. 9d ago First seen · 89 lines · 22 tokens per session scan A 32fa9e361b6e

Subscribe to this mod's changes

design-impact-reporting is a skill published in the GitHub repository Infrasity-Labs/dev-gtm-claude-skills (124 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 952 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to design-impact-reporting, differing in 2 lines, and is treated as a copy.

Related

Other skills, from other repositories

sxo

Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…

nowork-studio/notfair-plugin · 235 tokens

geo-audit

Full website GEO+SEO audit with parallel subagent delegation. Orchestrates a comprehensive Generative Engine Optimization audit across AI citability, platform analysis, technical infrastructure, content quality, and schema markup. Produces a composite GEO Score (0-100) with prioritized action plan.

techhorizonlabs/thl-open · 60 tokens

geo

GEO-first SEO analysis tool. Optimizes websites for AI-powered search engines (ChatGPT, Claude, Perplexity, Gemini, Google AI Overviews) while maintaining traditional SEO foundations. Performs full GEO audits, citability scoring, AI crawler analysis, llms.txt generation, brand mention scanning, platform-specific…

techhorizonlabs/thl-open · 139 tokens

geo-brand-mentions

Brand mention and authority scanner for AI visibility. Analyzes brand presence across platforms that AI models rely on for entity recognition and citation decisions. Produces a Brand Authority Score (0-100) with platform-specific recommendations.

techhorizonlabs/thl-open · 49 tokens

geo-llmstxt

Analyzes and generates llms.txt files -- the emerging standard for helping AI systems understand website structure and content. Can validate existing llms.txt files or generate new ones from scratch by crawling the site.

techhorizonlabs/thl-open · 46 tokens

agent-readiness-scan

Use when a client audit, GEO/AI-visibility snapshot, or remediation re-scan needs the Cloudflare agent-readiness score from isitagentready.com — e.g. Theo client audits, "is the site agent-ready", markdown negotiation / MCP / llms.txt / Content-Signal checks, or tracking score deltas after Tier 0/1 fixes.

techhorizonlabs/thl-open · 79 tokens