Jebi
JEBI AGENT: clean handoff Skill for successor Codex chats
npx -y skills add kyutomatte/jebi_agent --skill jebiAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 24 days oldThe repository was created 24 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Alias trigger for JEBI AGENT. Use immediately when the user invokes $jebi, says 제비로 옮겨주세요, 제비로 옮겨줘, 제비로 이동해주세요, 제비로 이사갈게요, 제비로 이사 가자, 제비한테 넘겨줘, 제비에게 넘겨주세요, 제비로 인수인계해줘, 제비 불러줘, 제비 출발, 제비 보내줘, 새 채팅으로 제비 보내줘, 새 채팅에 제비로 옮겨줘, 다음 채팅으로 제비가 옮겨줘, 제비로 새 채팅 만들어줘, 제비로 이어가자, or JEBI로 새 채팅 만들어줘. This means create a concise handoff and start a clean new Codex thread. Do not use for animal swallow questions, photos, filenames/code named jebi, explaining the agent, trigger editing, or when the user says not to move yet.
SKILL.md
1.5 KB, 193 tokens by cl100k_base, as published. Nobody here has run it
JEBI Alias
This is the short-name alias for jebi-agent. When this skill triggers, use the sibling Skill directory ../jebi-agent as the implementation source.
Required Behavior
- Read
../jebi-agent/SKILL.md. - Follow its output style, safety rules, and default flow exactly.
- Use
../jebi-agent/scripts/create_handoff.pyand../jebi-agent/scripts/create_successor_thread.py. - Use Codex App Server
thread/start; never usethread/fork. - Do not copy the current chat history into the successor thread.
If the user only mentioned 제비 or JEBI and handoff intent is unclear, ask:
JEBI AGENT로 현재 작업을 새 채팅에 인수인계할까요?
What ships with it: 2 files
433 B alongside SKILL.md
agents/
- openai.yaml218 B
- README.md215 B