stakeholder-report-writer

Translate technical findings into audience-appropriate narratives for executive decision-makers.

Updated Mar 5, 2026
One-click install
npx skills add https://github.com/zivtech/joyus-desktop --skill stakeholder-report-writer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stakeholder-report-writer
Source: https://github.com/zivtech/joyus-desktop/tree/main/.claude/skills/stakeholder-report-writer
Command: npx skills add https://github.com/zivtech/joyus-desktop --skill stakeholder-report-writer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill bridges the gap between technical teams and non-technical decision-makers by translating dense research, data, or technical findings into clear, actionable narratives.

Core Features & Use Cases

  • Audience-Specific Translation: Maps complex findings to the specific needs of boards, funders, or legislators.
  • Equity-Focused Reporting: Ensures population-specific outcomes are surfaced rather than buried in aggregate statistics.
  • Use Case: Use this when you have a set of complex clinical trial results or operational metrics that need to be presented to a board of directors who require a clear recommendation rather than a technical deep dive.

Quick Start

Use the stakeholder-report-writer skill to create a report plan for the technical findings in the attached research document.

Frequently Asked Questions about stakeholder-report-writer

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

FAQPage Schema
How do I translate complex technical findings into an executive report?▼

To translate complex technical findings into an executive report, you need structured input of your research data and clear audience requirements to generate a comprehensive narrative strategy. This bridges the gap between technical teams and non-technical decision-makers.

What is the best way to write equity-focused stakeholder reports?▼

Writing equity-focused stakeholder reports involves mapping complex findings to specific audience needs while ensuring population-specific outcomes are surfaced rather than buried in aggregate statistics. This approach generates clear, actionable narratives for diverse groups.

Can I convert clinical trial results into a board-level recommendation?▼

Yes, you can convert clinical trial results into a board-level recommendation by providing the technical findings as structured input. The process distills dense research data into a clear recommendation rather than a technical deep dive.

Does this approach work for translating operational metrics for non-technical decision-makers?▼

Yes, this approach works for translating operational metrics for non-technical decision-makers by mapping dense operational data to the specific needs of boards, funders, or legislators, ensuring non-technical audiences receive actionable narratives.

What input do I need to generate an audience-appropriate narrative?▼

To generate an audience-appropriate narrative, you need structured input of technical findings and a clear definition of audience requirements. This allows the process to accurately map research data to the specific needs of executive decision-makers.