Claude Skills by debabsah

Use when a finished thing — a source, a result, code, or the record — is about to be trusted or consumed; the gate fires before the work leans on it. Fire FIRST - before a number is BUILT on inherited sources or PRESENTED from them - when the silent assumptions baked into procs, queries, exports, or workbooks have not been validated; the clean, small, unremarkable figure is the primary case, not the edge case. Surfaces every inherited definition/filter/grain/unit/date-basis as a numbered assu...

Use when a measured result — an experiment, a forecast, a number that must tie out — is about to drive a decision; the validity checks run before the decision does. An experiment / A-B test / causal result is about to drive a decision - ship, roll out, shift budget - including when someone just wants the win written up. COMPUTES the validity checks a consumption read eyeballs past - sample-ratio mismatch, peeking, multiple comparisons, power/MDE, Simpson's, novelty, metric-vs-proxy - via a te...

Use when a measured result — an experiment, a forecast, a number that must tie out — is about to drive a decision; the validity checks run before the decision does. A forecast / projection / time-series prediction is about to drive a plan - demand, capacity, revenue, headcount, budget - or someone wants the forecast written up or "trusted". Checks the four temporal-validity failure modes - leakage, backtest validity, interval honesty, drift - computing coverage, accuracy-vs-naive, and error t...

Use when work is leaving the desk — findings, a status, or a number that must hold up in the room. The analysis is finished and the findings need communicating to a stakeholder or decision-maker. Composes the brief from the evidence on hand and makes every claim carry its provenance and status, so open questions stay open and the verdict is carried, not smoothed into a confident story. Detects: "write up my findings", "findings brief", "communicate the results", "summarize this analysis for <...

Use when the work is hands-in-the-data right now — a number moved, an open question needs exploring, a picture of the estate needs drawing, a change needs its blast radius known. A change is about to ship — a column rename or drop, a type cast, a logic edit, a source swap — and what it breaks must be KNOWN before it lands. Walks the dependency evidence (estate map, dbt manifest, code and contracts on hand) to every impacted node — BREAKS vs SILENT-DRIFTS (the cast that quietly changes a metri...

Use when work is leaving the desk — findings, a status, or a number that must hold up in the room. A number, finding, or recommendation must hold up in a meeting - rehearse against challenge before the room does it for real: a stakeholder review, exec readout, board deck. Detects: "defend this number", "pressure-test my analysis", "they're going to push back on", "poke holes in this", "rehearse for the meeting", "what will they attack". Within this family: writing the findings up is brief-my-...

Use when the work is hands-in-the-data right now — a number moved, an open question needs exploring, a picture of the estate needs drawing, a change needs its blast radius known. An OPEN-ENDED look at data with no wrongness symptom - find what is there, and make the findings survive scrutiny later. Pre-registers the questions and the finding-bar BEFORE results are examined, logs every cut (N cuts => ~N/20 false hits expected), keeps effect sizes and bases ahead of significance talk, labels fi...

Use when the work itself is still being shaped — a new project, an incoming request, a metric, a model — before anything is built. Get oriented on an unfamiliar or inherited BI/data estate and build the living knowledge base: reads what you provide, interviews you for the rest, and surfaces what you don't know yet. Detects: "new project", "inherited", "took over", "where do I start", "don't understand this estate", "catch me up". Within this family: validating a specific request is requiremen...

Use when a finished thing — a source, a result, code, or the record — is about to be trusted or consumed; the gate fires before the work leans on it. The project's knowledge base (knowledge-base/ - the accreted record of decisions, contracts, reviews, timeline) needs auditing against its sources and itself before its conclusions get used. Flags contradictions, partial-update drift, stale statuses, expired verdicts, map-staleness, broken provenance, and unsourced numbers; it writes the exact c...

Use when the work itself is still being shaped — a new project, an incoming request, a metric, a model — before anything is built. Pin the exact meaning of a metric or KPI before it is built, reported, or argued over — every definitional fork surfaced and owner-pinned; also when two reports of "the same" number disagree. Detects: "define this metric", "what exactly is [metric]", "pin down/lock the KPI", "how should we calculate", "two reports define the same metric differently", "nail down th...

Use when the work is hands-in-the-data right now — a number moved, an open question needs exploring, a picture of the estate needs drawing, a change needs its blast radius known. The estate needs DRAWING - ER or lineage/dataflow views as a picture that can be trusted: every edge cites its evidence, an edge nothing on hand supports renders dashed [unverified], islands stay islands, and each map records what it was derived from (refresh = re-run). Scope-gated (~25 nodes per view). Detects: "ER ...

Use when the work itself is still being shaped — a new project, an incoming request, a metric, a model — before anything is built. Design or restructure the dimensional/analytical model behind reports or a mart - facts, dimensions, grain, SCD, conformance - before it is built: pins the target grain, gates on the source grain, surfaces every modelling fork for the owner. Detects: "design a data model / star schema", "how should I model this", "what's the grain of my fact table", "dimensional m...

Use when a measured result — an experiment, a forecast, a number that must tie out — is about to drive a decision; the validity checks run before the decision does. Two systems or eras claim the same number and must be PROVEN to agree — a migration cutover (legacy vs new), a month-end tie-out. Comparability gate FIRST (same definition, population, window, grain, units — or the tie-out is invalid), tolerance pinned with its owner BEFORE results, compares by STRATUM via a tested kit (matching t...

Use when the work itself is still being shaped — a new project, an incoming request, a metric, a model — before anything is built. A stakeholder handed over a solution instead of a problem — specific KPIs, a dashboard, a report, a chart, a column, "can you also track ___" — and it needs validating before anyone scopes or builds. Anchored in the XY Problem, Jobs-to-be-Done, and 5 Whys. Detects: "build me a dashboard", "add these KPIs", "report on", "can you track that", "we need a metric for",...

Use when a finished thing — a source, a result, code, or the record — is about to be trusted or consumed; the gate fires before the work leans on it. A dashboard or report — the assembled surface — needs reviewing before it ships. The failures live in the ASSEMBLY, not the SQL — non-additive totals (summed distinct counts, averaged averages), measure-filter interactions, default filters that silently exclude, stale extracts, titles and axes that claim what the data doesn't. Reviews the defini...

Use when a finished thing — a source, a result, code, or the record — is about to be trusted or consumed; the gate fires before the work leans on it. The code behind a number - a SQL query, view, or stored procedure, a dbt or semantic model, a measure, calc group, or RLS rule - needs reviewing for correctness before it ships or gets defended. Reviews the code as text against the locked definition, hunting the bugs that ship the wrong number: fan-out joins, grain and dedup, NULL and filter-con...

Use when work is leaving the desk — findings, a status, or a number that must hold up in the room. The state of the WORK itself is being reported - a status report or weekly/steering update - and the truth must survive the pull to look green: every claim carries provenance, every green names what would turn it red, slipped is slipped with the delta, risks stay open until their owner closes them, verdicts travel with their age. Detects: "status report", "weekly update for steering", "are we on...

Use when the work is hands-in-the-data right now — a number moved, an open question needs exploring, a picture of the estate needs drawing, a change needs its blast radius known. A number or result is wrong, suspicious, or moved unexpectedly in production and the why must be found before it is explained - a KPI that jumped or cratered, two reports that won't reconcile, a figure no one trusts. Drives a systematic differential across the whole failure surface - code, data, pipeline, definition,...

Use when the work itself is still being shaped — a new project, an incoming request, a metric, a model — before anything is built. A stakeholder has data and goals but NO question yet — what is worth knowing must be PROPOSED: a question-charter of candidates, each anchored to a decision or tiered curiosity, feasibility cited or UNVERIFIED, answers labeled HYPOTHESIS. Detects: "what can our data tell us", "what should we be looking at", "we don't know what we need", "what's worth analyzing her...

Unattended work — "go ahead while I'm away", "run overnight", "proceed autonomously", a mandate for hours of solo work — and the return report after. Skip for ordinary interactive turns.

A wanted artifact with latent requirements — doc, plan, spec, schema, API shape, a look — where questions get "show me options" and requirements arrive as reactions. Also when a menu can't get a pick, and on "probe rounds". Skip when requirements are statable (interview) and for a new idea (superstack-inception).

Resuming or handing off — after a crash, session limit, compaction, or model handoff; picking up a HANDOFF or state file; closing a session with work in flight; the SessionStart continuity line. Also on "resume safely" or "write the handoff". Skip for a fresh session with nothing inherited.

Use when behavior contradicts expectation — a bug, an unexplained error, a failing test, output that looks wrong, a fix that didn't hold — or when you're about to retry the same category of fix a second time, or work keeps failing or stalling. Also when the user says "debug this", "why is this happening", or "still broken". Skip when the cause is already proven.

A mid-work technical fork — "which way should we go", a design/architecture/tooling choice about to lock — or the user ruling on how the thing is built (conduct rulings are superstack-doctrine's). Also on "record this decision". Skip for statute-governed choices, forks needing building (superstack-spike), and trivially reversible picks (a log line).

Dependencies need moving — an EOL or deprecation notice, a security advisory, "upgrade to vX", "how far behind are we". Also on "upgrade dependencies". Skip for new dependencies (superstack-decide), lockfile-only patch bumps, and updating the superstack plugin itself (the plugin manager's job).

A period report for a reader outside the session — a weekly update, client status, "what did we get done this month". Skip for end-of-task reports (superstack-ship), retros when a retro tool ships, and recalling past sessions for yourself (a memory tool).

A correction or standing ruling from the user — a rebuke of a working habit, "make this a rule", "always do X", "never do Y again". Mint the statute BEFORE giving the substantive reply. Also to review or amend standing law. Skip for one-off task instructions that don't outlive the turn.

Run a campaign — a build with milestone structure spanning many sessions — from an opened plan through audited milestones to closure, surviving compaction and cold starts. Load whenever the session-start line names an ACTIVE plan (required before build actions), when opening a plan, or on "continue the plan". Skip for work a task file covers.

An artifact with a face — a UI, dashboard, chart, game, rendered document, CLI output a human reads — whenever one is built or changed, before claiming done; and before trusting any new check or harness. Also on "look at it" or "screenshot QA". Skip for pure logic changes proven by existing tests.

A new idea with no spec — a product, tool, feature, or app arriving as "I have an idea", "let's build", "create/make me X". Also on "shape this idea". Skip for bug fixes, specced tasks, changes to a running codebase (superstack-scope) — and "new skill/module/pack" ideas (superstack-smith).

A live incident — production down or degraded, users affected, data at risk, a deploy gone wrong — however phrased ("why is this broken" included); mitigation outranks diagnosis while harm is ongoing. Skip for dev-time bugs with nothing live behind them (superstack-debug).

A schema or data change with real data behind it — DDL on a live table, a backfill, retyping/renaming columns, moving data between stores. Skip for empty schemas and rebuildable dev databases; code/dependency moves (superstack-deps); a live migration harming data (superstack-incident).

Going public — a push, PR creation or merge, a package publish, a release, an infra apply; run before any of them, and when the outward gate bounces a publish command. Writes the sweep receipt the gate checks. Skip for purely local work.

Parked work — "park this", "add it to the backlog", "someday", a shaped idea inception parks, a deferral with a revisit trigger; read the queue first when starting fresh work. Also on "what's parked". Skip for work starting now.

Use before trusting or shipping an answer, design, plan, analysis, or risky code change — when you are about to commit to it. Also when the user asks for a review, a red-team, a second opinion, or to check work adversarially. For pure code diffs, prefer a dedicated code-review command when the environment has one; this runner covers every other artifact and needs nothing installed.

Use at the start of a non-trivial task, or when the goal is fuzzy, the request is solution-shaped, or you cannot yet state in one sentence what "correct" will be checked against. Skip for trivial edits.

Use when finishing a task — writing the final report or status, shipping a change, or handing off — to produce a calibrated done-claim and the docs that make the work reproducible by someone else.

A new skill or pack for a superstack-family plugin — "new skill", "add a module", "build a pack for X" — or a recurring moment applying for admission. Skip for editing an existing skill (just edit, red-first near hooks) and product ideas that aren't skills (superstack-inception).

A feasibility question, not a delivery — "can X even do Y", "is this viable", "how expensive would Z be" — where throwaway code is the cheapest probe. Skip when a read-only probe answers, when reasoning settles it (superstack-decide), and for work meant to be kept (superstack-scope).

Use when the user asks for the superstack status, overlay health, the calibration record, or what the method has been tracking in this workspace. Read-only report; changes nothing.

The human wants to understand — "walk me through this", "explain at my level", "teach me" — or a handover where the maintainer is the human. Skip for one-line answers and stranger-facing docs (a documentation task, not teaching).

An outcome claim shipping — "this should increase signups", "this saves the team time" — recorded as a dated, falsifiable prediction; settled when the SessionStart line says due. Skip for work with no outcome claim.

Use when about to claim work is complete, fixed, passing, correct, or done — before committing, opening a PR, or moving to the next task. Also when a result looks good and you're tempted to move on, or a green signal came back suspiciously clean. If the environment ships a dedicated end-to-end verify skill for exercising code changes, prefer it for driving the change; this runner owns claim calibration (the evidence ledger) and non-code artifacts.

The front door — describe what you want to build, fix, or figure out; use it when you don't know which superstack skill fits. Fires on real uncertainty: multi-step builds, debugging, claims to verify, unopened data/APIs/files, handoffs, repeated failure, before declaring done. Also on "be rigorous". Skip for trivial edits, and when "superstack" means the plugin itself (install/update/release).