goal-griller
Turn vague ideas into verifiable Codex goals. Use when the user mentions goal mode, /goal, create_goal, autonomous work, or asks…
Research unfamiliar implementation work before coding. Use when work is ambiguous, version-sensitive, or risky and requires repo mapping, local reuse, upstream patterns, or current docs.
$ npx -y skills add hoangnb24/skills --skill xia --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/xiaContext preview
The summary Claude sees to decide when to auto-load this skill.
Research unfamiliar implementation work before coding. Use when work is ambiguous, version-sensitive, or risky and requires repo mapping, local reuse, upstream patterns, or current docs.
name: xia description: Research unfamiliar implementation work before coding. Use when work is ambiguous, version-sensitive, or risky and requires repo mapping, local reuse, upstream patterns, or current docs.
Xia is the anti-reinvention scout. Use it before unfamiliar, ambiguous, version-sensitive, or high-risk implementation work when a research brief should come before planning or code.
Do not write code or edit files until the research brief is complete, unless the user explicitly waives research or directly asks for immediate implementation.
If two viable paths differ materially in behavior, risk, or migration cost, finish the brief and ask one targeted question instead of guessing.
If unsure, use `Standard`.
1. Confirm whether research was waived. 2. Read repo contracts and map the stack from real artifacts. 3. Search locally for existing functionality and extension points. 4. Check upstream patterns only after local evidence is clear. 5. Check current official docs with version awareness. 6. Return a concise research brief using `references/research-brief-template.md`.
Load `references/xia-protocol.md` for stack-ledger guidance, local reuse targets, DeepWiki/Exa roles, recommendation rules, follow-up question criteria, and red flags.
Every non-trivial claim in the brief must be labeled:
Do not blur these categories.
Choose the lightest credible path:
1. Reuse existing local functionality. 2. Use built-in framework or library capabilities that fit the repo version. 3. Adapt an upstream pattern that fits the repo. 4. Build from scratch only when the other options are insufficient.
Explain why the chosen path beats the next-best alternative.
| File | When to Load | |---|---| | `references/xia-protocol.md` | Detailed research flow, tool roles, guardrails | | `references/research-brief-template.md` | Required brief structure |
Khuym is a focused Codex plugin containing five independent meta-skills and one tool-automation skill. It improves how an agent understands, researches, sequences, lands, and visualizes work without imposing a repository workflow.
Turn vague ideas into verifiable Codex goals. Use when the user mentions goal mode, /goal, create_goal, autonomous work, or asks…
Upgrade raw prompts into execution-ready instructions. Use when asked to improve a prompt, add context, tool, verification, or…
Build dependency-aware plans from goals, incidents, backlogs, or priorities. Use when priority conflicts with execution order and…
Organize an existing Git tree into logical commits and push them. Use when asked to commit everything, smart commit, group…
Create, inspect, edit, persist, and verify tldraw canvases through the tldraw Desktop local Canvas API without mouse-driven…