Skip to content

hoavdc/CodexKit / skills/codexkit-report-summarizer

codexkit-report-summarizer

Verified

Condense long reports, documents, or data exports into structured summaries with key findings, implications, and recommended actions. Use when the work is distilling dense content for busy readers. Do not use for original analysis, strategy formulation, or when the source material needs expert interpretation beyond summarization.

FileKindSize
SKILL.mdskill md3.9 KB
agents/openai.yamlconfig174 B
examples/common-mistakes.mdmarkdown894 B
examples/good-output.mdmarkdown1.5 KB
verification/checklist.mdmarkdown1.4 KB

examples/good-output.md

View on GitHub
# Good Output Example - Report Summarizer

## Scenario

The user asks for an executive summary of a quarterly customer support operations report.

## Good Output

```markdown
## Executive Summary - Q2 Support Operations

### One-Line Takeaway
Support volume grew 18% quarter over quarter, but resolution speed improved because the team deflected more how-to requests through documentation.

### Key Findings
- Ticket volume increased from 8,400 to 9,912, mainly from onboarding-related questions.
- Median first response time improved from 4.2 hours to 2.9 hours after staffing changes.
- Billing tickets still have the slowest resolution time at 3.8 days median.
- CSAT fell from 91% to 87%, with pricing confusion appearing in 14% of negative comments.

### Implications
- Documentation is reducing simple support load, but billing experience remains a friction point.
- The CSAT decline is concentrated enough to assign a specific owner rather than treating it as a broad service problem.

### Recommended Actions From Source
1. Update billing FAQ and in-product invoice copy by July 15.
2. Route billing tickets to a specialized queue for a four-week pilot.
3. Review onboarding documentation search logs weekly.

### Caveats
The report does not segment CSAT by customer tier, so enterprise impact is unclear.
```

## Why It Works

- It keeps the original numbers visible.
- It separates findings, implications, actions, and caveats.
- It does not add recommendations beyond the source.
- It highlights the one thing leadership should verify next.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 468kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 319kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 319kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 319kUpdated Claude CodeCodexVerifiedInstall