Agent skill

Large Document Reader

by wentorai in wentorai/research-plugins

Split and read long documents chapter-by-chapter for structured analysis

MITAuto-check passedAgent Workflows

Install Large Document Reader

skills CLI
$ npx skills add wentorai/research-plugins --skill large-document-reader -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install wentorai/research-plugins large-document-reader --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tools/document/large-document-reader .claude/skills/large-document-reader && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
large-document-reader
GitHub stars
298
Used in
1 other repo
Token cost
~2k tokens
SKILL.md length
489 words
Files
1
Skills in repo
428
Repo updated
First seen
Licence
MIT

At a glance

Split and read long documents chapter-by-chapter for structured analysis

  • Works in 3 steps: Survey → Sequential Deep Reading → Synthesis
  • Agent Workflows work in your project
  • SKILL.md covers Overview, Document Splitting Strategy, Structured Reading Workflow and Cross-Session Persistence, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Large Document Reader is an agent skill from wentorai/research-plugins. Split and read long documents chapter-by-chapter for structured analysis

Its SKILL.md is about 2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: 350+ academic research skills, MCP configs, and plugins for Research-Claw and AI agents. The licence is MIT.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/large-document-reader”

Requirements

  • Python 3

Workflow steps

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

  1. Survey
  2. Sequential Deep Reading
  3. Synthesis

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    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 python and json).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Links to these hosts (documentation or services it may open):

    • github.com
    • python-docx.readthedocs.io
    • pymupdf.readthedocs.io

    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

Large Document Reader loads about 2k tokens when it runs. Until then it costs about 24 tokens; SKILL.md has 489 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~24
When it runs · the whole SKILL.md, loaded when a task matches
~2k

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

Auto-check passed

The automated check found no risky patterns in SKILL.md.

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 wentorai/research-plugins at commit bf44b3c, republished under its MIT licence (© wentorai). 489 words, ~1,955 tokens.

Download SKILL.mdSave it as .claude/skills/large-document-reader/SKILL.md (or your agent's skills folder).
name
large-document-reader
description
Split and read long documents chapter-by-chapter for structured analysis

Large Document Reader

Split long documents (books, reports, theses, legal filings, technical manuals) into structured chapters or sections for systematic, chapter-by-chapter reading and analysis within LLM context windows.

Overview

Large Language Models have finite context windows, and even models with 100K+ token limits can lose accuracy on information buried in the middle of very long inputs. Academic researchers frequently work with documents that exceed practical context limits: doctoral theses (200+ pages), government reports, book-length monographs, legal case compilations, and multi-volume technical standards.

This skill provides a systematic approach to splitting large documents into semantically meaningful chapters or sections, maintaining cross-references between parts, and reading each section with full comprehension. Rather than naive fixed-size chunking that breaks mid-sentence or mid-argument, this approach respects document structure -- headings, chapter breaks, section markers, and logical boundaries.

The result is a structured reading experience where each chapter is analyzed in full context, summaries are maintained across sessions, and the reader can navigate directly to any section of interest. This is especially valuable for literature reviews, systematic reviews, and comprehensive document analysis tasks.

Document Splitting Strategy

Hierarchy of Split Points

Documents should be split at the highest-level structural boundary that keeps each chunk within the target size:

PriorityBoundary TypeMarkers
1Part/VolumePART I, Volume 2, page breaks with Roman numerals
2ChapterChapter 1, CHAPTER, numbered headings level 1
3Section1.1, Section, headings level 2
4Subsection1.1.1, headings level 3
5Paragraph breakDouble newline, indentation change
6Sentence boundaryPeriod + space + capital letter
Splitting Algorithm
python
def split_document(text, max_tokens=8000, overlap_tokens=200):
    """Split document respecting structural boundaries."""
    # Step 1: Detect document structure
    chapters = detect_chapters(text)

    if not chapters:
        # Fallback: split by sections
        chapters = detect_sections(text)

    if not chapters:
        # Fallback: split by paragraphs with size limit
        chapters = split_by_paragraphs(text, max_tokens)

    # Step 2: Merge small adjacent sections
    merged = merge_small_sections(chapters, min_tokens=500)

    # Step 3: Split oversized sections
    final = []
    for chapter in merged:
        if count_tokens(chapter.text) > max_tokens:
            sub_parts = split_by_paragraphs(chapter.text, max_tokens)
            for i, part in enumerate(sub_parts):
                final.append(Section(
                    title=f"{chapter.title} (Part {i+1})",
                    text=part,
                    index=len(final)
                ))
        else:
            chapter.index = len(final)
            final.append(chapter)

    # Step 4: Add overlap for continuity
    for i in range(1, len(final)):
        final[i].context_prefix = get_last_n_tokens(
            final[i-1].text, overlap_tokens
        )

    return final
Structure Detection Patterns
python
import re

CHAPTER_PATTERNS = [
    r'^#{1,2}\s+.+',                          # Markdown H1/H2
    r'^Chapter\s+\d+',                         # "Chapter 1"
    r'^\d+\.\s+[A-Z]',                        # "1. Introduction"
    r'^PART\s+[IVX]+',                         # "PART III"
    r'^\\(chapter|section)\{',                 # LaTeX commands
    r'^\f',                                    # Form feed (page break)
]

def detect_chapters(text):
    sections = []
    current_title = "Preamble"
    current_start = 0

    for match in re.finditer('|'.join(CHAPTER_PATTERNS), text, re.MULTILINE):
        if match.start() > current_start:
            sections.append(Section(
                title=current_title,
                text=text[current_start:match.start()].strip()
            ))
        current_title = match.group().strip()
        current_start = match.start()

    sections.append(Section(title=current_title, text=text[current_start:].strip()))
    return sections

Structured Reading Workflow

Phase 1: Survey

Read the table of contents, introduction, and conclusion first to build a mental model of the document's argument structure:

1. Extract and display Table of Contents
2. Read Introduction (typically Chapter 1)
3. Read Conclusion (typically last chapter)
4. Generate a document map: chapter titles + estimated page counts
5. Identify key themes and arguments
Phase 2: Sequential Deep Reading

Process each chapter with a standardized analysis template:

For each chapter:
  - Chapter title and position in document
  - Key arguments or findings (3-5 bullet points)
  - Methodology described (if applicable)
  - Data or evidence presented
  - Connections to previous chapters
  - Open questions or points for follow-up
  - Notable quotes or passages (with page/section references)
Show full SKILL.md (194 more words)Show less
Phase 3: Synthesis

After all chapters are read, generate cross-cutting analyses:

- Thematic summary across all chapters
- Argument progression map
- Methodology comparison (if multiple studies)
- Contradiction or tension identification
- Gap analysis relative to research questions

Cross-Session Persistence

For documents that take multiple sessions to read, maintain a reading state file:

json
{
  "document": "thesis_smith_2024.pdf",
  "total_sections": 24,
  "completed": [0, 1, 2, 3, 4, 5],
  "current": 6,
  "summaries": {
    "0": "Preamble: Defines scope of study on...",
    "1": "Chapter 1: Introduction to the problem of...",
    "2": "Chapter 2: Literature review covering..."
  },
  "themes": ["data governance", "algorithmic fairness", "institutional trust"],
  "open_questions": [
    "How does the author reconcile findings in Ch3 with Ch5?"
  ]
}

Format-Specific Handling

FormatToolNotes
PDFpdfplumber, PyMuPDFExtract text with layout awareness
EPUBebooklibChapters are HTML files in the spine
DOCXpython-docxHeadings define structure
LaTeXRegex on \chapter, \sectionNative structure markers
HTMLBeautifulSoupSplit on <h1>, <h2> tags
Plain textHeuristic detectionUse blank lines, indentation, page breaks

Best Practices

  1. Preserve cross-references: When a chapter references "as discussed in Section 3.2," maintain a reference index so the reader can retrieve that section.
  2. Maintain running context: Each chunk should include a brief summary of preceding material (the overlap window) to maintain narrative continuity.
  3. Respect tables and figures: Never split in the middle of a table, code block, or figure caption. These should be kept as atomic units.
  4. Index creation: Build a searchable index of key terms, names, and concepts with section references for rapid lookup.
  5. Citation extraction: Pull out all references cited in each chapter to build a cumulative bibliography.

References

© wentorai, 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 skills/tools/document/large-document-reader of wentorai/research-plugins.

Open the folder on GitHubat commit bf44b3c

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in wentorai/research-plugins, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Large Document Reader next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Large Document Reader compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Large Document Reader this skillwentorai/research-plugins2981 repos~2kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k62 repos~2.3kAutomated safety check: PassApache-2.0
Hook Development for Claude Code Pluginsanthropics/claude-plugins-official37k11 repos~4.1kAutomated safety check: NotesApache-2.0
Using Superpowersfarm-fe/farm5.6k34 repos~1.4kAutomated safety check: PassMIT
Executing Plans Inlineobra/superpowers296k2 repos~5.1kAutomated safety check: PassMIT
Claude Code Agent Developmentanthropics/claude-plugins-official37k8 repos~2.8kAutomated safety check: PassApache-2.0

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 62 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • Hook Development for Claude Code Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.

    37k GitHub starsUsed in 11 repos~4.1k tokens
    Agent WorkflowsAuto-check: notes
  • Using Superpowers

    farm-fe/farm

    A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions

    5.6k GitHub starsUsed in 34 repos~1.4k tokens
    Agent WorkflowsAuto-check passed
  • Executing Plans Inline

    obra/superpowers

    Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.

    296k GitHub starsUsed in 2 repos~5.1k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Agent Development

    anthropics/claude-plugins-official

    Official

    Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.

    37k GitHub starsUsed in 8 repos~2.8k tokens
    Agent WorkflowsAuto-check passed
  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    794 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed

More from wentorai/research-plugins

All 428 skills in this repo
  • Abstract Writing Guide

    wentorai/research-plugins

    Craft structured research abstracts that maximize clarity and journal acceptance

    298 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed
  • Academic Citation Manager

    wentorai/research-plugins

    Manage academic citations across BibTeX, APA, MLA, and Chicago formats

    298 GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed
  • Academic Paper Summarizer

    wentorai/research-plugins

    Summarize academic papers with structured extraction of key elements

    298 GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed
  • Academic Study Methods

    wentorai/research-plugins

    Evidence-based study techniques for academic learning and retention

    298 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed
  • Academic Tone Guide

    wentorai/research-plugins

    Adjust writing tone and register for academic audiences and venues

    298 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Academic Translation Guide

    wentorai/research-plugins

    Academic translation, post-editing, and Chinglish correction guide

    298 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed

Categories

Questions about Large Document Reader

What does Large Document Reader do?

Split and read long documents chapter-by-chapter for structured analysis. Large Document Reader is an agent skill from wentorai/research-plugins.

When should I use Large Document Reader?

Large Document Reader fits situations like: agent Workflows work in your project.

How do I install Large Document Reader in Claude Code?

Run `npx skills add wentorai/research-plugins --skill large-document-reader -a claude-code`. Or copy the skill folder (skills/tools/document/large-document-reader in wentorai/research-plugins) into .claude/skills/large-document-reader in your project. Claude Code loads it when a task matches its description.

How do I install Large Document Reader in Codex?

Run `npx skills add wentorai/research-plugins --skill large-document-reader -a codex`. Or copy the skill folder (skills/tools/document/large-document-reader in wentorai/research-plugins) into .agents/skills/large-document-reader in your project. Codex loads it when a task matches its description.

Can I use Large Document Reader in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wentorai/research-plugins --skill large-document-reader -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/large-document-reader, .gemini/skills/large-document-reader, .github/skills/large-document-reader and .opencode/skills/large-document-reader in your project.

What does Large Document Reader need to run?

SKILL.md names no scripts, command-line tools or credentials: Large Document Reader is instructions for the agent only. Our summary lists: Python 3.

Does Large Document Reader access the network?

SKILL.md names 3 domains. As links in the text: github.com, python-docx.readthedocs.io and pymupdf.readthedocs.io. This is read from the text; nothing was executed.

Is Large Document Reader safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Large Document Reader use?

Large Document Reader is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Large Document Reader use?

About 2k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Large Document Reader?

Skills that share tags, products or a category with Large Document Reader: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 37k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Large Document Reader?

wentorai (a GitHub user) maintains it in wentorai/research-plugins, which has 298 GitHub stars. The repository holds 428 skills in this directory. The repository was last updated on June 19, 2026.

Source: wentorai/research-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.