stakeholder-communication

stakeholder-communication is a skill for Claude Code from Owl-Listener/inclusive-design-skills. It costs 80 tokens per session (1,013 once invoked), scanned A, original, MIT.

Guidance for explaining accessibility requirements and decisions to people who are not accessibility specialists. Accessibility means making products usable by people with disabilities.

In plain words
What is it for?
Use it when presenting accessibility work to leaders, product managers, engineers, or other stakeholders. It helps frame the same decision for different audiences.
Why use it?
It helps teams understand why accessibility work matters in terms relevant to their responsibilities, such as user experience, delivery plans, risk, or compliance.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the accessibility-decisions plugin — 9 skills shipped together

Good fit Use it when presenting accessibility work to leaders, product managers, engineers, or other stakeholders. It helps frame the same decision for different audiences.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/owl-listener/inclusive-design-skills/stakeholder-communication
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 Owl-Listener/inclusive-design-skills --skill stakeholder-communication
Clone the repo
git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills

Made for: Claude Code.

Or install accessibility-decisions, the plugin that ships this one along with the rest of its 9 skills.

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 stakeholder-communication

README.md
[![agentmods](https://agentmods.dev/badge/skills/owl-listener/inclusive-design-skills/stakeholder-communication/github.svg)](https://agentmods.dev/skills/owl-listener/inclusive-design-skills/stakeholder-communication)
Your own site
<a href="https://agentmods.dev/skills/owl-listener/inclusive-design-skills/stakeholder-communication"><img src="https://agentmods.dev/badge/skills/owl-listener/inclusive-design-skills/stakeholder-communication/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 stakeholder-communication

Your own site · 80×15
<a href="https://agentmods.dev/skills/owl-listener/inclusive-design-skills/stakeholder-communication"><img src="https://agentmods.dev/badge/skills/owl-listener/inclusive-design-skills/stakeholder-communication.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,013 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 original No closer match found 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.00080 $0.01013
Opus 5 $0.00040 $0.00507
Sonnet 5 $0.00016 $0.00203
Haiku 4.5 $0.00008 $0.00101

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

Security

Grade A, and why

stakeholder-communication 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.

accessibility-decisions/skills/stakeholder-communication/SKILL.md · 118 lines

How it starts

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

Stakeholder Communication

Communicate accessibility decisions in language that resonates with the person you're talking to — because the right argument depends on who's listening.

Core Principle

Different stakeholders care about different things. The accessibility argument that moves a CFO is not the one that moves an engineer. Match your framing to their priorities.

Stakeholder Frames

For Executives and Leadership

They care about: risk, revenue, reputation, legal exposure.

Frame accessibility as:

  • Risk reduction: "Non-compliance exposes us to legal action. ADA lawsuits increased every year for the past decade. The European Accessibility Act is now in effect."
  • Market size: "15% of the global population has a disability. That's over 1 billion potential users we're currently excluding."
  • Brand reputation: "Accessibility failures become public quickly. Accessibility leadership becomes a differentiator."
  • Cost avoidance: "Fixing accessibility at the design stage costs 10x less than fixing it after launch and 100x less than fixing it after a lawsuit."

For Product Managers

They care about: user satisfaction, completion rates, scope, timeline.

Frame accessibility as:

  • Conversion improvement: "Users who can't complete the flow don't convert. Every accessibility barrier is a drop-off point."
  • User satisfaction: "Accessibility improvements consistently improve satisfaction scores for ALL users, not just those with disabilities."
  • Scope clarity: "Here are the specific acceptance criteria. They're not extra work — they're the definition of done."
  • Competitive advantage: "Our competitors don't do this well. Accessibility is a real differentiator in procurement decisions."

For Engineers

They care about: clarity, specificity, standards, implementation cost.

Frame accessibility as:

  • Clear specifications: "Here's exactly what needs to happen: specific WCAG criteria, specific attributes, specific behaviour."
  • Code quality signal: "Accessible code is well-structured code. Semantic HTML, logical DOM order, and proper state management are engineering best practices regardless of accessibility."
  • Testing criteria: "Here's how to test it: these keyboard sequences, these screen reader announcements, these contrast ratios."
  • Prevention over remediation: "Building it right now is faster than fixing it after QA finds it."

Read the full file on GitHub · 118 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. 12d ago First seen · 118 lines · 80 tokens per session scan A 6f1ba6498458

Subscribe to this mod's changes

stakeholder-communication is a skill published in the GitHub repository Owl-Listener/inclusive-design-skills (98 stars, last pushed 3mo ago), licensed MIT. It adds 80 tokens to every session and 1,013 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.

Related

Other skills, from other repositories

webgl-holographic-foil

A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.

nexu-io/open-design · 41 tokens

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).

nexu-io/open-design · 78 tokens

visual-ralph

Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ultragoal with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.

Yeachan-Heo/oh-my-codex · 52 tokens

accessibility

Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.

microsoft/hve-core · 47 tokens

make-resume

A Chinese-language tool for creating editable HTML resumes that can be changed in a browser and printed to PDF. It uses available resume templates when they are installed and otherwise provides a simpler fallback.

Hisn00w/ASu-skills · 86 tokens