give-me-tips

# give-me-tips - explain any senpi tip, in depth ## Purpose Senpi shows the user tips: startup tips, working tips, and `Tip:` lines injected by omo components. When the user asks about any of them - "what was that Tip: line", "what does this tip mean", "how does that feature work" - this skill produces a DEEP explanation of that exact tip, in the USER'S language (match the language they asked in, always). Specific over generic, every time. "It retries on failure" is a failure of this skill. "It detects the refusal from the stopDetails on the assistant message_end event, gates on the architect category in your .omo/omo.json, and only then injects the directive" is the bar. The user asked because the tip made them curious; reward that curiosity with the real mechanism, not a summary of the tip text they already read. ## Query the live tip list FIRST Never explain from memory. Get the ground truth of what tips exist: 1. Run the tip-listing flag of the command this product is installed as: `omo --list-tips` under OmO Native (omo-ai installs; the session environment carries `OMO_NATIVE=1` and `OMO_BIN`), or `senpi --list-tips` under a plain senpi install. Never spell it `senpi` on an OmO Native machine: package managers link only the top-level `omo` bin, so `senpi` is not on PATH there. If the brand command is not on PATH either (bunx/npx launches), invoke the launcher the `OMO_BIN` variable points at: `"$OMO_BIN" --list-tips`. The command prints JSON: `[{i...