사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/lilmgenius/paperthin --skill readchk시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Check the read before acting: did you understand the instruction correctly enough to spend the work?
Goal
readchk catches misread instructions before they become coherent work against the wrong target. It verifies a claim about the requester's intent against available context: the current message, session history, project memory, files on disk, and established conventions.
This is not factchk: the question is what was meant, not whether a world claim is true.
Workflow
- Recognize the signal: a long or multi-part instruction, ambiguous scope or referents, deliberately flexible wording, or stakes high enough that a wrong guess would cost real work.
- Restate the instruction internally in different words. Do not copy the user's wording back to yourself and treat that as understanding.
- Cross-check the restatement against available context. Look for contradictions, missing antecedents, or two plausible readings that context cannot choose between.
- If context resolves the read, proceed silently. Do not ask the requester to confirm what the available context already answered.
- If a real fork survives, surface one specific clarifying question anchored to the restated understanding. Name the choice; do not ask a vague "does this look right?"
- For substantial work, log one durable "understood as: ..." line before beginning so a later reader can audit whether the work matched the confirmed read.
Rules
- Restate, don't echo. A paraphrase proves you built a model of the request; a verbatim repeat proves little.
- Silent when context resolves it. The default good outcome is invisible. Surfacing a question for a resolved or unambiguous request is a defect.
- One fork at a time. If several ambiguities exist, surface the highest-stakes one first instead of dumping a checklist.
- Never silently resolve a fork that changes the shape of the work.
- Log large commitments, not every turn. Durable read logs are for plans, multi-file changes, irreversible actions, or work a fresh reviewer may need to audit.
Verification
Before proceeding with the work: the restatement is a paraphrase, every surfaced fork is genuinely unresolved by available context, and no substantial work starts without either a silent pass or a resolved fork.



