New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Exec Summary

by mvschwarz in mvschwarz/openrig

Generate a 1-2 page executive summary for a feature — orients sales, leadership, and engineering from a single document.

Apache-2.0Auto-check passedWriting & Content

Install Exec Summary

skills CLI
$ npx skills add mvschwarz/openrig --skill exec-summary -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install mvschwarz/openrig exec-summary --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/mvschwarz/openrig.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/_canonical/pm/exec-summary .claude/skills/exec-summary && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
exec-summary
GitHub stars
5.5k
Token cost
~723 tokens
SKILL.md length
171 words
Files
1
Skills in repo
49
Repo updated
First seen
Licence
Apache-2.0

At a glance

Generate a 1-2 page executive summary for a feature — orients sales, leadership, and engineering from a single document.

  • Works in 4 steps: SPEC.md — acceptance criteria, business… → background.md — customer drivers,… → validation.md — demand evidence, status… → …
  • Tasks that involve OKRs and executive reporting
  • SKILL.md covers What You Produce, Sources to Read, Output Structure and Writing Guidelines
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Exec Summary is an agent skill from mvschwarz/openrig. Generate a 1-2 page executive summary for a feature — orients sales, leadership, and engineering from a single document.

Its SKILL.md is about 720 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Writing & Content, covering OKRs and executive reporting and Summarization. The repository describes itself as: Build your own network of agents from Claude Code, Codex and Pi: persistent teams with roles, shared context and owned work. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve OKRs and executive reporting
  • Tasks that involve Summarization

Example prompts

  • “/exec-summary”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. SPEC.md — acceptance criteria, business rules, scope, user stories
  2. background.md — customer drivers, competitive context, regulatory considerations
  3. validation.md — demand evidence, status quo, desperate user, narrowest wedge
  4. supporting/mockup-ascii.md — visual mockups (pull 2-3 key screens)

What it can do on your machine

Read from SKILL.md and the folder at commit a7fed63. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Exec Summary loads about 723 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 171 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~33
When it runs · the whole SKILL.md, loaded when a task matches
~723

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from mvschwarz/openrig at commit a7fed63, republished under its Apache-2.0 licence (© mvschwarz). 171 words, ~723 tokens.

Download SKILL.mdSave it as .claude/skills/exec-summary/SKILL.md (or your agent's skills folder).
name
exec-summary
description
Generate a 1-2 page executive summary for a feature — orients sales, leadership, and engineering from a single document.

You generate an executive summary for a feature that's ready for development. The summary orients three audiences from one document: sales (pitch), leadership (strategy), and engineering (behavioral overview).

What You Produce

A single executive-summary.md file in the feature folder. 600-800 words excluding mockups and FAQ. Written in present tense as if the feature already exists.

Sources to Read

Before writing, silently gather all context from the feature folder:

  1. SPEC.md — acceptance criteria, business rules, scope, user stories
  2. background.md — customer drivers, competitive context, regulatory considerations
  3. validation.md — demand evidence, status quo, desperate user, narrowest wedge
  4. supporting/mockup-ascii.md — visual mockups (pull 2-3 key screens)

Output Structure

markdown
---
title: "Executive Summary: [Feature Name]"
feature: [feature-folder-name]
status: [ready | in-progress | shipped]
jira: [ticket key]
updated: [today's date]
---

# [Feature Name]

## The Problem
[2-3 sentences. Customer pain in their language. Name real customers/prospects.]

## The Solution
[2-3 sentences. What we built, present tense. No jargon.]

## Who It's For
[Primary personas + named customers/prospects waiting for this.]

## Why Now
[Deals it unblocks, competitive gap it closes, what it enables next.]

## How It Works
[5-8 key capabilities. Describe actual user-facing behavior — enough for a dev to understand what to build.]

## Key Decisions
[5-8 non-obvious business rules and design choices. Focus on surprising or counter-intuitive ones.]

## Visual Preview
[2-3 ASCII mockup screens from supporting/ — the key screens that tell the story.]

## What We're NOT Building
[5-8 key out-of-scope items with brief reason.]

## Dependencies & Sequencing
[What must ship first. Cross-feature dependencies. Prerequisites.]

## Success Metrics
[2-4 measurable outcomes. Mix of usage and business metrics.]

## FAQ

### For Sales
[2-3 questions. When available, what to tell prospects, competitive positioning.]

### For Leadership
[2-3 questions. Opportunity cost, strategic fit, risks.]

### For Engineering
[2-3 questions. Dependencies, known risks, what's deferred, data model implications.]

Writing Guidelines

  • Present tense throughout. Write as if the feature exists.
  • Customer-readable language. A prospect should understand sections 1-5.
  • Be specific, not vague. Name deals, dollar amounts, competitors.
  • Key Decisions should surprise. Don't list obvious things.
  • Mockups are curated. Pick the 2-3 that tell the story.
  • FAQ answers should be direct. No hedging.
  • Hard cap: 2 pages for core content. FAQ can be a third page.

© mvschwarz, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/_canonical/pm/exec-summary of mvschwarz/openrig.

Open the folder on GitHubat commit a7fed63

Compare with similar skills

Exec Summary next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Exec Summary compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Exec Summary this skillmvschwarz/openrig5.5k—~723Automated safety check: PassApache-2.0
Board Pre Readmohitagw15856/pm-claude-skills1.4k—~889Automated safety check: PassMIT
Reportmicrosoft/data-formulator18k—~1.5kAutomated safety check: PassMIT
Executive Summary Generatornimrodfisher/data-analytics-skills465—~699Automated safety check: PassMIT
Performance Reportindranilbanerjee/digital-marketing-pro8541 repos~1.1kAutomated safety check: PassMIT
Board Meeting Prepw95/awesome-claude-corporate-skills235—~3.2kAutomated safety check: PassMIT

Similar skills

  • Board Pre Read

    mohitagw15856/pm-claude-skills

    Write a board pre-read that's sent before the meeting so the meeting is about decisions, not status.

    1.4k GitHub stars~889 tokensUpdated yesterday
    Writing & ContentAuto-check passed

  • Report

    microsoft/data-formulator

    Official

    Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded…

    18k GitHub stars~1.5k tokensUpdated yesterday
    Writing & ContentAuto-check passed

  • Executive Summary Generator

    nimrodfisher/data-analytics-skills

    Create concise executive summaries from detailed analysis. An agent skill from nimrodfisher/data-analytics-skills.

    465 GitHub stars~699 tokensUpdated 12 days ago
    Writing & ContentAuto-check passed

  • Performance Report

    indranilbanerjee/digital-marketing-pro

    Turn marketing data into a stakeholder-ready performance report: executive summary, channel-by-channel KPI dashboard, trend analysis, anomaly alerts with root-cause hypotheses, and recommendations…

    854 GitHub starsUsed in 1 repo~1.1k tokens
    Business, Finance & HRAuto-check passed

  • Board Meeting Prep

    w95/awesome-claude-corporate-skills

    ACTIVATE when preparing for board meetings, creating board decks, drafting board materials, developing executive summaries for directors, writing talking points, crafting board agendas, addressing…

    235 GitHub stars~3.2k tokensUpdated 7 mo ago
    Business, Finance & HRAuto-check passed

  • Novel Outline

    eternityspring/shuohao-skills

    把一本小说改编成短剧大纲五件套：改编说明、人物表、爽点表、分集梗概、资产清单， 产出 outline.json + Markdown + 单页评审报告（KPI 带、关键决策、爽点时间轴、调度矩阵、场景概览、质量门）。

    4.2k GitHub stars~1.2k tokensUpdated 11 days ago
    Writing & ContentAuto-check: notes

More from mvschwarz/openrig

All 49 skills in this repo

  • OpenRig Upgrade Procedure

    mvschwarz/openrig

    Walks an agent through upgrading the OpenRig CLI and daemon one observed step at a time, keeping live seats alive and reconciling managed plugin files.

    5.5k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • OpenRig Software Factory

    mvschwarz/openrig

    Helps set up a continuing agent software team for a real repository with OpenRig, choosing between manual work, queue handoffs and an explicit Workflow.

    5.5k GitHub stars~2.5k tokensUpdated today
    Auto-check passed

  • Seat Continuity and Handover

    mvschwarz/openrig

    Separates a stable agent seat's identity from its changing occupant, and records honest, two-part provenance whenever one occupant replaces another.

    5.5k GitHub stars~2.1k tokensUpdated today
    Auto-check passed

  • Addressable Markdown Loader

    mvschwarz/openrig

    Loads one section of a Markdown file by its path#h2-slug address with a bundled resolver script, for use outside OpenRig's context library.

    5.5k GitHub stars~341 tokensUpdated today
    Auto-check passed

  • Vault User

    mvschwarz/openrig

    A skill your agent uses when checking the health of this rig's HashiCorp Vault or writing, reading, listing, deleting or explaining its secrets.

    5.5k GitHub starsUsed in 1 repo~451 tokens
    Auto-check passed

  • Agent Refocusing

    mvschwarz/openrig

    Re-grounds a long-running agent in the current product outcome by running a path-based trace to the root of its topology and work trees.

    5.5k GitHub stars~399 tokensUpdated today
    Auto-check passed

Categories

Questions about Exec Summary

What does Exec Summary do?

Generate a 1-2 page executive summary for a feature — orients sales, leadership, and engineering from a single document. Exec Summary is an agent skill from mvschwarz/openrig. Generate a 1-2 page executive summary for a feature — orients sales, leadership, and engineering from a single document.

When should I use Exec Summary?

Exec Summary fits situations like: tasks that involve OKRs and executive reporting; tasks that involve Summarization.

How do I install Exec Summary in Claude Code?

Run `npx skills add mvschwarz/openrig --skill exec-summary -a claude-code`. Or copy the skill folder (skills/_canonical/pm/exec-summary in mvschwarz/openrig) into .claude/skills/exec-summary in your project. Claude Code loads it when a task matches its description.

How do I install Exec Summary in Codex?

Run `npx skills add mvschwarz/openrig --skill exec-summary -a codex`. Or copy the skill folder (skills/_canonical/pm/exec-summary in mvschwarz/openrig) into .agents/skills/exec-summary in your project. Codex loads it when a task matches its description.

Can I use Exec Summary in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add mvschwarz/openrig --skill exec-summary -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/exec-summary, .gemini/skills/exec-summary, .github/skills/exec-summary and .opencode/skills/exec-summary in your project.

What does Exec Summary need to run?

SKILL.md names no scripts, command-line tools or credentials: Exec Summary is instructions for the agent only.

Does Exec Summary access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Exec Summary safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Exec Summary use?

Exec Summary is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Exec Summary use?

About 723 tokens (SKILL.md is roughly 2.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Exec Summary?

Skills that share tags, products or a category with Exec Summary: Board Pre Read (mohitagw15856/pm-claude-skills, 1.4k stars), Report (microsoft/data-formulator, 18k stars), Executive Summary Generator (nimrodfisher/data-analytics-skills, 465 stars) and Performance Report (indranilbanerjee/digital-marketing-pro, 854 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Exec Summary?

mvschwarz (a GitHub user) maintains it in mvschwarz/openrig, which has 5,542 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 7, 2026.

Source: mvschwarz/openrig on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.