# Edit Large Research Reports Safely

Large reports are difficult to edit without losing structure or citations. This skill guides chunked Markdown edits, backups, and citation-aware review.

## Install

```bash
npx skillstore add acskamloops/large-report-editor
```

## Metadata

- - Status: approved
- - Slug: acskamloops-large-report-editor
- - Version: 1.0.0
- - Author: ACSKamloops
- - GitHub username: ACSKamloops
- - License: MIT
- - Repository: https://github.com/ACSKamloops/shs-engine/tree/master/.codex/skills/large-report-editor
- - Ref: master
- - Supported tools: Claude, Codex, Claude Code
- - Risk level: low
- - Risk factors: filesystem
- - Quality score: 78
- - Quality tier: bronze
- - Public page: https://skillstore.pages.dev/skills/acskamloops-large-report-editor
- - Manifest: https://skillstore.pages.dev/api/skills/acskamloops-large-report-editor/manifest

## Capabilities

- Guides edits for very large Markdown research reports.
- Uses structure files to preserve report organization during changes.
- Encourages backups before major edits.
- Requires citations for newly added factual claims.
- Supports chunked, context-aware editing workflows.
- Helps compile report sections after targeted changes.

## Use Cases

- Revise Long Research Drafts: Update a large Markdown report while keeping headings, citations, and section order consistent.
- Prepare Evidence-Based Reports: Add new findings only when they include stable citations and page anchors.
- Compile Document Deliverables: Merge edited sections into a coherent report after staged review.

## Prompt Templates

### Review Report Structure

```
Review the report structure and identify sections that need editing. Do not change files yet.
```

### Edit One Section

```
Edit the named Markdown section using the provided evidence. Preserve existing citations and add page anchors for new claims.
```

### Apply Chunked Revisions

```
Revise the report in small chunks. Create a backup first, then summarize each changed section and citation impact.
```

### Compile Final Report

```
Compile the edited sections into the final report. Check structure consistency, unresolved citations, and factual claims before finishing.
```

## Limitations

- Does not verify sources unless the user provides source material.
- Does not replace legal or academic review.
- Requires access to the report files and referenced instructions.
- Cannot guarantee citation accuracy without page-level evidence.

## Best Practices

- Create a backup before major document edits.
- Edit one logical section at a time for easier review.
- Require stable citations for every new factual claim.

## Anti Patterns

- Do not add facts without source evidence.
- Do not rewrite the entire report when a targeted patch is enough.
- Do not ignore local report instructions or structure files.

## Security Audit

- - Safe to publish: true
- - Audited at: 2026-06-28T03:48:56.068\+00:00
- - Summary: The three external command findings are false positives caused by Markdown inline code around file paths on lines 7, 8, and 10. The weak cryptography finding is also a false positive because line 3 uses descriptive report-editing language, not a cryptographic algorithm. The skill does involve local file editing workflows, so it carries normal filesystem caution but no confirmed malicious behavior.

## Stats

- - Views: 209
- - Downloads: 6
- - Favorites: 0
- - Popularity score: 0