third-pass-deep-read
Skill1 starsChanged 3 months agoApache-2.0View on GitHub
Keshav's third pass — the heaviest of the three, a full sentence-by-sentence re-read including proofs/derivations, attempting a virtual re-implementation of the paper to surface implicit assumptions and concrete improvement points. Use this after second-pass-grasp, as the terminal step of the Keshav three-pass method, whenever genuine mastery of a paper (not just a summary) is needed. This is not a skippable recap — treat "nothing new to add" as suspicious, not a default outcome.
In this repository34 other files it gives its agents.
- acu-nugget-recallSkill
- argumentative-zoningSkill
- atomic-unit-matchingSkill
- atomic-unit-recall-aggregateSkill
- atomic-unit-writingSkill
- claim-label-predictionSkill
- claim-writingSkill
- domain-level-judgmentSkill
- dual-column-self-checkSkill
- engineering-config-gradingSkill
- first-pass-skimSkill
- keshav-three-passSkill
- multi-stage-cascade-extractionSkill
- paper-fetchSkill
- qalmriSkill
- qalmri-worksheetSkill
- qasper-evidence-qaSkill
- quality-appraisal-checklistSkill
- question-framingSkill
- rationale-selectionSkill
- reforms-gradingSkill
- reporting-standard-checklistSkill
- reproducibility-third-party-verificationSkill
- research-question-appraisalSkill
- rhetorical-structure-qualitySkill
- second-pass-graspSkill
- signalling-question-answeringSkill
- star-awardingSkill
- study-design-tool-gateSkill
- sum-threshold-scoringSkill
- template-slot-fillingSkill
- unit-classificationSkill
- unit-segmentationSkill
- worst-case-lookupSkill
The file
Files
Third Pass Deep Read
Keshav's third pass: sentence-by-sentence re-read with proofs/derivations included, attempting virtual re-implementation. The heaviest pass of the three — terminal step of the Keshav cascade.
Execution
Subagent — spawned via spawn-agent skill.
Why renamed from third-pass-verify (v1's name)
v1's version of this SOP (staged/wechat-article-v1/skills/third-pass-verify/) treated this as a "targeted re-check of uncertain_fields, no-op if none flagged" step — which, per the coverage audit's S2 finding, effectively deleted Keshav's real third pass (a 4-5+ hour re-implementation attempt) and replaced it with a cheap verification step serving v1's own pipeline. This v2 SOP restores the actual third pass; the rename to third-pass-deep-read marks that this is not the same behavior as the old third-pass-verify, even though both sit in the same cascade position.
Why Subagent
A genuine re-implementation attempt needs a context that can hold the full paper and reason through design alternatives without being anchored to how pass 2 already framed the contribution.
<!-- BEGIN available-tables (generated) -->Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use |
| spawn-agent | Spawn a customized CC subagent with full MCP tool access. |
<!-- END available-tables (generated) -->Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.