context-gap-analyzer
No SKILL.md available for this skill.
View on GitHubMore from andurilcode/skills
causal-inference
Apply causal inference whenever the user is interpreting metrics, debugging system behavior, reading A/B test results, or trying to understand whether an observed change was caused by an action or by something else. Triggers on phrases like "X caused Y", "since we deployed this, metrics changed", "the A/B test showed a lift", "why did this metric move?", "is this correlation or causation?", "we changed X and Y improved", "how do we know this worked?", "the data shows…", or any situation where conclusions are being drawn from observational data. Also trigger before any decision based on metric interpretation — confusing correlation with causation leads to interventions that don't work and misattribution of credit. Never assume causation without applying this skill.
30first-principles-thinking
Apply first principles thinking whenever the user is questioning whether a design, strategy, or solution is fundamentally right — not just well-executed. Triggers on phrases like "are we solving the right problem?", "why do we do it this way?", "is this the best approach?", "everyone does X but should we?", "we've always done it this way", "challenge our assumptions", "start from scratch", "is there a better way?", or when the user seems to be iterating on a flawed premise rather than questioning the premise itself. Also trigger when a proposed solution feels like an incremental improvement on something that may be fundamentally broken. Don't optimize a flawed foundation — question it first.
21scenario-planning
Apply scenario planning whenever the user is making long-term decisions, building roadmaps, evaluating strategies, or operating in an environment with significant uncertainty about how the future will unfold. Triggers on phrases like "what should our roadmap look like?", "how do we plan for the future?", "what if things change?", "we're not sure which direction the market will go", "how do we make this strategy resilient?", "what's our plan B?", "what are the different futures we could face?", or when a plan assumes a single future state. Also trigger when someone is over-committed to one expected outcome and hasn't stress-tested the strategy against alternative futures. Don't plan for one future — plan for multiple.
21red-teaming
Apply red teaming whenever the user wants to stress-test a system, plan, architecture, security model, or decision against adversarial conditions — or when they want to find the weakest points before someone else does. Triggers on phrases like "where are the weak points?", "how would someone break this?", "is this secure?", "find the holes in this plan", "play devil's advocate", "what are we not seeing?", "challenge this", "attack this design", "where could this be exploited?", or when the user is about to launch or commit to something significant. Also trigger for any system where trust, security, incentives, or adversarial actors are relevant — don't wait for the user to ask for a red team explicitly.
20decision-synthesis
Apply decision synthesis whenever the user has completed analysis — run multiple frameworks, mapped the problem, identified options — and now needs to actually choose. Triggers on phrases like "so what should we do?", "how do we decide between these?", "we have too many options", "everything seems equally valid", "how do we weigh these trade-offs?", "we can't agree on which direction", "given all this, what's the call?", or when a rich diagnostic phase has produced competing insights without a clear winner. Also trigger when a decision involves multiple stakeholders with different priorities, multiple criteria that pull in different directions, or significant irreversibility. This skill bridges analysis to action — don't leave a decision unmade because the map is rich.
20systems-thinking
Apply systems thinking frameworks whenever the user asks to evaluate, assess, audit, review, or analyze anything — a product, process, architecture, feature, team structure, business model, workflow, or strategy. Triggers on words like "evaluate", "assess", "analyze", "review", "is this working?", "what's wrong with", "how can we improve", "should we change", or any request to understand why something isn't performing as expected. Use this skill even when the user doesn't explicitly say "systems thinking" — if they're asking Claude to understand how something works and where it might fail, this skill should be consulted. Don't wait to be asked twice.
19