exec-summary

exec-summary is a skill for Claude Code from DavidROliverBA/ArchitectKB. It costs 9 tokens per session (1,252 once invoked), scanned A, original, MIT.

A tool that turns technical notes—such as architecture decisions, project records, or documentation pages—into summaries for business readers.

In plain words
What is it for?
Use it to prepare board updates, management briefings, stakeholder communications, and other non-technical summaries.
Why use it?
It removes technical detail that executives, managers, or other stakeholders may not need while preserving business impact, risks, costs, and timing.

Skill for Claude Code

Written for Claude Code: arguments in frontmatter.

Good fit Use it to prepare board updates, management briefings, stakeholder communications, and other non-technical summaries.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/davidroliverba/architectkb/exec-summary
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add DavidROliverBA/ArchitectKB --skill exec-summary
Clone the repo
git clone --depth 1 https://github.com/DavidROliverBA/ArchitectKB

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for exec-summary

README.md
[![agentmods](https://agentmods.dev/badge/skills/davidroliverba/architectkb/exec-summary/github.svg)](https://agentmods.dev/skills/davidroliverba/architectkb/exec-summary)
Your own site
<a href="https://agentmods.dev/skills/davidroliverba/architectkb/exec-summary"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/exec-summary/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for exec-summary

Your own site · 80×15
<a href="https://agentmods.dev/skills/davidroliverba/architectkb/exec-summary"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/exec-summary.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,252 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00009 $0.01252
Opus 5.5 $0.00004 $0.00501
Sonnet 5.5 $0.00002 $0.00250
Haiku 4.5 $0.00001 $0.00125

Measured 1mo ago against content hash 8ba9fa5b5483, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

exec-summary scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/exec-summary/SKILL.md · 215 lines

How it starts

The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/exec-summary Skill

Generate a non-technical executive summary from technical ADRs, Pages, or Project notes.

Purpose

Translate technical architecture content for non-technical stakeholders. Useful for:

  • Board presentations
  • Stakeholder updates
  • Management briefings
  • Cross-team communication

Usage

/exec-summary "ADR - API Gateway Selection"
/exec-summary "Project - AIIncidentProcessor" exec
/exec-summary "Page - Kafka Integration" manager

Instructions

  1. Read the source note completely

  2. Identify the audience (default: exec):

    • exec - C-suite, board level (business impact, risk, cost)
    • manager - Department heads (operational impact, timeline, resources)
    • stakeholder - Project stakeholders (what changes, how affects them)
  3. Extract key information:

    For ADRs:

    • What decision was made (one sentence)
    • Why it matters to the business
    • What it costs / saves
    • Key risks and mitigations
    • Timeline / when it takes effect

    For Projects:

    • What the project delivers
    • Business benefit
    • Current status (RAG)
    • Key milestones
    • Resources / budget

    For Pages:

    • What this document describes
    • Why it matters
    • Key takeaways
    • Actions required (if any)
  4. Generate summary using this template:

# Executive Summary: {{Title}}

**Generated:** {{date}}
**Source:** [[{{source note}}]]
**Audience:** {{audience}}

---

## One-Line Summary

{{Single sentence explaining what this is about in business terms}}

## Why This Matters

{{2-3 sentences on business impact - avoid technical jargon}}

## Key Points

- {{Point 1 - business language}}
- {{Point 2 - business language}}
- {{Point 3 - business language}}

## Impact

| Area | Impact |
|------|--------|
| **Cost** | {{cost impact or "No direct cost impact"}} |
| **Timeline** | {{when does this happen}} |
| **Risk** | {{key risk in plain language}} |
| **Benefit** | {{main business benefit}} |

## Recommendation / Decision

{{What was decided or what action is recommended - one paragraph}}

## Questions This Answers

- {{Question a stakeholder might ask}}
- {{Another likely question}}

---

*This summary was generated from technical documentation. For full details, see [[{{source note}}]].*

Read the full file on GitHub · 215 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 1mo ago First seen · 215 lines · 9 tokens per session scan A 8ba9fa5b5483

Subscribe to this mod's changes

exec-summary is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (53 stars, last pushed 7mo ago), licensed MIT. It adds 9 tokens to every session and 1,252 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens