Stakeholder Communication
rampstackco/claude-skills
Communicate effectively with stakeholders across functions and seniority levels.
Create and review stakeholder status updates, progress reports, and executive summaries.
Install Stakeholder Update
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill stakeholder-update -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace stakeholder-update --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/.curated/stakeholder-update .claude/skills/stakeholder-update && rm -rf skills-srcUse ~/.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/
Install the "stakeholder-update" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/stakeholder-update into .claude/skills/stakeholder-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-update", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/stakeholder-updateType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill stakeholder-update -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace stakeholder-update --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/.curated/stakeholder-update .agents/skills/stakeholder-update && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "stakeholder-update" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/stakeholder-update into .agents/skills/stakeholder-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-update", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill stakeholder-update -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace stakeholder-update --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/.curated/stakeholder-update .cursor/skills/stakeholder-update && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "stakeholder-update" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/stakeholder-update into .cursor/skills/stakeholder-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-update", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/jeremylongshore/tons-of-skills-marketplace.git --path skills/.curated/stakeholder-update--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill stakeholder-update -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace stakeholder-update --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/.curated/stakeholder-update .gemini/skills/stakeholder-update && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "stakeholder-update" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/stakeholder-update into .gemini/skills/stakeholder-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-update", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install jeremylongshore/tons-of-skills-marketplace stakeholder-updateInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill stakeholder-update -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/.curated/stakeholder-update .github/skills/stakeholder-update && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "stakeholder-update" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/stakeholder-update into .github/skills/stakeholder-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-update", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill stakeholder-update -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install jeremylongshore/tons-of-skills-marketplace stakeholder-update --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/.curated/stakeholder-update .opencode/skills/stakeholder-update && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "stakeholder-update" agent skill from https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/main/skills/.curated/stakeholder-update into .opencode/skills/stakeholder-update/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "stakeholder-update", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
stakeholder-update- GitHub stars
- 2.8k
- Token cost
- ~2.5k tokens
- SKILL.md length
- 1,211 words
- Files
- 2 (incl. references)
- Skills in repo
- 3,342
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create and review stakeholder status updates, progress reports, and executive summaries.
- Works in 5 steps: Lead with the headline — Don't bury the… → Use consistent structure — Same format… → Be honest about risks — Surface problems… → …
- The user needs to write concise upward communication
- SKILL.md covers Overview, Instructions, Update Structure and Principles, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Stakeholder Update is an agent skill from jeremylongshore/tons-of-skills-marketplace. Create and review stakeholder status updates, progress reports, and executive summaries. Use when the user needs to write concise upward communication. Trigger with "stakeholder update", "status update", "progress report", "update leadership", "weekly update", or "executive summary".
Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/evidence-and-review.md`). Compatibility notes: Designed for Claude Code
It sits in Writing & Content, covering Summarization and Internal communications. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.
When your agent uses it
- The user needs to write concise upward communication
- With stakeholder update
- Progress report
- Update leadership
Example prompts
- “stakeholder update”
- “status update”
- “progress report”
- “/stakeholder-update”
Requirements
- Compatibility (from SKILL.md): Designed for Claude Code
- Pre-approved tools (allowed-tools): Read, Glob, Grep
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Lead with the headline — Don't bury the lead
- Use consistent structure — Same format builds trust
- Be honest about risks — Surface problems early
- Include clear asks — What do you need from them?
- Keep it scannable — Executives skim
What it can do on your machine
Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobGrep
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
en.wikipedia.orgamazon.com
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.
Compatibility
Designed for Claude Code
From compatibility in the SKILL.md frontmatter.
Context cost
Stakeholder Update loads about 2.5k tokens when it runs, and up to ~2.8k if it reads all its reference files. Until then it costs about 76 tokens; SKILL.md has 1,211 words of instructions outside code blocks.
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 jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 1,211 words, ~2,543 tokens.
Download SKILL.mdSave it as
.claude/skills/stakeholder-update/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- stakeholder-update
- description
- Create and review stakeholder status updates, progress reports, and executive summaries. Use when the user needs to write concise upward communication. Trigger with "stakeholder update", "status update", "progress report", "update leadership", "weekly update", or "executive summary".
- allowed-tools
- Read, Glob, Grep
- compatibility
- Designed for Claude Code
- version
- 1.10.0
- author
- Ahmed Khaled Mohamed <ahmd.khaled.a.mohamed@gmail.com>
- license
- MIT
- argument-hint
- project or team
- tags
- productivity, stakeholder-update
- model
- inherit
- effort
- medium
- user-invocable
- true
Stakeholder Update Skill
Overview
Turn current evidence into a concise update that leads with status, names risks plainly, and makes decisions or help requests explicit. Use the evidence and review checklist before sending it.
Use Glob to locate status artifacts, Grep to trace commitments, and Read to verify the data.
Instructions
Help create clear, concise stakeholder updates that communicate progress, risks, and asks effectively.
Authentication
Use only existing authenticated access when source systems are involved. Never request or expose credentials, tokens, or API keys; if access is unavailable, report the last verified timestamp.
Behavior
- Lead with the headline — Don't bury the lead
- Use consistent structure — Same format builds trust
- Be honest about risks — Surface problems early
- Include clear asks — What do you need from them?
- Keep it scannable — Executives skim
Tone
- Confident but not arrogant
- Transparent about challenges
- Action-oriented
- Respectful of reader's time
Advanced Patterns
- The bad news sandwich is dead — Don't bury risks between good news. Executives see through it and lose trust. Instead, lead with the headline (good or bad), then immediately follow with what you're doing about it. "Android delivery dropped to 88%. Root cause identified, fix deploying Monday, ETA to recover: 2 weeks." Confidence comes from having a plan, not from hiding problems
- Metric trend > metric snapshot — A single number is noise. Three data points are a trend. Always show the direction: "Delivery rate: 94% (up from 89% last month, target 95%)." The reader can instantly assess: are we improving, stable, or declining? Without trend, they'll ask — and you'll look unprepared
- The "asks" section is the point — Most PMs treat the asks section as an afterthought. But the entire update exists to get your asks answered. If you have no asks, you're sending a status report — send it as an email. If you have asks, lead with them in the TL;DR: "On track for March launch. Need: decision on scope cut by Friday."
- Audience-calibrated detail — Your skip-level wants 3 bullets. Your manager wants a page. Your team wants the full picture. Don't write one update for three audiences. Write the full version, then create progressively shorter summaries. The TL;DR section should stand alone as a complete Slack message
- Consistency builds trust — Send updates on the same day, in the same format, at the same cadence. When stakeholders know what to expect, they read it. When the format varies, they skim or ignore. The best update format is the one you actually send every week, not the perfect template you use once
Update Structure
## [Project/Team] Update — [Date]
### TL;DR
One sentence summary. What's the single most important thing to know?
### Status: On Track / At Risk / Off Track
### Progress This Period
- [Completed item 1]
- [Completed item 2]
- [In progress item]
### Key Metrics
| Metric | Target | Actual | Trend |
|--------|--------|--------|-------|
| [Metric 1] | X | Y | up/down/flat |
### Risks & Blockers
| Risk | Impact | Mitigation | Owner |
|------|--------|------------|-------|
| [Risk 1] | [High/Med/Low] | [What we're doing] | [Who] |
### Asks
- [ ] [What you need from leadership]
### Next Period
- [ ] [What's coming next]Principles
Headline First
Bad: "We had several meetings this week and discussed various topics..." Good: "We're on track to launch March 1st. Key risk: Android testing capacity."
Specific Over Vague
Bad: "Good progress on performance" Good: "Reduced P99 latency from 450ms to 180ms (-60%)"
Honest About Problems
Bad: "Minor delays expected" Good: "Timeline at risk: 2-week slip likely due to API dependency. We need [specific help]."
Clear Asks
Bad: "Would be helpful to have more resources" Good: "Requesting: 1 additional Android engineer for 3 weeks, or we slip by 2 weeks"
Examples
Example 1: Weekly Update
User: Help me write a weekly update for my team's work on push notification improvements.
Good Response:
Push Notifications Update — Week of Feb 10, 2026
TL;DR
Delivery rate hit 94% (target: 95%). Android token refresh fix deployed, monitoring results.
Status: At Risk
On track for delivery rate target, but Android reachability work is behind schedule.
Progress This Week
- Android token refresh fix deployed — Live for 10% of users, expanding Monday
- iOS delivery optimization — P99 latency down from 2.1s to 1.4s
- Rich media support — Design complete, engineering started (40% done)
- Quick reply buttons — Blocked on iOS 17 API approval
Key Metrics
| Metric | Target | This Week | Last Week | Trend |
|---|---|---|---|---|
| Delivery rate (iOS) | 95% | 96.2% | 95.8% | up |
| Delivery rate (Android) | 95% | 91.4% | 89.2% | up |
| P99 latency | <2s | 1.4s | 2.1s | up |
Risks & Blockers
| Risk | Impact | Mitigation | Owner |
|---|---|---|---|
| Quick reply blocked on Apple | High | Escalated to partner team, ETA next week | Ahmed |
| Android engineer out sick | Med | Redistributing work, 3-day slip possible | Michelle |
Asks
- Decision needed: Should we launch rich media without quick reply, or wait?
- Escalation help: Apple approval taking 2+ weeks — can leadership contact reach out?
Next Week
- Android token refresh: expand to 100%
- Rich media: complete implementation
- Quick reply: resolve Apple blocker
Adjust anything?
Show full SKILL.md (484 more words)Show less
Example 2: Executive Summary
User: Write an executive summary of our Q1 progress for leadership.
Good Response:
Client Messaging — Executive Summary
Bottom Line
Strong Q1. Delivered 3 of 4 planned initiatives. Push delivery rate at 94% (target: 95%), with clear path to close the gap in Q2. Team velocity improved 20% after process changes.
What We Shipped
| Initiative | Status | Impact |
|---|---|---|
| Android token refresh | Shipped | +5% delivery rate, +2M reachable users |
| Push performance optimization | Shipped | -60% latency (2.1s to 0.8s) |
| Inbox redesign | Shipped | +15% inbox open rate |
| Rich media push | 70% | Slipped to Q2 (Apple approval delay) |
Key Metrics
| Metric | Previous period | Current period | Target | Status |
|---|---|---|---|---|
| Push delivery rate | 89% | 94% | 95% | At Risk |
| Message success rate | 10% | 14% | 15% | At Risk |
| Team velocity (points/sprint) | 45 | 54 | 50 | On Track |
What Worked
- Focus on Android — Concentrated effort closed the iOS/Android delivery gap
- Process improvements — Async standups + clearer ownership = faster shipping
- Partner alignment — Early stakeholder involvement reduced late-stage churn
What Didn't
- Apple dependency — Underestimated approval timeline for new notification APIs
- Scope creep — Rich media grew 40% from original spec
- On-call burden — Team spent 15% of time on unplanned support
Q2 Priorities
- Close the delivery gap — 94% to 99% (Android token + FCM reliability)
- Ship rich media — Unblock Apple, launch by April
- Reduce support burden — Self-service tools for partners
Asks
- Headcount: Request 1 additional engineer for Q2 to maintain velocity
- Executive support: Apple escalation for notification APIs
- Decision: Invest in self-service tooling vs. dedicated support engineer?
Want me to adjust the framing or add more detail anywhere?
Example 3: Quick Status
User: I need a quick Slack update about a feature delay.
Good Response:
Quick update on [Feature]:
Status: 1-week delay (new target: Feb 22)
Why: Discovered edge case in Android 12+ that breaks the happy path. Fix is straightforward but needs testing.
Impact: No user-facing impact (feature not launched). Marketing aware and adjusting.
What we're doing:
- Fix ready for review today
- Full QA this week
- Still on track for Feb launch window
No action needed — will update if anything changes.
Good for Slack?
Prerequisites
- Claude Code with read access to project files
- Project status information: progress, metrics, risks, and blockers
- Awareness of the target audience (manager, VP, cross-functional peers)
Output
Structured stakeholder updates including TL;DR headline, traffic-light status, progress summaries, metric trends with context, risks with mitigations and owners, clear asks, and next-period plans calibrated to audience seniority.
Error Handling
When project metrics are unavailable, use qualitative progress indicators and flag the measurement gap as a risk. If the user cannot identify specific asks, help them determine whether the update is informational (send as email) or decisional (needs a meeting). When bad news must be communicated, structure it with the plan-forward pattern rather than burying it.
Resources
- BLUF (Bottom Line Up Front) -- lead-with-the-headline communication
- Pyramid Principle -- structured top-down communication
- RAG status reporting -- Red/Amber/Green project health
© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file (references) in skills/.curated/stakeholder-update of jeremylongshore/tons-of-skills-marketplace.
- SKILL.md
- references/evidence-and-review.md
Open the folder on GitHubat commit cfae287
Compare with similar skills
Stakeholder Update 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Stakeholder Update this skilljeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~2.5k | Automated safety check: Pass | MIT | |
| Stakeholder Communicationrampstackco/claude-skills | 945 | — | ~2.8k | Automated safety check: Pass | MIT | |
| 07 Bao Cao Marketingminhnv0807/ai-business-skills | 609 | — | ~3.6k | Automated safety check: Pass | MIT | |
| 07 Marketing Report Globalminhnv0807/ai-business-skills | 609 | — | ~2.9k | Automated safety check: Pass | MIT | |
| Strategic Narrative Generatormohitagw15856/pm-claude-skills | 1.4k | — | ~995 | Automated safety check: Pass | MIT | |
| Foundation Prioritized Action Planproduct-on-purpose/pm-skills | 716 | — | ~5.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
07 Bao Cao Marketing
minhnv0807/ai-business-skills
Dung khi can viet bao cao marketing cho nguoi khac doc — weekly 1 trang cho CEO, monthly day du, hoac strategy report theo quy.
07 Marketing Report Global
minhnv0807/ai-business-skills
A skill your agent uses when the user needs to WRITE a marketing report someone else will read — a one-page weekly for a CEO, a full monthly, or a quarterly strategy report with TL;DR, results…
Strategic Narrative Generator
mohitagw15856/pm-claude-skills
Generate the strategic story connecting a product roadmap to company goals in a form non-technical stakeholders can repeat.
Foundation Prioritized Action Plan
product-on-purpose/pm-skills
Produce a comprehensive, evidence-grounded prioritized action plan from any PM input (notes, transcripts, drafts, executive asks, Slack threads, or a raw situation).
Program Manager
borghei/Claude-Skills
Program management for multi-project coordination, portfolio governance, dependency tracking, benefits realization, charters, and steering-committee reporting.
More from jeremylongshore/tons-of-skills-marketplace
All 3,342 skills in this repoPerforming Security Code Review
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.
Adapting Transfer Learning Models
jeremylongshore/tons-of-skills-marketplace
Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.
Agent Context Loader
jeremylongshore/tons-of-skills-marketplace
Execute proactive auto-loading: automatically detects and loads agents.md files.
Aggregating Performance Metrics
jeremylongshore/tons-of-skills-marketplace
Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.
Analyzing Capacity Planning
jeremylongshore/tons-of-skills-marketplace
Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.
Analyzing Database Indexes
jeremylongshore/tons-of-skills-marketplace
Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.
Related
Questions about Stakeholder Update
What does Stakeholder Update do?
Create and review stakeholder status updates, progress reports, and executive summaries. Stakeholder Update is an agent skill from jeremylongshore/tons-of-skills-marketplace. Create and review stakeholder status updates, progress reports, and executive summaries.
When should I use Stakeholder Update?
Stakeholder Update fits situations like: the user needs to write concise upward communication; with stakeholder update; progress report; update leadership.
How do I install Stakeholder Update in Claude Code?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill stakeholder-update -a claude-code`. Or copy the skill folder (skills/.curated/stakeholder-update in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/stakeholder-update in your project. Claude Code loads it when a task matches its description.
How do I install Stakeholder Update in Codex?
Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill stakeholder-update -a codex`. Or copy the skill folder (skills/.curated/stakeholder-update in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/stakeholder-update in your project. Codex loads it when a task matches its description.
Can I use Stakeholder Update 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 jeremylongshore/tons-of-skills-marketplace --skill stakeholder-update -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-update, .gemini/skills/stakeholder-update, .github/skills/stakeholder-update and .opencode/skills/stakeholder-update in your project.
What does Stakeholder Update need to run?
SKILL.md names no scripts, command-line tools or credentials: Stakeholder Update is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Glob, Grep. Compatibility (from SKILL.md): Designed for Claude Code.
Does Stakeholder Update access the network?
SKILL.md names 2 domains. As links in the text: en.wikipedia.org and amazon.com. This is read from the text; nothing was executed.
Is Stakeholder Update 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 Update use?
Stakeholder Update is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Stakeholder Update use?
About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 243 tokens, read only when the agent opens those files.
What are the alternatives to Stakeholder Update?
Skills that share tags, products or a category with Stakeholder Update: Stakeholder Communication (rampstackco/claude-skills, 945 stars), 07 Bao Cao Marketing (minhnv0807/ai-business-skills, 609 stars), 07 Marketing Report Global (minhnv0807/ai-business-skills, 609 stars) and Strategic Narrative Generator (mohitagw15856/pm-claude-skills, 1.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Stakeholder Update?
jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.
Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.