CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

stakeholder-update-generator

Create compelling progress updates and release notes. Use when shipping a new feature or need to communicate progress to stakeholders.

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/stakeholder-update-generator/SKILL.md
SKILL.md
Quality
Evals
Security

Domain Context

This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.

Input Requirements

  • Context about your product, feature, or problem
  • Relevant data, research, or constraints (recommended but optional)
  • Clear articulation of what you're trying to achieve

Stakeholder Update Generator

When to Use

  • Shipping a new feature or product update
  • Need to communicate progress to stakeholders
  • Writing release notes for users
  • Preparing status updates for leadership
  • Documenting what changed in a sprint or milestone

What This Skill Does

Creates engaging, well-structured updates that communicate what shipped, why it matters, and what comes next.

Instructions

Help me write an engaging update for [product/feature/sprint] that is both informative and compelling. Include:

  1. High-level summary (2-3 sentences)
  2. Key accomplishments or new features
    • Feature/item name
    • Brief description
    • User benefit and impact
  3. Improvements and fixes
  4. Metrics or results (if available)
  5. What's next

Style preference: [Professional/Casual/Technical] Audience: [Users/Leadership/Engineering/Investors]

Changes to document: [List what shipped, improvements made, or progress achieved]

Best Practices

  • Lead with the most impactful changes
  • Focus on user benefits, not technical details (unless technical audience)
  • Use concrete metrics when possible ("50% faster" not "performance improvements")
  • Keep the tone consistent with your brand
  • Include visuals or screenshots if possible (note them in the text)
  • Add a call-to-action if relevant

Example

Input: Shipped notification center, improved search performance, fixed 15 bugs Output: Structured update highlighting "Never miss an important update" (notification center benefits), "Find anything in seconds" (search improvements), professional tone, metrics included (3x faster search), next steps mentioned

Further Reading

  • Stakeholder Update Templates
Repository

saski/arnesto

Path

.agents/skills/stakeholder-update-generator/SKILL.md

Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.