incident-workflow
openbooklet.com/s/incident-workflowopenbooklet.com/s/incident-workflow@1.0.0GET /api/v1/skills/incident-workflowUse when investigating real defects (alerts, error spikes, service degradation, near-misses caught by guardrails) AND the current repo would benefit from a forensic post-mortem. Also use to bootstrap the incidents/ structure in a new repo. Captures the diagnostic trail (commands run, hypotheses ruled out, smoking-gun evidence) that ADRs and SPECs do not. NOT for inbox material (use ingest-to-wiki) or for designing new features (use SDD / brainstorming).
When you genuinely need a browser, pick the right one. Distilled from the May 2026 audit + empirical Lightpanda + Playwright validation.
Use when the user asks to process, ingest, or close a month of family cashflow in tieubao/family-office (e.g. "process April cashflow", "close April", "ingest expenses", "do the April books", "fill in May cashflow"). Triggers on screenshots of expense summaries, bank CSVs, transfer slips, or receipts dropped in _inbox/ OR pasted inline in a session. Produces a populated `tracking/cashflow/YYYY-MM.md` with deduped transactions, per-property and per-staff attribution, an `INGEST_LOG.md` entry, and source archival per the repo privacy rule. Cashflow only; net worth and PnL are out of scope.
Compact long-form append-only documentation (handoff files, decisions ledgers, similar artifacts) without losing irreplaceable signal. Use when the user asks to "compact", "trim", "shrink", "audit signal density", "make X concise" on a doc that has grown past ~600 lines, or when a file's `purpose:` claim no longer matches reality (it claims "minimal" but takes >60s to scan). Implements a three-bucket triage (DELETE / COMPRESS / ARCHIVE) with anchor-integrity verification before merge.
Use when the user notices a multi-step manual process they have repeated across sessions and asks to formalize it as a Claude Code skill or slash command. Symptoms include "I keep doing this manually", "let's pack this as a skill", "save this workflow", "make this repeatable", "skill-ify it", "this should be a skill", "extract this into a skill", "I noticed a pattern across sessions". Drives triage and packaging; uses superpowers:writing-skills for the actual writing rigor.
Use when the user asks to reconcile, sync, or check drift between tieubao/family-office and tieubao/properties for shared property data (rent, ownership, status, addresses). Also invoke automatically before running /health-check or monthly net-worth/cashflow snapshots in family-office, to catch stale figures before they get committed. Read-only by default; mutates only on user confirmation.
Auto-indexed from dwarvesf/dotfiles
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.