anchor
무료Rewrite a rule so anyone applies it the same way. Use when a stated rule or claim takes the reader's judgment to apply.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Report where a session missed moo's standard — the agent asks only while stating intent and shape, then works on its own — as issues a builder can act on. Pass a session id to report on a past session instead of this one.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
harvest captures and reports. It never drafts, builds or fixes a skill: builders do that from the report.
Run ${CLAUDE_SKILL_DIR}/scripts/read.sh <id>, where <id> is $ARGUMENTS if given, else ${CLAUDE_SESSION_ID}. It fails → show its error and stop.
Its output is the only source. A turn you cite is a numbered turn in it. It cuts long agent text; read.sh <id> <turn> prints one turn whole.
Read every file in ${CLAUDE_SKILL_DIR}/kinds/. Each names one way a session misses the standard: its sign in the marked turns, what counts, what doesn't, the evidence it needs. Walk the turns once per kind and collect each flow that meets it with the evidence it asks for. A flow without that evidence is dropped, not guessed at — but first read whole every cut turn it cites.
For each flow, one of the rows below. A skill covers the need when its description fits the turns; it says the move when a line of its SKILL.md, at the path read.sh prints, asks for what the turn skipped.
| The flow shows | Opportunity |
|---|---|
A [skill] line for a skill that covers the need and says the move | A line the agent had and lost, quoted. Rewording it is not the fix |
No [skill] line for the skill that covers the need, or another skill ran in its place | Selection: the skill, and the turn's words that should have loaded it |
A [skill] line for a skill that covers the need, silent or vague on the move | Improve that skill, named |
| No installed moo skill covers it | A new skill |
| Steps the user gave more than once | A reusable piece |
State the need — what must happen, and when — never the unit that would carry it. Check the installed list read.sh prints before calling anything new: a need an installed skill covers takes one of the first three rows. A line quoted from a plugin read.sh marks as updated after the session began may not be the text that ran: say so.
Name which of moo's four outcomes the fix serves: reduce decision regret, increase conceptual clarity, fewer but stronger artifacts, preserve the capacity to own what you produce. None → drop the flow.
Run ${CLAUDE_SKILL_DIR}/scripts/past.sh. It fails → show its error and stop: filing needs the same access.
It lists every harvest issue, open or closed, with what its comments say about reopening it. A flow whose need a listed issue already states, in any words, is a new case for that issue, never a new issue. Read the issue whole (gh issue view <N> -R saadshahd/moo.md --comments) before calling the match.
Each into its own file from mktemp: one issue per new flow, laid out as ${CLAUDE_SKILL_DIR}/issue.md; one comment per matched flow, laid out as ${CLAUDE_SKILL_DIR}/comment.md. Quote the user only from read.sh turns. Put a placeholder where a repo, file, service, person or remote would go.
Run ${CLAUDE_SKILL_DIR}/scripts/scrub.sh <id> <draft> on each draft. Exit 1 → replace each term it lists with a placeholder and run it again. Never show a draft that has not passed.
Every flow, ranked by the weight of its evidence: most turns cited and clearest sign first. For each, the draft in full and its file path; for a comment, also the issue it joins and whether it reopens it. Then ask the reporter which to file.
Only the drafts the reporter says yes to, as shown:
tail -n +2 <draft> | gh issue create -R saadshahd/moo.md --label harvest --title "$(sed -n '1s/^Title: //p' <draft>)" --body-file -. The draft's first line is its title, so the body starts after it.gh issue comment <N> -R saadshahd/moo.md --body-file <draft>, then gh issue reopen <N> -R saadshahd/moo.md when its Reopen section says the case meets the issue's condition.Show each URL. A draft changed after the yes goes back through Scrub and Show.
Never:
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Rewrite a rule so anyone applies it the same way. Use when a stated rule or claim takes the reader's judgment to apply.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Turn words with two readings into one confirmed ask. Use when the user's words admit two readings that would build different things.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan the skills an ask needs, invoke each as its condition arrives. Use when the ask has multiple aspects that different skills carry, or the user named multiple skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Bring how named experts would think about the question. Use when the user wants expert thinking on a tradeoff, choice, or stuck problem — not a verdict.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Hold an ask to the bar a top professional in its field would set — a deeper ask, never a bigger one. Use when an ask is clear but nothing yet names the sources, methods, target, or outside check the work will meet.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Build the thing the user can't specify, choices surfaced. Use when the user needs something to react to before they can choose.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.