메뉴
Take one quest and see it through in a single session — claim it, get onto the right branch, solve it by its kind, and close it out. Use when the user wants to work the next thing on an adventure, or when a dispatcher needs one session's work done against one record.
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/asermax/claude-plugins --skill take명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Build something already designed, together with the user, then verify it and offer to commit. Use when a design is agreed and the work is ready to write, or when another skill needs the shared build discipline.
Load first when working with any zenku skill. Carries the vocabulary, the two rules, how to find the project's vault and conventions, and the habits for writing into it.
Lay out the current shape so the user can settle a new one — which modules exist, where the seams are, how data flows, and what earlier quests already decided. Use when the user wants to design a feature or a module, work out an interface, decide where a boundary belongs, or when another skill needs a shape agreed before code.
SKILL.md 표시 중
SOC 직업 분류 기준
| name | take |
| description | Take one quest and see it through in a single session — claim it, get onto the right branch, solve it by its kind, and close it out. Use when the user wants to work the next thing on an adventure, or when a dispatcher needs one session's work done against one record. |
Load zenku:codex.
One session, one quest. This is the loop both zenku:travel and zenku:raid run, and it is the same loop whichever kind of adventure it sits under.
Its destination, its bearings, its trials, its solved index. Not every quest body: fetch a solved quest in full only when you need what it actually decided, and the index line is what tells you whether you do.
The bearings are the part to act on rather than skim. Read what they say to read before deciding anything, and take their warnings as settled instead of re-deriving them.
A raid carries the journey it came from. Its bearings say so, and that journey's solved quests are where the reasoning behind the shape lives.
A loose quest has no adventure at all. Read the quest and go on.
The one named, else the first in reach. Claim it before any work, so a concurrent session skips it. If the session ends without an answer, zenku:solve sets it back to open: a claim left behind hides the quest from every view.
Get onto the branch this work belongs on — the adventure's, creating it if this is the first quest to touch code, or one of its own on the project's pattern for a loose quest. Nothing else in the framework does this, and code written on the trunk is caught only at commit time, after it is written.
research → zenku:research · design → zenku:design · spike → zenku:spike · build → zenku:build. Anything that resolves by talking → zenku:parley.
A quest that needs a person to do something outside the repo, provision access, sign up, move data, is solved when that is done and the facts it produced are written down.
With zenku:solve. The solving skill may end by saying it is done building or done reading; that ends the work, not the session. The quest is not solved until zenku:solve has run.
Then stop. Keep the pace.