stakeholder-communication

stakeholder-communication is a skill for Claude Code, Codex from uthumany/uthy-legacy-os. It costs 30 tokens per session (906 once invoked), scanned A, original, MIT.

A writing framework for status updates, executive briefs, and dashboards aimed at stakeholders such as leaders, partner teams, and customers.

In plain words
What is it for?
Use it to report project status, explain delays or blockers, present results to leadership, and communicate changes to teams or customers.
Why use it?
It helps communicate progress, risks, dependencies, and decisions in a format suited to each audience.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to report project status, explain delays or blockers, present results to leadership, and communicate changes to teams or customers.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/uthumany/uthy-legacy-os/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 uthumany/uthy-legacy-os --skill stakeholder-communication
Clone the repo
git clone --depth 1 https://github.com/uthumany/uthy-legacy-os

Made for: Claude Code, Codex.

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/uthumany/uthy-legacy-os/stakeholder-communication/github.svg)](https://agentmods.dev/skills/uthumany/uthy-legacy-os/stakeholder-communication)
Your own site
<a href="https://agentmods.dev/skills/uthumany/uthy-legacy-os/stakeholder-communication"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/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/uthumany/uthy-legacy-os/stakeholder-communication"><img src="https://agentmods.dev/badge/skills/uthumany/uthy-legacy-os/stakeholder-communication.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 906 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.00030 $0.00906
Opus 5.5 $0.00012 $0.00362
Sonnet 5.5 $0.00006 $0.00181
Haiku 4.5 $0.00003 $0.00091

Measured 2mo ago against content hash 7e07e057453d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

skills/shipping/stakeholder-communication/SKILL.md · 95 lines

How it starts

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

Stakeholder Communication

Overview

Great product work + poor communication = perceived failure. This skill helps you communicate with stakeholders — executives, cross-functional teams, and customers — in ways that build trust, manage expectations, and keep everyone aligned.

When to Use

  • Providing regular status updates on an initiative
  • Communicating a delay, blocker, or risk
  • Presenting results to leadership
  • Onboarding a new stakeholder to your project
  • Don't use for: day-to-day team standups (different audience, different format), marketing communications

Instructions

1. Know Your Audience

Stakeholder What They Care About Format
Executives Impact, risks, decisions needed 2-3 sentence summary + RAG status
Cross-functional teams Dependencies, timelines, action items Bullet list with owners
Customers What's changing, when, why Release notes, blog posts
Your team Progress, blockers, decisions Standup, Slack update

2. Use the RAG Status Framework

  • 🟢 Green: On track. No blockers. Expected to ship on time.
  • 🟡 Yellow: At risk. Blocker identified, plan to resolve exists, timeline may slip.
  • 🔴 Red: Off track. Needs escalation. Timeline WILL slip without intervention.

3. Write the Status Update

Executive summary (3 sentences max):

  1. What happened since last update
  2. Current status (RAG + why)
  3. What you need from them

Details (if needed):

  • Progress against goals (metrics if available)
  • Key decisions made
  • Risks and mitigations
  • Upcoming milestones

4. Communicate Bad News

When things go wrong:

  1. Be early — Bad news doesn't get better with age
  2. State the problem clearly — What happened, what's the impact
  3. Bring a plan — What we're doing about it, what we need
  4. Timeline — When will we know more / when will it be fixed
  5. Own it — Blame doesn't help. Solutions do.

Template for bad news:

"We're going to miss the [date] launch for [feature]. Here's why: [reason]. Impact: [cost/scope]. Our plan: [mitigation]. We need from you: [decision/help]. Revised ETA: [new date]."

Read the full file on GitHub · 95 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. 2mo ago First seen · 95 lines · 30 tokens per session scan A 7e07e057453d

Subscribe to this mod's changes

stakeholder-communication is a skill published in the GitHub repository uthumany/uthy-legacy-os (5 stars, last pushed 5mo ago), licensed MIT. It adds 30 tokens to every session and 906 once invoked, about $0.0001 per session on Opus 5.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-31.

Related

stakeholder-communication compared with skills from other repositories

stakeholder-communication next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
stakeholder-communicationuthumany/uthy-legacy-osSkill55mo agoMITA30Claude Code, Codex
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
systematic-debuggingobra/superpowersSkill314k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code
chat-pet-sprite-creationmicrosoft/vscodeSkill195ktodayMITA53Claude Code, Codex