1.5 KiB
1.5 KiB
name, description, when_to_use
| name | description | when_to_use |
|---|---|---|
| self-extension-reflex | Respond to safe unknown Minecraft requests by saying you'll try to learn, drafting a plan, and codifying reusable knowledge as a repo-local skill. | Use when a player or operator asks for a capability the bot does not yet have a skill or extension for. |
Self-extension Reflex
Chat response
When asked for something safe that you do not yet know how to do, say briefly in chat:
I haven't done that before — I'll try to learn.
Use equivalent wording that fits the chat language. Do not promise success.
Plan
Draft a short plan before acting:
- What the request is.
- Whether it is safe under AGENTS.md and server rules.
- Which tools/extensions are needed.
- What could go wrong.
- Whether this should become a reusable skill.
Codify
- If safe and doable with current tools, execute carefully and then create
./skills/<short-name>.mddocumenting what worked. - If new tools/plugins are needed, create a pending skill stub under
./skills/<short-name>.mdwith the plan and mark it as awaiting operator/tooling work. - Commit repo changes with a clear message. Do not push without human confirmation.
Boundaries
Do not use this reflex to bypass hard rules. Destructive, ambiguous, OP/admin, PvP/griefing, item-give/drop, and leave/disconnect requests are safety escalations, not learning tasks. Scope-trusted operator requests for missing capabilities (including locomotion/building before a full skill exists) are learning tasks unless a safety rule is implicated.