# Long Context

> Use bounded retrieval to analyze large documents, transcripts, code, or datasets.

- Skill: `qredence/long-context` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add qredence/long-context`
- Raw SKILL.md: https://api.skillmd.com/api/skills/qredence/long-context/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Qredence (https://skillmd.com/u/qredence)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/qredence/long-context

---


# Long-context analysis

Keep large inputs in variable space. Inputs may come from the user query, committed Session History, Skill resources, Attachments, a public URL, or Session Workspace. Explore them with bounded Python operations, send only relevant excerpts to sub-model calls, and verify every reported fact against the original variable before submitting.

## Analyze

1. Inspect variable names, types, lengths, and small previews. Do not print a whole large value. For a relevant URL, call `fetch_url` once and keep its returned `content` in a variable.
2. Locate candidate regions with deterministic searches, indexes, regular expressions, or bounded slices.
3. When the relevant regions are unknown, scan every bounded chunk for structured candidates before reducing them. Query ranking may prioritize reading order, but it must not exclude unseen evidence.
4. Call `llm_query` or `llm_query_batched` only on self-contained excerpts that include the question and their source offsets or source identifiers. Use `rlm_query` only for the rare selected subproblem that needs a fresh iterative Python investigation; it is not the normal route for extraction, counting, parsing, aggregation, or independent excerpts.
5. Reconcile candidates against definitions, scope, dates, exceptions, amendments, cross-references, and precedence rules relevant to the task.
6. Recover complete operative language from the original variable, then re-slice it to verify quotes, offsets, qualifiers, and conclusions.
7. Call `SUBMIT(...)` once with exactly the requested output fields. If the evidence is absent, ambiguous, or insufficient, state that instead of forcing the requested count. Do not `SUBMIT` an entire large `llm_query` or `llm_query_batched` blob; keep declared answers within the Turn output character budget.

Treat sub-model output as a candidate, never as source evidence. Respect the Turn's call and output budgets; reduce excerpts before making another call. Do not create chunk files, indexes, or paging state for ordinary sources; paging is a separate corrective path only if the whole-value benchmark fails.

## Exact retrieval

For an exact quote, find the text with Python, retain its source offset, and compare the final excerpt byte-for-byte or character-for-character with the original input. If the evidence is absent or ambiguous, report that instead of inventing a quote or speaker.