Report

What it does

When your agent uses it

• /report project-a
• What should I know
• Executive summary
• User wants a non-technical status update focused on outcomes not implementation

Example prompts

• “/report”
• “/report project-a”
• “report to me”
• “/report”

Requirements

• Pre-approved tools (allowed-tools): Read, Bash, Glob, Grep, Write, TaskCreate, TaskUpdate, TaskList, TaskGet

Workflow steps

7 steps, taken from the step headings in SKILL.md.

1. 1Parse Input
2. 2Gather Signals
3. 3Synthesize Executive Brief
4. 4Deliver
5. 5Optional: Save
6. 6Optional: Preview
7. 7Coaching Close

What it can do on your machine

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

• Tool permissions

  Pre-approves these tools, so the agent can use them without asking each time:

  • Read
  • Bash
  • Glob
  • Grep
  • Write
  • TaskCreate
  • TaskUpdate
  • TaskList
  • TaskGet

  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

Report loads about 1.7k tokens when it runs. Until then it costs about 86 tokens; SKILL.md has 510 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~86

When it runs · the whole SKILL.md, loaded when a task matches

~1.7k

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

• NotePre-approves every shell command (allowed-tools: Bash)SKILL.md

  allowed-tools: Read, Bash, Glob, Grep, Write, TaskCreate, TaskUpdate, TaskList, TaskGet

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 kv0906/pm-kit at commit 2cb5d9f, republished under its MIT licence (© kv0906). 510 words, ~1,745 tokens.

name

report

description

Executive briefing in plain language — report to me like I'm the CEO or product owner. Business impact and user impact only, no jargon. Use for "/report", "/report project-a", "report to me", "brief me", "what should I know", "executive summary", or when user wants a non-technical status update focused on outcomes not implementation.

allowed-tools

Read, Bash, Glob, Grep, Write, TaskCreate, TaskUpdate, TaskList, TaskGet

user-invocable

true

/report
/report project-a
/report all
/report project-a --week
/report all --preview
/report project-a --save --preview

TaskCreate: "Gather vault signals"
  activeForm: "Reading vault for executive signals..."

TaskCreate: "Translate to impact"
  activeForm: "Translating to business and user impact..."

TaskCreate: "Deliver brief"
  activeForm: "Preparing your briefing..."

# Briefing — {Project or All Projects}
**{Date}** · {Period covered}

## Bottom Line
{2-3 sentences. Most important thing first. What should they walk away knowing?}

## What Users Get (or Will Get)
- {Shipped capabilities in user language}
- {In-progress capabilities — expected value, not ETA unless due date exists}

## Business Impact
- {Revenue, risk reduction, speed, cost, compliance, trust — only what's evidenced in vault}

## What's at Risk
- {Open blockers translated to user/business consequences}
- {Overdue items flagged clearly}

## Decisions Made (Recent)
- {Decision → why it matters to product/business, not technical rationale}

## Needs Your Attention
- {Explicit asks: approve, escalate, decide, unblock}
- {If nothing: "No decisions needed from you this period."}

# Briefing — Project A
**2026-06-29** · Jun 22 – Jun 29

## Bottom Line
Checkout is live for most users, but peak-hour failures are still possible until we resolve the API limit blocker. No decisions needed from you today.

## What Users Get (or Will Get)
- Company sign-in is live — fewer password reset support tickets
- Order shipping alerts are in progress — users will know when packages leave the warehouse

## Business Impact
- Sign-in migration reduces support load and improves enterprise deal readiness
- Shipping alerts expected to cut "where is my order?" contacts

## What's at Risk
- API rate limits may cause checkout failures during promotions — backend team owns fix, due Friday

## Decisions Made (Recent)
- Chose PostgreSQL for billing data — stronger protection for payment records

## Needs Your Attention
- No decisions needed from you this period.

---
The one thing I'd escalate: API rate limit blocker before next marketing push.

No meaningful updates in the last 7 days for {project}.
Suggest: run /daily to start capturing, or widen with --since.

© kv0906, MIT. 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 .claude/skills/report of kv0906/pm-kit.

Open the folder on GitHubat commit 2cb5d9f