foundation-stakeholder-update — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited foundation-stakeholder-update (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
<!-- PM-Skills | https://github.com/product-on-purpose/pm-skills | Apache 2.0 -->
A stakeholder update is async communication to readers who need to know the outcomes of a meeting. Primary audience is non-attendees; secondary audience is some attendees who want a reference version (came in late, stepped out, need something to forward).
Distinct from foundation-meeting-recap in audience, format, and purpose: the recap is a summary of what happened for people who were in the room; the stakeholder-update is a translation of outcomes into what-it-means for readers (tailored to their role, with technical-to-business translation where the audience warrants it).
Distinct from /discover-stakeholder-summary: that skill is about understanding stakeholders (input to the user's work). This skill is about communicating to stakeholders (output from the user's work).
This skill belongs to the Meeting Skills Family. It conforms to the Meeting Skills Family Contract.
foundation-meeting-recap./discover-interview-synthesis plus targeted comms.Per the family contract, this skill never blocks on interrogation. Default flow:
project/topicsgo or correctionsIf invoked with --go, skip the inference summary. The entire output is shareable content (per family contract. no separate summary block needed).
When asked to create a stakeholder update, follow these steps:
Parse frontmatter to extract meeting context, decisions, actions, outcomes. If no recap provided, accept raw meeting notes with a lower input-quality flag.
Scan same directory for prior stakeholder-update artifacts with matching project / topics. If found, reference the prior update in the frontmatter thread_continuation_of field.
Show inferred channel (if not specified), detected audience, proposed CTA, thread continuation status, translation candidates (flagged jargon or acronyms that may not land).
From the recap or notes, select 3-5 outcomes that matter to the target audience. Do not include everything from the recap. filter by audience relevance.
If action is needed: lead with it, not bury it If FYI-only: state explicitly in the TL;DR
Flag jargon and acronyms unlikely to land with the audience. Provide plainer alternatives. Keep a translations-applied log for user verification in the output's Generation context.
Other variants may be included as collapsible alternates for user flexibility. Remove all guidance blockquotes from the final artifact.
channel is in enumaudience_variant is in enumprimary_cta is non-empty (use "FYI-only" if no action needed)related_recap is a valid filename reference or flagged as raw-notes input## Shareable update section present with channel-tailored body (v1.1.0. replaces "entire output is shareable" from v1.0.0)YYYY-MM-DD_HH-MMtimezone_title_stakeholder-update-{channel}-{audience}.mdfoundation-meeting-recap. upstream: primary input source/discover-stakeholder-summary. distinct purpose (understanding stakeholders, not communicating to them)~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.