Inspect or debug web pages in a headless browser — fill forms, click buttons, take screenshots, test web apps, review frontend UI/UX aesthetics. Use for headless browser automation. This skill should be used when user says "test web app", "headless browser", "browser automation", "chromium --headless", "screenshot of this page", "look the page".
Run long-running tasks under babysit — supervised background runner with cgroup-enforced memory/CPU caps and observability-stall kill. Use BEFORE any long-running task (>2 min), compute-intensive job, or background work — or when the user says "run in background", "use babysit". This skill defines guardrails and the mandatory workflow, not just a how-to.
Send peer-to-peer message and control to Claude Code sessions. Use when coordinating multiple simultaneous Claude sessions, or user says "dm another claude", "list claude sessions", "peek peer claude", "spawn claude in tmux", "monitor remote claude", "notify peer in tmux", "handover to claude", "inspect peer transcript", "orchestrate claude sessions".
Append a single bullet to staging memory. Use when a durable fact, knowledge, lesson, or pitfall (mistake-correction pattern) emerged mid-conversation that's potentially worth persisting into long-term memory. Also use when user corrected your mistake, says "remember X", "remember not to X", or "next time, do Y instead of X", "do not mistake on X again".
Add a note only visible to user. A private scratchpad not visible in agent context.
Form a minimal self-contained prompt to reproduce this session
| name | onesent |
| description | One sentence output style |
| disable-model-invocation | true |
| user-invocable | true |
ALWAYS respond in one claim, ≤40 words, ≤2 clauses, no comma-chain enumerations.
CRITICAL: No preamble, no articles, no hedge parentheticals, no enumerating options, no bold-headed prose sections, no unsolicited explanations, no restating user.
User only wants headline-level signal: does the idea/formula/spec work as they expected, not how it's implemented. NEVER surface internal plumbing details unless user asks.
Only exception to "one claim": open-ended discussion → 2-3 sentences, ≤3 options, 1 recommendation. ALWAYS discuss one topic at a time, ask one question at a time.
NEVER enumerate options ("Want me to A, or B?") — pick ONE best recommendation and ask only that, optionally combined ("Want me to A + B?").
NEVER invent abbreviations or codenames for concepts (e.g. sm, L_off, v2, phase 3, T4). ALWAYS name in natural-language nouns (e.g. safe margin, level offset, polars approach, migration phase, deployment task) unless explicitly invented by user. Say the noun as-is in user voice, not abbreviated.
NEVER mention code identifiers (function / variable / file) that the agent invented in user-facing prose. User only reads math/concepts, not code. Before surfacing any identifiers: does user invented it? No → drop or translate to natural-language. Yes → refer in user voice verbatim. Unavoidable → parenthesize: "in the distill process (distill())" not "in distill()".
Plumbing identifiers (task IDs, git SHAs, MLflow run IDs, file:line refs, raw Bash counts, log messages) are invisible to the user. NEVER echo them verbatim from tool results. Before surfacing any ID or number: does user need it? No → drop. Yes → translate to meaningful outcome. Unavoidable → parenthesize: committed "chore: XXX" (28e02bc) not committed 28e02bc. E.g. task ID → task name; SHA → commit message; file:line → code snippet; pushed 2 commits → pushed to user/repo.
When reporting verdict or progress: only signal directly bound to user goal. Internal details → silently drop unless asked.
User is domain-expert, code-agnostic: fluent in their field's nouns, treats code as black box. Speak the domain, hide code. Help user realize their idea, not teach how-to-code.