agni-kai
Zuko's Agni Kai for bakeoffs. The formal firebending duel, where competing implementations fight under the same rules and a judge…
Iroh asking Zuko what he really seeks. Restate in your own words what you think the user's goals are and what problem they are trying to solve, so a wrong reading surfaces before any work starts. Use for in-your-own-words, /in-your-own-words, "what do you think I want", "say it
$ npx -y skills add tmcfarlane/team-avatar --skill what-you-seek --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/what-you-seekContext preview
The summary Claude sees to decide when to auto-load this skill.
Iroh asking Zuko what he really seeks. Restate in your own words what you think the user's goals are and what problem they are trying to solve, so a wrong reading surfaces before any work starts. Use for in-your-own-words, /in-your-own-words, "what do you think I want", "say it
name: what-you-seek description: Iroh asking Zuko what he really seeks. Restate in your own words what you think the user's goals are and what problem they are trying to solve, so a wrong reading surfaces before any work starts. Use for in-your-own-words, /in-your-own-words, "what do you think I want", "say it back", "do you understand the goal", or before a large task when the ask is ambiguous.
Zuko spent years chasing the Avatar and called it honor. Iroh kept asking him what he really wanted until the true goal came out. Before the work starts, say back what the person is after, in your own words, so either of you can see whether it is right.
1. **Read everything they gave you.** Read the conversation, the files they named, and the code those files touch. Do not restate a request you have only skimmed. 2. **Restate the goal.** In your own words, say what they want to be true when this is done. Name the outcome, not the task. "Reviewers can approve a PR without pulling the branch" is a goal. "Add screenshots to the PR template" is a task that may serve it. 3. **Restate the problem.** Say what is wrong or missing today that makes the goal matter, and who feels it. 4. **Name what you inferred.** Mark each part that you read between the lines instead of hearing directly. Label it *inferred*. Name any constraint you assumed, such as scope, deadline, or what must not change. 5. **Stop.** Do not start the work, and do not propose a plan unless they asked for one. Let them confirm or correct.
The restated goal, the restated problem, and the inferred parts labeled as *inferred*. No plan and no preamble.
Team Avatar: a universal agent orchestrator for Claude Code, Codex, and Cursor. Nine Avatar characters, 58 engineering skills. pstack with Avatar characters on top.
Zuko's Agni Kai for bakeoffs. The formal firebending duel, where competing implementations fight under the same rules and a judge…
Aang showing a new friend around the team. Explains Team Avatar to a user, the roster and who owns what, how to invoke a skill on…
Aang's operating mode for Team Avatar, principal-level engineering where each task goes to the character who owns that…
Aang choosing which bender takes which fight. Configures which model each Team Avatar character runs on, the default reasoning…
Sokka's battle map, the decision trail he keeps so anyone can see how the campaign was won. Use for show-me-your-work,…
Appa's morning departure for picking up paused or handed-off work. The team breaks camp, reads the map they left, and flies on…