New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Stakeholder Communication

by Owl-Listener in Owl-Listener/inclusive-design-skills

Communicate accessibility decisions, requirements, and value to stakeholders who aren't accessibility specialists.

MITAuto-check passedFrontend & Design

Install Stakeholder Communication

skills CLI
$ npx skills add Owl-Listener/inclusive-design-skills --skill stakeholder-communication -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Owl-Listener/inclusive-design-skills stakeholder-communication --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/accessibility-decisions/skills/stakeholder-communication .claude/skills/stakeholder-communication && rm -rf skills-src

Use ~/.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/

Facts

Skill name
stakeholder-communication
GitHub stars
105
Token cost
~1.3k tokens
SKILL.md length
609 words
Files
1
Skills in repo
55
Repo updated
First seen
Licence
MIT

At a glance

Communicate accessibility decisions, requirements, and value to stakeholders who aren't accessibility specialists.

  • Works in 4 steps: State the specific user problem (not the… → Quantify who's affected (numbers, not… → Show the fix and its scope (specific,… → …
  • Presenting accessibility work to leadership
  • SKILL.md covers Core Principle, Stakeholder Frames, Structuring the Conversation and Anti-Patterns, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Stakeholder Communication is an agent skill from Owl-Listener/inclusive-design-skills. Communicate accessibility decisions, requirements, and value to stakeholders who aren't accessibility specialists. Use when presenting accessibility work to leadership, product managers, engineers, or anyone who needs to understand why accessibility decisions matter. Triggers on: stakeholder, business case, justify accessibility, explain accessibility, leadership, executive, ROI, why accessibility, cost of accessibility, persuade, convince, accessibility presentation.

Its SKILL.md is about 1.3k 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 Frontend & Design, covering Internal communications and Accessibility. The repository describes itself as: Inclusive design skills for AI coding agents — from cognitive accessibility to adaptive interfaces, inclusive research, and accessibility decision-making. The licence is MIT.

When your agent uses it

  • Presenting accessibility work to leadership
  • Product managers
  • Anyone who needs to understand why accessibility decisions matter
  • Justify accessibility

Example prompts

  • “/stakeholder-communication”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. State the specific user problem (not the technical requirement)
  2. Quantify who's affected (numbers, not percentages alone)
  3. Show the fix and its scope (specific, bounded, achievable)
  4. Connect to something they already care about (legal, revenue, brand)

What it can do on your machine

Read from SKILL.md and the folder at commit 6e0740f. 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

Stakeholder Communication loads about 1.3k tokens when it runs. Until then it costs about 125 tokens; SKILL.md has 609 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~125
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

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/inclusive-design-skills at commit 6e0740f, republished under its MIT licence (© Owl-Listener). 609 words, ~1,293 tokens.

Download SKILL.mdSave it as .claude/skills/stakeholder-communication/SKILL.md (or your agent's skills folder).
name
stakeholder-communication
description
Communicate accessibility decisions, requirements, and value to stakeholders who aren't accessibility specialists. Use when presenting accessibility work to leadership, product managers, engineers, or anyone who needs to understand why accessibility decisions matter. Triggers on: stakeholder, business case, justify accessibility, explain accessibility, leadership, executive, ROI, why accessibility, cost of accessibility, persuade, convince, accessibility presentation.

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."
For Designers

They care about: user experience, craft, professional standards.

Frame accessibility as:

  • Design quality: "Accessible design is better design. Clear hierarchy, consistent patterns, plain language, and forgiving interactions improve the experience for everyone."
  • Professional standard: "Accessibility is not a constraint on creativity. It's a design requirement, like responsive design or performance."
  • User empathy: "We design for real people in real contexts. Disability is part of that reality."
Show full SKILL.md (225 more words)Show less

Structuring the Conversation

When Asking for Resources
  1. State the specific user problem (not the technical requirement)
  2. Quantify who's affected (numbers, not percentages alone)
  3. Show the fix and its scope (specific, bounded, achievable)
  4. Connect to something they already care about (legal, revenue, brand)
When Pushing Back on Cuts
  1. Name exactly who gets excluded by the cut
  2. State the severity (blocked vs friction)
  3. Offer an alternative scope reduction that doesn't sacrifice accessibility
  4. Document the decision if overruled (this protects everyone)
When Reporting Progress
  • Lead with outcomes: "3 more user groups can now complete checkout"
  • Show before/after: concrete improvements, not abstract compliance
  • Connect to metrics they track: completion rate, support tickets, satisfaction scores
  • Avoid jargon: "users who can't see the screen" not "JAWS users encountering ARIA violations"

Anti-Patterns

  • Leading with compliance alone (feels like box-ticking, not value)
  • Using guilt ("disabled people can't use our product")
  • Being vague ("we need to improve accessibility")
  • Framing as optional ("it would be nice to...")
  • Treating accessibility as a separate project rather than part of quality

Assessment Questions

  1. Can you articulate the accessibility argument in terms each stakeholder cares about?
  2. Are accessibility requirements presented as specific acceptance criteria, not vague aspirations?
  3. Is progress reported in user outcomes, not technical compliance?
  4. When accessibility is deprioritised, is the decision and its impact documented?

© 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 accessibility-decisions/skills/stakeholder-communication of Owl-Listener/inclusive-design-skills.

Open the folder on GitHubat commit 6e0740f

Compare with similar skills

Stakeholder Communication 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.

Stakeholder Communication compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Stakeholder Communication this skillOwl-Listener/inclusive-design-skills105—~1.3kAutomated safety check: PassMIT
Web Interface Guidelines Reviewervercel-labs/openreview1.7k97 repos~308Automated safety check: PassNone
Accessibility Reviewmarkmead/hyperui12k1 repos~1.1kAutomated safety check: PassMIT
Web Animation DesignbaptisteArno/typebot.io11k2 repos~2.7kAutomated safety check: PassCustom licence
Accessibility Fixeribelick/ui-skills9.6k4 repos~1.2kAutomated safety check: PassMIT
Wcag Audit PatternsvmDeshpande/ai-agent-automation17811 repos~610Automated safety check: PassApache-2.0

Similar skills

  • Web Interface Guidelines Reviewer

    vercel-labs/openreview

    Official

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…

    1.7k GitHub starsUsed in 97 repos~308 tokens
    Frontend & DesignAuto-check passed

  • Accessibility Review

    markmead/hyperui

    Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.

    12k GitHub starsUsed in 1 repo~1.1k tokens
    Frontend & DesignAuto-check passed

  • Web Animation Design

    baptisteArno/typebot.io

    Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.

    11k GitHub starsUsed in 2 repos~2.7k tokens
    Frontend & DesignAuto-check passed

  • Accessibility Fixer

    ibelick/ui-skills

    Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.

    9.6k GitHub starsUsed in 4 repos~1.2k tokens
    Frontend & DesignAuto-check passed

  • Wcag Audit Patterns

    vmDeshpande/ai-agent-automation

    Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance.

    178 GitHub starsUsed in 11 repos~610 tokens
    Frontend & DesignAuto-check passed

  • Baseline UI

    ibelick/ui-skills

    Applies a fixed set of UI rules for stack, components, interaction, animation, typography and layout, or reviews a file against them with concrete fixes.

    9.6k GitHub starsUsed in 8 repos~855 tokens
    Frontend & DesignAuto-check passed

More from Owl-Listener/inclusive-design-skills

All 55 skills in this repo

  • Assistive Technology Scenarios

    Owl-Listener/inclusive-design-skills

    Writes usage scenarios, use cases and storyboards that show real people using screen readers, switches, voice control and other assistive technology to finish tasks.

    105 GitHub stars~1.1k tokensUpdated 4 mo ago
    Auto-check passed

  • Error Prevention and Recovery

    Owl-Listener/inclusive-design-skills

    Designs forgiving forms and flows: prevent input errors, write messages that say what happened and what to do, and add undo, confirmation and recovery paths.

    105 GitHub stars~739 tokensUpdated 4 mo ago
    Auto-check passed

  • Accessible Heading Structure

    Owl-Listener/inclusive-design-skills

    Designs heading hierarchies for screen reader navigation and cognitive accessibility on pages, articles, dashboards and forms.

    105 GitHub stars~763 tokensUpdated 4 mo ago
    Auto-check passed

  • Ability Spectrum Mapping

    Owl-Listener/inclusive-design-skills

    Maps a feature across a range of vision, hearing, motor and cognitive ability to find where the design starts to fail, and to explain accessibility scope to stakeholders.

    105 GitHub stars~917 tokensUpdated 4 mo ago
    Auto-check passed

  • Accessibility Debt Tracking

    Owl-Listener/inclusive-design-skills

    Track and manage accessibility debt — known accessibility issues that have been deferred.

    105 GitHub stars~869 tokensUpdated 4 mo ago
    Auto-check passed

  • Accessibility Testing Strategy

    Owl-Listener/inclusive-design-skills

    Plan what to test, how to test, and who should test for accessibility.

    105 GitHub stars~1k tokensUpdated 4 mo ago
    Auto-check passed

Categories

Questions about Stakeholder Communication

What does Stakeholder Communication do?

Communicate accessibility decisions, requirements, and value to stakeholders who aren't accessibility specialists. Stakeholder Communication is an agent skill from Owl-Listener/inclusive-design-skills. Communicate accessibility decisions, requirements, and value to stakeholders who aren't accessibility specialists.

When should I use Stakeholder Communication?

Stakeholder Communication fits situations like: presenting accessibility work to leadership; product managers; anyone who needs to understand why accessibility decisions matter; justify accessibility.

How do I install Stakeholder Communication in Claude Code?

Run `npx skills add Owl-Listener/inclusive-design-skills --skill stakeholder-communication -a claude-code`. Or copy the skill folder (accessibility-decisions/skills/stakeholder-communication in Owl-Listener/inclusive-design-skills) into .claude/skills/stakeholder-communication in your project. Claude Code loads it when a task matches its description.

How do I install Stakeholder Communication in Codex?

Run `npx skills add Owl-Listener/inclusive-design-skills --skill stakeholder-communication -a codex`. Or copy the skill folder (accessibility-decisions/skills/stakeholder-communication in Owl-Listener/inclusive-design-skills) into .agents/skills/stakeholder-communication in your project. Codex loads it when a task matches its description.

Can I use Stakeholder Communication 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/inclusive-design-skills --skill stakeholder-communication -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/stakeholder-communication, .gemini/skills/stakeholder-communication, .github/skills/stakeholder-communication and .opencode/skills/stakeholder-communication in your project.

What does Stakeholder Communication need to run?

SKILL.md names no scripts, command-line tools or credentials: Stakeholder Communication is instructions for the agent only.

Does Stakeholder Communication 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 Stakeholder Communication 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 Stakeholder Communication use?

Stakeholder Communication 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 Stakeholder Communication use?

About 1.3k tokens (SKILL.md is roughly 5.2k 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 Stakeholder Communication?

Skills that share tags, products or a category with Stakeholder Communication: Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars), Accessibility Review (markmead/hyperui, 12k stars), Web Animation Design (baptisteArno/typebot.io, 11k stars) and Accessibility Fixer (ibelick/ui-skills, 9.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Stakeholder Communication?

Owl-Listener (a GitHub user) maintains it in Owl-Listener/inclusive-design-skills, which has 105 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on June 9, 2026.

Source: Owl-Listener/inclusive-design-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.