analyze-documents

Feedforward-AI's avatarfrom Feedforward-AI

Analyzes all documents in a folder and creates a comprehensive summary. Use when asked to summarize documents, understand a collection of files, get an overview of materials, or analyze what's in a folder.

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 10, 2026
[Summarization]

When & Why to Use This Skill

This Claude skill automates the analysis of multiple documents within a folder to generate a structured, comprehensive summary. It extracts key metadata, identifies recurring themes, maps out timelines, and highlights important stakeholders, enabling users to quickly grasp the essence of large document collections and synthesize complex information without manual reading.

Use Cases

  • Project Onboarding: Quickly synthesize a folder of legacy project documents, memos, and reports to understand historical context and key decisions.
  • Research Synthesis: Analyze a collection of academic papers or market reports to identify recurring themes, data points, and gaps in current knowledge.
  • Internal Audit & Review: Scan through email threads and internal communications to map out timelines of events and identify key stakeholders involved in specific issues.
  • Information Management: Generate a high-level table of contents and summary for an unorganized corpus of files to facilitate better document discovery and organization.
nameanalyze-documents
descriptionAnalyzes all documents in a folder and creates a comprehensive summary. Use when asked to summarize documents, understand a collection of files, get an overview of materials, or analyze what's in a folder.

Document Analyzer

Analyzes all documents in a specified folder and produces a structured summary.

When to Use

  • User asks to "summarize the documents" or "what's in these files"
  • User wants an overview of a document collection
  • User needs to understand a corpus before diving deeper

Instructions

  1. List the documents: Use ls or find to identify all readable files in the target folder (typically docs/ for this course)

  2. Read each document: For each file, extract:

    • Document type (memo, email thread, report, slack export, etc.)
    • Author(s) and recipient(s) if applicable
    • Date or time period covered
    • Key topic or purpose (1-2 sentences)
    • Notable quotes or data points

  3. Identify patterns: Look for:

    • Recurring themes across documents
    • Key people who appear multiple times
    • Timeline of events
    • Tensions or conflicts
    • Unanswered questions

  4. Produce the summary:

Output Format

# Document Collection Summary

## Overview
[2-3 sentence high-level summary]

## Documents Analyzed
| File | Type | Date | Key Topic |
|------|------|------|-----------|
| ... | ... | ... | ... |

## Key Themes
1. [Theme 1]
2. [Theme 2]

## Key People
- **[Name]** - [Role/relevance]

## Timeline of Events
- [Date]: [Event]

## Open Questions
- [Question that documents raise but don't answer]

## Recommended Deep Dives
- [Specific document or topic worth examining more closely]

Tips

  • For large document sets (10+ files), consider grouping by type or theme
  • Pay attention to who's talking to whom—organizational dynamics matter
  • Look for what's NOT said as much as what is
  • Dates matter—sequence often reveals causation