Menu
Read the entirety of one or more files without skipping or chunking. Use when the user wants you to read complete files and not summarize or truncate.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when someone is about to lose access to a machine (shared server, lab box, cloud/VM instance, expiring rental) and needs to preserve all their work before it's gone. Systematically finds everything that exists ONLY on that machine — unpushed commits, stashes, untracked/uncommitted files, dirty submodules, non-git dirs, loose files, and large gitignored artifacts — and backs it up to GitHub / HuggingFace / an off-machine archive, non-destructively. Triggers on "losing access to this machine", "back up everything before I lose the server", "migrating off this box", "decommission", "my instance expires".
Use when preparing a paper's camera-ready or arXiv release — de-anonymizing an accepted submission, packaging an arXiv tarball, checking dual-submission safety against a concurrent venue (e.g. a paper accepted at a workshop that's also under review at NeurIPS/ICML), or flagging reviewer-requested post-review additions. Encodes a byte-identity discipline (the public version changes ONLY author/venue metadata, never content), a numbers-from-scripts integrity gate, and the arXiv mechanics that actually bite.
Spin up one or more fresh-context subagents to critically evaluate a proposed theory, hypothesis, interpretation, or experimental design before committing to it. Use when the user says "have an agent critique this" / "get a second opinion on" / "is this design sound" / invokes /critique, or proactively before running any experiment or committing to a non-trivial theoretical claim.
Use when launching a multi-hour neural-network training, fine-tune, or other long GPU job autonomously from Claude Code and you need to catch failures (NaN, stuck-at-chance, dead process, throughput collapse, OOM) early instead of waking up to a wasted GPU window.
Use when the user asks to check, audit, or improve a website or web project for accessibility (a11y), WCAG compliance, screen reader support, keyboard navigation, color contrast, or alt text. Triggers a plan-mode investigation against the TeachAccess design and code checklists, then implements approved fixes.
Consolidate scattered research notes, logs, experiment outputs, and submodule docs into a single living research paper. Use when the user wants to pull together multiple source documents into one structured paper.
| name | read-entire |
| description | Read the entirety of one or more files without skipping or chunking. Use when the user wants you to read complete files and not summarize or truncate. |
| user_invocable | true |
The user has explicitly asked you to read one or more files in their entirety. This is a deliberate, conscious request. Do NOT:
head, tail, or limited line rangesRead with no offset or limit parameters.offset and limit, reading sequential chunks until you reach the end. Do not stop after the first chunk.Example for a 6000-line file:
Read file_path="..." offset=0 limit=2000
Read file_path="..." offset=2000 limit=2000
Read file_path="..." offset=4000 limit=2000
.md files that fail due to embedded base64 images, use the read-large-md skill technique.If the user provides multiple file paths, read ALL of each file completely. Launch parallel Read calls when possible.
Only after you have read the complete contents of every requested file should you proceed with whatever task the user has asked you to do. Do not start working on the task with partial file contents.
Pass the file paths as arguments. Example: /read-entire path/to/file1.tex path/to/file2.md
If no file paths are given, ask the user which files to read.