stakeholder-communication

stakeholder-communication is a skill for Claude Code, Codex from makifbaysal/tasktrooper. It costs 37 tokens per session (483 once invoked), scanned A, original, Apache-2.0.

A stakeholder-communication guide for reporting work in terms of user outcomes rather than internal technical details. It also provides a format for surfacing risks and asking for decisions.

In plain words
What is it for?
It helps write progress updates, translate implementation details into user-facing effects, and frame decision requests with options, trade-offs, and recommendations.
Why use it?
It helps non-technical stakeholders understand what changed, what is next, and what may block progress. Early, clear risk reporting gives them time to respond.

Skill for Claude CodeCodex

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

Good fit It helps write progress updates, translate implementation details into user-facing effects, and frame decision requests with options, trade-offs, and recommendations.

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

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/makifbaysal/tasktrooper/stakeholder-communication/github.svg)](https://agentmods.dev/skills/makifbaysal/tasktrooper/stakeholder-communication)
Your own site
<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/stakeholder-communication"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/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/makifbaysal/tasktrooper/stakeholder-communication"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/stakeholder-communication.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 483 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.00037 $0.00483
Opus 5.5 $0.00015 $0.00193
Sonnet 5.5 $0.00007 $0.00097
Haiku 4.5 $0.00004 $0.00048

Measured 8d ago against content hash e71ee750d0c2, 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 8d 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.

catalog/agents/product-manager/skills/stakeholder-communication/SKILL.md · 57 lines

What it actually says

Stakeholder Communication

Overview

The stakeholder cares about outcomes, not mechanics. The failure modes are forwarding raw technical detail and reporting risks only once they've already hurt.

Core principle: Outcome language, and bad news early.

Rules

  • Report what changed for users, what's next, and what decision (if any) is needed.
  • Translate, don't forward. "Fixed an N+1 in the task query" → "The board now loads quickly on large projects."
  • Bad news early: report a risk when you detect it, not when it materializes.

Structure

Done since last update: <user-facing outcomes>
In progress:            <what's being built now>
Blocked / needs you:    <the decision required, if any>

Decision-request format

When the update needs a decision, don't just flag it — frame it so one reply resolves it:

Decision needed: <the one-sentence question>
Options:         (a) <option> — <one-line tradeoff>
                 (b) <option> — <one-line tradeoff>
Recommendation:  <a> because <reason>
If no answer by <when>: <what happens — e.g. "work stays queued behind it">

Worked Example

Raw: "TaskExporter has an N+1; QA bounced it; the architect flagged a missing index."

Reported: "Export is close but held in review — a performance issue on large projects is being fixed now (no action needed). Everything else from this batch is done. Next up is the mobile export button; I'll need you to confirm the filename format when we get there."

Common Mistakes

  • Forwarding jargon (N+1, nil deref, migration).
  • A "green" update that hides a known risk.
  • Reporting a slip only after the deadline passed.

Red Flags

  • The update contains a term a non-engineer wouldn't understand.
  • A risk you knew about last update surfaced as a surprise this update.
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. 8d ago First seen · 57 lines · 37 tokens per session scan A e71ee750d0c2

Subscribe to this mod's changes

stakeholder-communication is a skill published in the GitHub repository makifbaysal/tasktrooper (113 stars, last pushed yesterday), licensed Apache-2.0. It adds 37 tokens to every session and 483 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-10-05.

Related

Other skills, from other repositories

paperclip

Use for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and following company governance. Includes control plane API operations for assignments, comments, approvals, and routines.

paperclipai/paperclip · 54 tokens

paperclip

Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.

paperclipai/paperclip · 43 tokens

paperclip-board

Manage a Paperclip company as a board member via chat. Use when the user wants onboarding, company or agent management, approvals, task monitoring, cost oversight, or work product review in the Paperclip control plane.

paperclipai/paperclip · 47 tokens

paperclip-distill

Use when an operation issue is a Paperclip cursor-window, distill, or backfill. Turn source-bundled Paperclip activity into wiki-insightful project standups, durable project pages, decisions, and history without asset dereferencing.

paperclipai/paperclip · 54 tokens

summarize-status

Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language status, streaming progress as it works.

paperclipai/paperclip · 0 tokens

paperclip-task-bridge

Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.

paperclipai/paperclip · 27 tokens