stakeholder-update

Name: stakeholder-update
Availability: InStock
Author: Amplitude

Generate weekly stakeholder updates from metrics, bets, customer quotes, and highlights.

142|16|Updated Mar 20, 2026

Search Tags:#status report #stakeholder communication #product metrics #weekly update #leadership briefing

Ready to run

npx skills add https://github.com/amplitude/builder-skills --skill stakeholder-update-amplitude

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: stakeholder-update
Source: https://github.com/amplitude/builder-skills/tree/main/execution-skills/skills/stakeholder-update
Command: npx skills add https://github.com/amplitude/builder-skills --skill stakeholder-update-amplitude

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Leaders and cross‑functional teams often struggle to create concise, data‑rich weekly updates that keep everyone aligned on metrics, bets, and customer signals.

Core Features & Use Cases

Metrics Summary: Highlights key metric movements with context and goal status.
Bets in Progress: Provides status and impact of ongoing initiatives.
Customer Signal: Includes real quotes or feedback to add credibility.
Highlights & Callouts: Shares shout‑outs, experiments, and useful links.
Use Case: A product manager can quickly generate a weekly stakeholder briefing for leadership without manually stitching together numbers and narratives.

Quick Start

Write a weekly stakeholder update for my initiative using the current metrics, bets in progress, customer quotes, and highlights.

Frequently Asked Questions about stakeholder-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write a weekly stakeholder update with product metrics?▼

To write a weekly stakeholder update, input your raw product metrics, bet statuses, customer quotes, and optional dashboard links. The tool then generates a structured, skimmable narrative summarizing metric movements, ongoing initiatives, and highlights for leadership.

What should a leadership briefing include for a weekly status report?▼

A leadership briefing should include a metrics summary with goal status, bets in progress, customer signals like real quotes, and highlights or callouts. This ensures cross-functional teams and leaders stay aligned on ongoing initiatives and data-driven results.

How do I create a data-driven status report without manually stitching numbers and narratives?▼

You can generate a data-driven status report by providing raw context inputs such as metric values and customer feedback. The system automatically structures these inputs into a concise narrative, preventing the need to manually stitch numbers and narratives together.

Can I use this to generate a product update for cross-functional teams?▼

Yes, you can use this to generate a product or initiative update for cross-functional teams. It processes raw context inputs like bet status and metric values to produce concise, data-rich communications tailored for weekly alignment.

What raw context inputs do I need to provide to generate a stakeholder communication?▼

To generate stakeholder communication, you need to provide raw context inputs including metric values, bet status, customer quotes, and optional dashboard links. These elements are required to produce a structured, skimmable narrative for leaders.