Skip to content

hoavdc/CodexKit / skills/codexkit-document-summarizer

codexkit-document-summarizer

Unverified

Summarize document-heavy inputs such as memos, policies, PDFs, research notes, proposals, and multi-document packets. Use when users need key points, obligations, questions, and action implications from documents.

Document Summarizer

When to Use

  • Summarizing long documents that are not formal business reports.
  • Extracting key points from policies, proposals, PDFs, research notes, or document packets.
  • Preparing a quick readout before deciding whether to read the full document.
  • Comparing multiple documents for themes, contradictions, or action items.

Procedure

Step 1 - Identify Document Type

Classify the source: policy, proposal, memo, research, contract-like document, transcript, academic paper, operating document, or mixed packet.

Step 2 - Extract Core Content

Capture:

  • purpose
  • main claims or findings
  • dates, parties, obligations, or deadlines
  • decisions requested
  • open questions
  • risks or caveats

Step 3 - Separate Summary From Interpretation

Keep source-backed summary separate from analysis or recommendation. Mark anything inferred.

Step 4 - Produce Audience-Specific Output

Adapt format for executive, manager, student, legal/compliance reviewer, or team member.

Step 5 - Add Reading Guidance

State which sections deserve human review and why.

Inputs

InputRequiredFormat
Document text or excerptYesPasted text, extracted notes, OCR
Document typeRecommendedProposal, policy, memo, research, etc.
AudienceRecommendedExecutive, manager, student, team
Desired lengthOptional5 bullets, one page, detailed brief
Focus areaOptionalRisks, obligations, actions, decisions

Output

## Document Summary - [Document Name]

### One-Line Takeaway
[Core point]

### Key Points
- [Point backed by source]

### Actions / Decisions
| Item | Owner | Deadline | Source Note |
|------|-------|----------|-------------|

### Risks / Caveats
- [Risk]

### Needs Human Review
- [Section or issue]

Quality Criteria

  • The summary stays faithful to the document and does not invent missing facts.
  • Important dates, obligations, numbers, and decisions are preserved.
  • Source-backed summary is separated from interpretation.
  • The output states what was not reviewed or could not be verified.
  • High-risk documents are flagged for expert review.

Verification (4C)

CheckQuestion
CorrectnessAre all summarized claims traceable to the document text?
CompletenessAre key points, actions, deadlines, risks, and review needs captured?
Context-fitDoes the summary match the audience and intended decision?
ConsequenceWhat could be misread if the user relies only on the summary?

Edge Cases

  • OCR or extraction errors - Flag low confidence and avoid definitive claims.
  • Legal, financial, or compliance content - Summarize only and recommend expert review before acting.
  • Multiple documents conflict - Show a contradiction table instead of choosing a winner.
  • Very long packet - Summarize by section and list skipped or unread portions.

Examples

Prompt: "Summarize this vendor proposal for an operations manager. Focus on deliverables, pricing assumptions, risks, and questions for the vendor."

Good pattern: "The proposal assumes customer data export is available by June 1. This is a dependency, not a confirmed commitment."

Definition of Done

  • The user can decide whether to read the full document.
  • Important actions and risks are visible.
  • Uncertainty and review needs are explicit.

Changelog

  • v1.0.0 - Initial release
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: 464kUpdated Claude CodeCodexVerifiedInstall
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: 464kUpdated 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: 318kUpdated Claude CodeCodexUnverifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 318kUpdated Claude CodeCodexUnverifiedInstall