사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/saadshahd/moo.md --skill freeze시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Observe
Build the snapshot, invoking each named skill with the Skill tool where its condition holds:
- Which outside facts this work touches reads two ways, and the two would build different snapshots → use clarify skill. Scope to the slice the work touches, not a general map.
- Name the facts the work depends on. Naming which facts matter is the only place reasoning fills in; each fact's value comes from reading it.
- Read each named fact live, read-only — look, don't touch: no write, no state-changing call, no toggle. A fact unreachable, or one that reading would change → an open gap, with instructions for the human to retrieve it by hand.
- Use draft skill on the snapshot: the observed facts and the open gaps, kept apart — each observed fact carrying what it says, where it lives, and when it was read; anything concluded over the facts marked as a conclusion and kept out of the observed set.
- The snapshot → use judge skill, on the claim: every named fact is observed or an explicit open gap, and no value was invented. An invented value demotes to a gap or gets re-observed.
A hand-retrieved fact, a re-observation, or an amendment re-enters the snapshot, and the snapshot gets judged again. A fact's value is observed or it is a gap; there is no third kind.
The snapshot
One snapshot, in conversation, stateless: re-run the whole freezing to refresh it. Hand it back as two lists of short bullets — each observed fact on one line with where it lives and when it was read, each gap on one line named as a gap.
It stands when judge's verdict stands and the user locks it, or when the user stops with gaps standing. A snapshot with named open gaps is a valid lock; the gaps are what is open.
Every needed fact lives in the repo → read them where the work runs; no snapshot. The outside system is to be changed, not read → that is the work itself, not its grounding; proceed with the work.