S06-超长文本读取

Reads oversized bibliographic data files in record-aligned chunks to guarantee complete coverage.

Updated May 18, 2026
One-click install
npx skills add https://github.com/heyixue511-creator/ai --skill s06-heyixue511-creator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: S06-超长文本读取
Source: https://github.com/heyixue511-creator/ai/tree/main/My-Own-Skills-main/%E6%96%87%E7%8C%AE%E8%AE%A1%E9%87%8F%E5%88%86%E6%9E%90%E6%8A%80%E8%83%BD/S06-%E8%B6%85%E9%95%BF%E6%96%87%E6%9C%AC%E8%AF%BB%E5%8F%96
Command: npx skills add https://github.com/heyixue511-creator/ai --skill s06-heyixue511-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Large bibliographic data files often exceed the AI context window, making full-file reads impossible and risking skipped records during literature cleaning. This Skill provides a chunked reading strategy that guarantees zero omissions by splitting files at safe record boundaries. ## Core Features & Use Cases - Format-Aware Chunking: Splits files by record delimiters for WoS plain text (ER lines), CSV (line numbers), RIS (blank lines), BibTeX (@ entries), CNKI custom tags, and XML elements. - Boundary Safety & Progress Tracking: Verifies each batch starts and ends on a record boundary, reports per-batch progress, and supports resuming from breakpoints after interruptions. - Use Case: When running full-corpus field statistics or semantic screening on a 5MB WoS export with 3,000 records, this Skill computes a batch plan (e.g., 50 records per batch), reads each chunk by line range, and validates that total processed records match the expected count. ## Quick Start Read the file 'wos-export.txt' in complete record-aligned batches so every record is processed without omission.

Frequently Asked Questions about S06-超长文本读取

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I read a large file that exceeds the AI context window?▼

Split the file into batches using line-number ranges sized to about 60% of the context window, then read each batch sequentially. Ensure every batch starts and ends on a complete record boundary so no record is cut in half.

How to chunk WoS, RIS, or BibTeX files without splitting records?▼

Use each format's record delimiter as the chunk boundary: ER lines for WoS plain text, blank lines for RIS, and @ entry markers for BibTeX. After each read, verify the last line closes a record and extend to the next delimiter if not.

What batch size should I use when processing large bibliographic files?▼

Batch size depends on the operation: use 60-80 records for counting and field extraction, 20-40 for semantic judgment, and 10-20 for complex reasoning like noise pattern detection. Cap total read content at 60% of the context window.

Can chunked file processing resume after an interruption?▼

Yes. Record the last completed batch number and line position, verify previously processed records were saved, then continue from the next batch without reprocessing. A final check confirms processed count equals the expected total.

When should I not use chunked reading for data files?▼

Chunked reading is unnecessary when the entire file fits within the context window, typically under 2MB or fewer than 1000 records. It is designed specifically for full-scan operations on oversized files.