give-me-tips - Deep Explanations of senpi Tips

What it does

senpi shows short Tip: lines at startup and while you work. This skill turns any of those one-liners into a real, verified explanation of the mechanism behind it.

• Runs senpi --list-tips first to get the ground-truth catalog (falls back to reading the tips catalog sources if the flag is missing).
• Checks the tips toggle in settings.json, tipsHistory cooldown rotation, and requiresCommand gating so it tells you which tips you personally can encounter, not the whole superset.
• Never invents behavior: it reads the actual implementation in the senpi and oh-my-openagent repos and cites concrete file paths. If the code contradicts the tip text, the code wins.
• For the Fable-5-refusal tip it walks the full fallback-architect pipeline: refusal detection, architect-category gate, hidden directive, and the visible tip renderer.
• Answers in whatever language you asked in, with a deliberately "engine room tour" tone: named events, gates, and exact order of operations.

Who it's for

• Active senpi / oh-my-openagent (omo) users curious about the tips they keep seeing
• Developers who want event-level and state-machine-level detail, not a paraphrase of the tip
• Anyone debugging why a given tip does or doesn't appear in their own setup

Examples

1. "What did that Tip: line mean?" → matches the tip against the live list, opens the relevant feature files, and explains the mechanism step by step.
2. "What's the tip that shows up after Fable 5 refuses?" → covers refusal detection semantics, the hidden 5-step architect playbook, and the self-cancelling nudge, with file paths.
3. "Which tips can I actually see?" → reports the tips reachable under your settings and tip history, and why the others are gated out.

Install the skill I found on Claude Skill Mart.
Copy the packages/omo-senpi/skills/give-me-tips folder from the GitHub repo code-yeongyu/oh-my-openagent into my ~/.claude/skills/give-me-tips/.
When it's done, tell me in one line what this skill can do.