Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Stakeholder Communication

ASecurity

Use when updating the stakeholder - report in outcome language (what changed for users, what's next, what decision is needed), translate technical detail, and surface risks early

109 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgoperformance

Security Analysis

A100/100

Scanned 10/2/2026

$npx -y skills add makifbaysal/tasktrooper --skill stakeholder-communication --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Stakeholder Communication?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Stakeholder Communication
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/makifbaysal-stakeholder-communication/badge)](https://www.skillsdirectory.com/skills/makifbaysal-stakeholder-communication)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: stakeholder-communication
category: pm
description: Use when updating the stakeholder - report in outcome language (what changed for users, what's next, what decision is needed), translate technical detail, and surface risks early
source: anthropics/knowledge-work-plugins stakeholder-update (Apache-2.0), adapted
---
# 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.

Attribution

makifbaysalmakifbaysal
View sourceSee grades on GitHubMore from makifbaysal →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →