executive-summary

Generate narrative executive summaries from GitHub conversations and meeting transcripts.

4|Updated Dec 23, 2025
One-click install
npx skills add https://github.com/jonmagic/skills --skill executive-summary
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: executive-summary
Source: https://github.com/jonmagic/skills/tree/main/skills/executive-summary
Command: npx skills add https://github.com/jonmagic/skills --skill executive-summary

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill creates formal, narrative executive summaries from GitHub conversations (issues, pull requests, discussions) and meeting transcripts (Zoom, Teams, etc.), enabling leaders to quickly understand decisions, trade-offs, and next steps.

Core Features & Use Cases

  • GitHub Conversations: Fetch complete conversations, apply the GitHub-specific rules, archive source transcripts to Transcripts/YYYY-MM-DD and store summaries in Executive Summaries/YYYY-MM-DD with dated structure.
  • Meeting Transcripts: Retrieve transcripts from provided URIs, attribute speakers, reference shared documents, and produce executive summaries with linked sources.
  • Output Organization: Consistently organize outputs by date to facilitate audit and archival.

Quick Start

Provide a GitHub issue URL or a meeting transcript URI to generate the corresponding executive summary.

Frequently Asked Questions about executive-summary

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

FAQPage Schema
How do I generate executive summaries from GitHub issues and pull requests?

To generate executive summaries from GitHub issues and pull requests, provide the conversation URL to produce a narrative summary of decisions and next steps, archiving sources to dated Transcripts and Executive Summaries folders.

Can I create leadership-ready summaries from Zoom and Teams meeting transcripts?

Yes, you can create leadership-ready summaries from Zoom and Teams meeting transcripts by providing the transcript URI; the skill attributes speakers, references shared documents, and outputs a narrative executive summary with linked sources.

What is the best way to organize meeting transcripts and executive summaries for auditing?

The best way to organize meeting transcripts and executive summaries for auditing is using date-based folders, archiving sources to Transcripts/YYYY-MM-DD and storing summaries in Executive Summaries/YYYY-MM-DD.

How does source-linking work for executive summaries generated from GitHub conversations?

Source-linking for executive summaries generated from GitHub conversations works by archiving the original issue or PR transcripts to a dated Transcripts directory and referencing them within the formal narrative summary.

Do I need any special dependencies to produce executive summaries from GitHub and meeting transcripts?

No special dependencies are required to produce executive summaries from GitHub and meeting transcripts; you only need access to the GitHub conversation URLs or meeting transcript URIs to generate the output.

What should I expect in an executive summary derived from a GitHub discussion?

An executive summary derived from a GitHub discussion is a formal narrative document highlighting leadership decisions, trade-offs, and next steps, structured by applying specific workflow rules to attribute statements and link sources.