Agent skill · writing content · code-yeongyu
give-me-tips
Explains any senpi tip in depth, including Tip: lines in the TUI. Use when the user asks about a tip, what a tipped feature does, or which tips they can see.
Why this skill is useful
Provides detailed, user-specific explanations of tips based on live data and code verification, which the AI wouldn't reliably generate on its own.
What it needs
About 8k tokens when loaded. Last updated 2026-08-07. 67,387 stars on the source repository.
What this skill does
give-me-tips - explain any senpi tip, in depth Purpose Senpi shows the user tips: startup tips and working tips, each drawn as a Tip: line by senpi itself. omo components add notices of their own beside them, such as the fallback-architect ⚡ Fallback upgrade engaged card and the ✦ Kibitzer line. 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 messageend 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 OMONATIVE=1 and OMOBIN), 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 into the user's shell, so senpi is not on their PATH (inside a session the bundled engine's .bin is on PATH, so senpi can resolve there — spell it omo anyway). If the brand command is not on PATH either (bunx/npx launches), invoke the launcher the OMOBIN variable points at: "$OMOBIN" --list-tips. The command prints JSON: [{id, text, requiresCommand?}]. Match the user's tip against this list by id or by text fragment. 2. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills code-yeongyu/give-me-tips