Explore skills

Process URLs from Obsidian inbox, scrape content, create concise summaries with topic tags, and link related entries for knowledge tracking

Use when the original plan needs to flex mid-flight in response to new information / changed inputs / discovered constraints — but flexibility WITHOUT defined scope degenerates into either rigid plan-sticking or unbounded winging-it. CRITICAL Step 0 (mirror of chengyu-close-door-catch-thief): scope MUST be defined before any deviation. If operator hasn't given a flexibility-scope tier, agent must

Use when the operator has explicitly authorised an indirect / non-causal move — when frontal attack is blocked AND chengyu-remove-firewood-from-cauldron has been exhausted, requiring attention-redirect or incentive-shift rather than technical root-fixing. Default to chengyu-remove-firewood-from-cauldron unless the operator has told the agent how to 圍魏.

Use when proven-elsewhere logic should be transplanted into your project rather than re-derived — covers both reviving abandoned-but-good code from your own history AND copying live working config (linting, CI, README templates, infra patterns) from a healthy sibling project. The "soul" is the working logic; the "body" is your project that receives it.

Use when designing a migration — graceful transition where the old interface stays as a thin stub/proxy/shim, real implementation moves underneath, consumers keep working through the transition, eventual cleanup of the shell once consumer count reaches zero. The schema of every good rename / endpoint move / library v1→v2 / database schema migration / monorepo split.

Use when debugging by narrowing the search space — isolate the failure domain so the bug reproduces in a controlled, minimal environment. CRITICAL Step 0: the agent must ASK (if unclear) or PITCH (if obvious, just needs operator confirmation) the specific "close the door" strategy BEFORE executing it; the closing has side effects (disabling services, modifying shared state, replacing real integrat

SUBAGENT-ONLY skill for generating a graduated spread of plausible-to-speculative solutions when the main agent is stuck in a local minimum. Output is one continuous artifact (NO dividers) that starts from verified fact and slides into bottom-K speculation; calling main-agent fact-checks throughout. Has TWO HARD PRECONDITIONS that must be met before any output: (1) running on a BullshitBench-passi

Use when the operator's requirement, the failing test, the stakeholder argument, or any other inputs are STILL IN FLUX and the temptation is to start implementing now "to be ready" — strategic patience while the situation clarifies, rather than burning cycles on work that may need to be redone after the dust settles

Create an agent team to analyze data engineering architectural changes from multiple perspectives (performance, architecture/design patterns, data quality). Teammates work in parallel to review changes, then synthesize findings into a design document with recommendations.

Use when resisting the urge to demonstrate cleverness — obvious-and-simple is often the right answer, and performative complexity is the failure mode. REQUIRES a target parameter at invocation specifying which dimension to apply to — implementation (over-engineered code), representation (over-fancy reply / unnecessary verbosity), or both. The agent must ASK for the target if the operator hasn't sp

Use when about to soften critical feedback into vague hedges, or when the operator suspects an agent (this one or another) is sugarcoating — missing the "Honest answer" framing, OR marked-honest-answer that smells performatively gentle. Self-applied: deliver the direct version even when uncomfortable. Cross-applied: name when another agent's reply has the sugarcoated shape.

Use when (a) operator describes a situation OR a plan step OR the agent shows an inverse pattern, and agent should NAME the right chengyu from the catalog (SELECTOR — default progressive-disclosure; covers current-situation naming, pre-flight plan tagging, and anti-pattern detection); (b) operator asks "what does that mean?" or "what's in this catalog?" (EXPLAINER — four-beat from 成語動畫廊's 熊貓博士 for