stakeholder-update SKILL.md skillA
stakeholder-update from broomva/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add broomva/skills/stakeholder-update@git:20260628.9edbf07Pins git:20260628.9edbf07 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- broomva/skills
- Path
skills/cadence/stakeholder-update/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260628.9edbf07, committed Jun 28, 2026
- Size
- 2,886 bytes
- Repository stars
- 4
- License
- MIT
Takes one set of project facts and generates three versions: technical for engineering, business-impact for leadership, and customer-facing for success teams. Use when the user says "stakeholder update", "write an update", "communicate this to different audiences", "translate for leadership", "customer-facing version", or needs to communicate the same information to different audiences.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Stakeholder Update One set of facts → three audience-specific versions. ## Workflow 1. **Gather the facts** — Accept raw project facts from the user. These can be: - A list of bullet points - A technical doc or PR description - A conversation summary - A vault note path 2. **Extract the core** — Identify: - What changed (the facts) - Why it matters (the impact) - What's next (the action items) - Any risks or blockers 3. **Generate three versions**: ### Version 1: Technical (Engineering) - Lead with what changed technically - Include relevant code/architecture details - Reference PRs, commits, or technical docs - Use precise technical language - Focus on: implementation details, technical debt, performance metrics ### Version 2: Business Impact (Leadership) - Lead with business outcome - Translate technical changes to business metrics - Include timeline and resource implications - Use clear, jargon-free language - Focus on: revenue impact, risk reduction, strategic alignment, timeline ### Version 3: Customer-Facing (Success Teams) - Lead with user benefit - Explain changes in terms of user experience - Include any action items for customers …
Read the whole file at its exact version.
How to install
mdr add broomva/skills/stakeholder-update@sha256:5d13733e80e62c3dThe line at the top of this page pins the label git:20260628.9edbf07, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_zufplrdwfqqjc3s5)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Jun 28, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (2886 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
broomva/skills · 4 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zufplrdwfqqjc3s5 GET https://markdownregistry.com/api/v1/resolve?ref=broomva/skills/stakeholder-update GET https://markdownregistry.com/api/v1/blob/5d13733e80e62c3d418069282c281225cfa5bb5e5688ebe9d4b1c112888a10aa
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.