andurilcode

@andurilcode source repo

69 skills
0 followers
18 hours ago last updated

▌
Dispatching Parallel Agents · andurilcode
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

0
installs
▌
Supertinker · andurilcode bundle
Run supertinker agent orchestrator workflows and monitor their execution, and the authoritative authoring reference for every supertinker plugin type. Use this skill whenever the user wants to run a multi-agent workflow, orchestrate agents, launch supertinker, check on a supertinker run, resume a paused workflow, or mentions supertinker by name. Also trigger when the user asks to search, install, manage, build, or create supertinker plugins — workflows, providers, hooks, storage adapters, commands, or custom node types.

0
installs
▌
Ctx Code · andurilcode
Make code changes using symbol-anchored edit tools. Use when you know what to change and need to patch, insert, or rename symbols.

0
installs
▌
Ctx Search · andurilcode
Understand codebases using ctx tools for token-aware navigation. Use when exploring files, researching topics, onboarding, or preparing to make changes.

0
installs
▌
Ctx Verify · andurilcode
Verify code changes by reviewing diffs and running tests. Use after making changes to check correctness.

0
installs
▌
Rules To Hook · andurilcode bundle
Author and maintain .claude/context-rules.json — the declarative config for the context-inject hook. Scans the codebase to propose an initial rule set, then guides interactive rule addition. Use with /rules-to-hook.

0
installs
▌
Edd · andurilcode
Use when iterating on agent harnesses, system prompts, context pipelines, or any context artifact that will run repeatedly. Triggers on "how do I test my harness?", "is my agent getting better or worse?", "I changed the prompt and something broke", "regression in agent behavior", "how do I know if this context change helped?", "my harness used to work", "I'm tweaking the prompt but can't tell if it's improving". Do NOT use for one-off prompts, feature code testing (that's TDD), or exploratory prototyping where "good" isn't defined yet.

0
installs
▌
Kaizen · andurilcode
Apply kaizen continuous improvement philosophy to any codebase — identifying waste, unevenness, and overburden at the code level and producing small, actionable improvement opportunities. Triggers on '/kaizen', 'kaizen this codebase', 'continuous improvement audit', 'find waste in this code', 'what small improvements can we make?', 'improve this codebase incrementally', 'code health check', 'codebase hygiene', 'tech debt sweep', or any request to find incremental improvement opportunities in code. Also trigger when the user says 'clean up', 'tidy up', 'make this codebase better', or expresses frustration about code quality without wanting a full rewrite. This is NOT a code review skill for PRs or diffs — kaizen operates on the codebase as a whole or a focus area, looking for systemic improvement opportunities. Use this skill even for small codebases — the philosophy scales down gracefully.

0
installs
▌
Automate · andurilcode bundle
Build automation scripts and pipelines that use coding-agent CLIs (Claude Code, Codex, Gemini CLI, GitHub Copilot CLI) in headless/non-interactive mode as the AI engine, or delegate work to cloud agents (`gh agent-task`) that open pull requests asynchronously. Use this skill whenever the user wants to write a shell script, CI job, cron task, batch processor, webhook handler, or any automation that shells out to `claude`, `codex`, `gemini`, `copilot`, or `gh agent-task` — single-turn prompts, multi-turn agentic loops, parallel fan-out across files/folders, structured JSON outputs consumed by downstream tools, or cloud-delegated tasks that produce PRs. Trigger on phrases like "script that uses Claude", "automate with Claude Code", "headless Claude", "batch process files with an LLM", "pipeline with codex exec", "gemini -p", "copilot --autopilot", "gh agent-task create", "GitHub Action that calls Claude", "cron job to review PRs", "agent loop in bash", "dispatch an agent task to open a PR", "fleet-wide agent-tas

0
installs
▌
Kintsugi · andurilcode
Apply kintsugi (金継ぎ) repair visibility philosophy to any codebase — finding invisible repairs and making them legible with 'gold' context. Triggers on '/kintsugi', 'kintsugi this codebase', 'repair visibility audit', 'are our fixes documented?', 'why was this changed?', 'undocumented fixes', 'invisible patches', 'git archaeology', 'missing context on past fixes', 'why does this workaround exist?', or any request to understand or document the history behind code changes. Also trigger when someone asks 'why is this code like this?', 'what incident caused this?', 'who knows why we do it this way?', or when tribal knowledge about past repairs is at risk of being lost. This skill audits the history layer of a codebase — not what the code does today, but whether past breaks and repairs are visible and legible to future developers.

0
installs
▌
Summarizer · andurilcode
Apply this skill whenever the user asks to summarize, condense, distill, or compress any content — a document, article, meeting notes, conversation, codebase, book, research paper, video transcript, or any other source material. Triggers on phrases like 'summarize this', 'give me the TL;DR', 'condense this', 'what are the key points?', 'distill this down', 'brief me on this', 'what's the gist?', 'BLUF this', 'executive summary', 'compress this for me', or any request to reduce content while preserving its essential value. Also trigger when the user pastes a long text and implicitly wants it shortened, when they share a link and ask 'what does this say?', or when they ask for meeting notes or action items from a transcript. This skill does NOT apply to 'explain X to me' (use topic-explainer) or 'write a summary section for my doc' (use technical-writing). This skill is for when source material exists and needs to be compressed.

0
installs
▌
Red Teaming · andurilcode
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.

0
installs
▌
Context Eval · andurilcode bundle
Evaluate whether a context engineering harness actually improves agent outcomes. Use when the user wants to measure, benchmark, compare, or validate any context artifact — rules, instructions, guidelines, docs, retrieval pipelines, tool setups. Triggers on "does this context help?", "benchmark my context", "evaluate my prompt", "A/B test my context", "is this worth the tokens?", "eval my context", or when someone wants empirical evidence their context engineering produces better outcomes than baseline.

0
installs
▌
Skill Router · andurilcode
Scan ALL available skills before any non-trivial request. Prevents skill blindness, tunnel vision, and wrong-skill selection. Entry point for all skill-assisted work.

0
installs
▌
Argument Craft · andurilcode
Apply argument-craft whenever the user needs to communicate a recommendation, persuade stakeholders, or structure a case for a decision. Triggers on phrases like "help me make the case for", "structure this argument", "write an executive summary", "how do I present this?", "convince the team", "frame this for leadership", "what's the narrative?", "how do I pitch this?". Use proactively when the user has completed analysis via decision-synthesis or scenario-planning but hasn't yet structured the communication.

0
installs
▌
Limit Thinking · andurilcode
Apply limit thinking when the user wants to understand what happens when a variable or condition is pushed toward its extreme — zero, infinity, 100%, or any boundary. Triggers on 'what happens if we scale this?', 'where does this break?', 'what's the ceiling?', 'what does this converge to?', or when evaluating a system by exploring its trajectory rather than its current state. Also trigger when a decision is based on a snapshot but hasn't examined what it converges to at scale. Use before any scaling decision, rollout plan, or growth strategy.

0
installs
▌
Process Design · andurilcode
Apply process-design whenever the user needs to create, improve, or streamline a workflow or operational process. Triggers on phrases like "design a workflow", "improve this process", "streamline this", "too many handoffs", "the process is too slow", "automate or not?", "how should we structure this pipeline?". Use proactively when a user describes repeated operational friction, bottlenecks, or unclear ownership in how work moves through a system.

0
installs
▌
Systems Thinking · andurilcode
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.

0
installs
▌
Test Challenger · andurilcode
Challenge AI-generated (or any) unit tests to find false positives — tests that pass against wrong behavior. Use this skill whenever the user asks to review, audit, validate, or challenge test quality, especially tests generated by AI to increase code coverage. Triggers on phrases like 'review these tests', 'are these tests actually correct?', 'challenge my tests', 'test quality audit', 'false positive tests', 'these tests were auto-generated', 'AI wrote these tests', 'coverage went up but I don't trust it', 'are these tests testing the right thing?', 'validate test correctness', or any situation where tests exist alongside source code and someone wants to know whether the tests are genuinely verifying correct behavior vs. merely mirroring implementation bugs. Also trigger when the user mentions increasing code coverage with AI, copilot-generated tests, or test generation tools — these are high-risk contexts for false positive tests.

0
installs
▌
Topic Explainer · andurilcode
Apply this skill whenever the user asks to have a topic, concept, technology, or idea explained to them. Triggers on phrases like 'explain X to me', 'what is X?', 'how does X work?', 'teach me about X', 'help me understand X', 'break down X', 'ELI5', 'explain like I'm five', 'give me an overview of X', 'I don't understand X', 'walk me through X', or any situation where the user wants to learn or understand something rather than produce an artifact. Also trigger when someone pastes a concept and asks for clarification, when they ask 'why' something works a certain way, or when they need a refresher on a topic they've encountered before. This skill does NOT apply to 'write documentation about X' (use technical-writing) or 'analyze X' (use reasoning skills). This skill is for when the human is the learner.

0
installs
▌
Causal Inference · andurilcode
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.

0
installs
▌
Fermi Estimation · andurilcode
Apply Fermi estimation whenever the user needs a quantitative answer but lacks precise data — or when a number is needed quickly to inform a decision, sanity-check a plan, or evaluate feasibility. Triggers on phrases like "how long will this take?", "how much will this cost?", "is this feasible?", "how many X are there?", "what's the order of magnitude?", "rough estimate?", "ballpark this for me", "how many tokens does this use?", "how does this scale?", or any situation requiring a quantitative judgment under uncertainty. Also trigger to sanity-check existing estimates — a Fermi calculation that disagrees with an official estimate by an order of magnitude is a signal worth investigating. Don't refuse to estimate because you lack data. Decompose and calculate.

0
installs
▌
Lateral Thinking · andurilcode
Apply lateral thinking whenever the user is stuck on a problem, has tried the obvious solutions without success, needs to generate new ideas or alternatives, or wants to break out of conventional thinking patterns. Triggers on phrases like "we're out of ideas", "nothing seems to work", "what else could we try?", "how do we innovate here?", "we keep thinking about it the same way", "what if we approached this differently?", "brainstorm alternatives", "we need a creative solution", or any situation where analytical thinking has hit a ceiling. Also trigger when a proposed solution is merely an incremental improvement on the existing approach — lateral thinking looks sideways, not just forward. Don't keep digging in the same direction when the hole isn't working.

0
installs
▌
Context Debugging · andurilcode
Use when an agent is failing, producing wrong output, ignoring instructions, hallucinating, or behaving unexpectedly — and the cause isn't an obvious code bug. Triggers on "my agent keeps failing", "the agent ignores my instructions", "it hallucinates even though I told it not to", "I fixed one thing but something else broke", "the agent used to work but now it doesn't", "why is the agent doing X instead of Y?". Do NOT use for infrastructure errors (API 500s, timeouts), code bugs in the harness (use systematic-debugging), or when the agent has never worked (use context-cartography to design first).

0
installs
▌
Cynefin Framework · andurilcode
Apply the Cynefin framework whenever the user is deciding how to approach a problem, choosing between solutions, or asking why a previous solution didn't work. Triggers on phrases like "how should we approach this?", "which solution is better?", "we tried X but it didn't work", "this is complicated", "this feels unpredictable", "we don't know what to do", "what's the right process here?", or when evaluating whether to apply best practices, run experiments, or call in experts. Also trigger when the user is applying a structured/rigid process to something that might be complex or chaotic — this is a common mismatch that Cynefin catches. Use this skill before recommending any solution approach.

0
installs
▌
Epistemic Mapping · andurilcode
Apply epistemic mapping whenever the user is starting an analysis, entering unknown territory, or needs to understand the limits of their own knowledge before acting. Triggers on phrases like "what do we know?", "what are we missing?", "what would change our minds?", "what are our assumptions?", "where are the blind spots?", "we don't know what we don't know", "what should we validate first?", "what's the riskiest assumption?", or at the start of any complex investigation, design, or decision. Also trigger before other analysis frameworks when the knowledge landscape hasn't been mapped — running diagnosis without knowing what you don't know is a common failure mode. Map your knowledge before you reason with it.

0
installs
▌
Ethical Reasoning · andurilcode
Apply ethical reasoning whenever the user faces a decision, design, or action with moral implications — especially when someone could be harmed, rights could be violated, or values are in tension. Triggers on phrases like "is this the right thing to do?", "what are the ethical implications?", "who could this harm?", "should we build this?", "is this fair?", "what are our obligations?", "value trade-off", "responsible AI". Use proactively when reviewing any high-stakes decision, product design affecting vulnerable populations, or action where the beneficiaries and those bearing costs are different groups.

0
installs
▌
Fairness Auditing · andurilcode
Apply fairness auditing whenever the user describes a system, algorithm, policy, or process that allocates outcomes across groups and wants to know whether it is equitable. Triggers on phrases like "is this fair?", "disparate impact", "bias in the system", "does this discriminate?", "algorithmic fairness", "who's disadvantaged by this?", "equitable outcomes". Use proactively when reviewing any allocation mechanism, scoring system, or automated decision pipeline that affects people differently based on group membership.

0
installs
▌
Learning Strategy · andurilcode
Apply learning-strategy whenever the user needs to close a knowledge gap, ramp up on a new domain, or build a structured plan for acquiring understanding. Triggers on phrases like "how do I learn this?", "I'm new to this domain", "ramp up on", "knowledge gap", "what should I study?", "learning plan", "how do I get up to speed?", "teach me about", "onboarding plan". Use proactively when epistemic-mapping reveals gaps that block decisions — knowing what you don't know is only useful if you then learn it efficiently.

0
installs
▌
Scenario Planning · andurilcode
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.

0
installs
▌
Technical Writing · andurilcode
Apply whenever the user needs to write, draft, review, or improve technical documents — RFCs, design docs, ADRs, runbooks, postmortems, one-pagers, announcements, Slack threads, PR descriptions. Triggers on 'write a design doc', 'draft an RFC', 'help me write this up', 'write a runbook', 'review my doc', 'make this clearer', 'write a postmortem', or when technical information must be communicated to a specific audience. Also trigger when the user pastes a draft for feedback or needs to explain technical decisions to non-technical stakeholders.

0
installs
▌
Context Compressor · andurilcode
Maximize signal-per-token in agent context windows. Use whenever context is being assembled for a task and the question is "what to include, what to cut, and how to encode it." Triggers on: "optimize context", "context window too full", "token budget", "which files in context?", "rank context by importance", "deduplicate context", "context triage", "compress this for the agent", or any curation of context under a finite token budget. Also trigger when assembling CLAUDE.md, AGENTS.md, .ctx files, system prompts, or skill files and deciding what earns its token cost. Unlike summarization (which compresses uniformly for human readers), this skill triages context by task-relative information value — scoring each fragment's entropy, redundancy, and efficiency, then cutting or compressing selectively. If tokens are scarce and context is abundant, always use this skill.

0
installs
▌
Decision Synthesis · andurilcode
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.

0
installs
▌
Evidence Synthesis · andurilcode
Apply evidence-synthesis whenever the user has multiple sources of evidence and needs to reach a conclusion — especially when sources conflict, vary in quality, or come from different methodologies. Triggers on phrases like "what does the evidence say?", "synthesize these findings", "are these studies consistent?", "literature review", "conflicting data", "what can we conclude from all this?", "meta-analysis", "weigh the evidence". Use proactively after causal-inference or learning-strategy produce findings that need integration with other evidence before a decision.

0
installs
▌
Execution Planning · andurilcode
Apply execution-planning whenever the user has made a decision and needs to turn it into action — decomposing work, sequencing tasks, estimating timelines, and assigning ownership. Triggers on phrases like "how do we execute this?", "break this into tasks", "what's the project plan?", "create a roadmap", "what are the dependencies?", "who does what by when?", "how long will this take to build?". Use proactively after decision-synthesis or architecture-evaluation produces a committed decision that requires coordinated implementation.

0
installs
▌
Financial Modeling · andurilcode
Apply financial modeling whenever the user needs quantitative rigor for a business decision — evaluating an investment, pricing a product, comparing costs and benefits, or assessing profitability. Triggers on phrases like "what's the unit economics?", "build a financial model", "is this profitable?", "what's the ROI?", "pricing strategy", "cost-benefit analysis", "what's the NPV?", "should we invest in this?". Use proactively when a decision has financial implications that the user has not quantified.

0
installs
▌
Llms Txt Generator · andurilcode
Generate llms.txt-style context documents — token-budgeted, section-per-concept Markdown optimized for LLM and RAG consumption. Use this skill whenever someone asks to generate an llms.txt, create LLM-friendly documentation, produce a context document for a library or codebase, build a RAG-ready reference, make docs 'agent-readable', create a developer quick-reference, or says anything like 'generate context for X', 'make an llms.txt for this repo', 'create a reference doc for NotebookLM', 'turn these docs into something an LLM can use', 'context document', 'developer cheatsheet from docs'. Also trigger when someone provides a GitHub repo URL and asks for documentation synthesis, or when working inside a codebase and asked to produce a self-contained reference of how it works. This is the context engineer's doc generation tool — it turns sprawling documentation into precise, structured, token-efficient context.

0
installs
▌
Presentation Craft · andurilcode
Apply this skill whenever the user needs to create, plan, structure, or improve a presentation, talk, pitch, keynote, or slide deck. Triggers on phrases like 'make a presentation about', 'I have a talk on', 'help me structure my deck', 'create slides for', 'pitch deck for', 'I'm presenting at', 'conference talk', 'prepare a keynote', 'workshop slides', or any request that involves communicating ideas to an audience via slides and spoken delivery. Also trigger when the user has existing slides and wants to improve the narrative flow, when they need speaker notes, or when they want to rehearse timing. This skill does NOT produce .pptx files directly (use the pptx skill for file creation). This skill produces the presentation SCRIPT — the narrative blueprint that determines what each slide says, shows, and how long the presenter spends on it.

0
installs
▌
Analogical Thinking · andurilcode
Apply analogical thinking whenever the user is designing a system, architecture, or process and would benefit from structural patterns that already exist in other domains — or when a problem feels novel but may have been solved elsewhere under a different name. Triggers on phrases like "how should we structure this?", "has anyone solved this before?", "we're designing from scratch", "what's a good model for this?", "I keep feeling like this resembles something", "what patterns apply here?", or when facing architecture, organizational, or process design decisions. Also trigger when a problem has been analyzed thoroughly but no good solution has emerged — the answer may exist in an adjacent domain. Don't reinvent what's been solved. Recognize the shape of the problem first.

0
installs
▌
Context Cartography · andurilcode
Use when designing what goes into an agent's context window — system prompts, tool definitions, retrieval results, or any context artifact assembled before the agent runs. Triggers on "what should I put in the system prompt?", "how do I structure my context?", "the agent loses track of...", "my context window is full", "how do I decide what to include?", "designing a new harness", "the agent ignores my instructions". Do NOT use for one-off prompts, runtime conversation management, or when the problem is model capability rather than context design.

0
installs
▌
Experimental Design · andurilcode
Apply experimental-design whenever the user needs to test a hypothesis, validate an assumption, or determine whether something actually works. Triggers on phrases like "how do we test this?", "design an experiment", "what would prove this?", "set up an A/B test", "how do we validate this hypothesis?", "what's the right control?", "is this result significant?", "what sample size do we need?". Use proactively when decisions rest on untested assumptions — designing the test before collecting data prevents post-hoc rationalization.

0
installs
▌
Facilitation Design · andurilcode
Apply facilitation-design whenever the user needs to plan a meeting, workshop, retrospective, or any group session aimed at a specific outcome. Triggers on phrases like "design a workshop", "how do I run this meeting?", "facilitate a retrospective", "structure a brainstorm", "we need alignment", "how do I get the group to decide?", "plan an offsite session". Use proactively when a user describes a group decision-making challenge, alignment gap, or collaborative work session that lacks structure.

0
installs
▌
Inversion Premortem · andurilcode
Apply inversion and pre-mortem thinking whenever the user asks to evaluate a plan, strategy, architecture, feature, or decision before execution — or when they want to stress-test something that already exists. Triggers on phrases like "is this a good idea?", "what could go wrong?", "review this plan", "should we do this?", "are we missing anything?", "stress-test this", "what are the risks?", or any request to validate a decision or design. Use this skill proactively — if the user is about to commit to something, this skill should be consulted even if they don't ask for it explicitly.

0
installs
▌
Knowledge Architect · andurilcode
Apply whenever knowledge is at risk of being lost, needs to be captured, or a team needs to design how knowledge flows and persists. Triggers on 'document this decision', 'we should write this down', 'someone is leaving the team', 'why did we do it this way?', 'we keep re-debating this', 'set up our knowledge system', 'our docs are a mess', 'onboarding is painful', or any situation where implicit knowledge needs to become explicit and discoverable. Also trigger after incidents, migrations, vendor choices, or finished spikes — high-value capture moments.

0
installs
▌
Context Gap Analyzer · andurilcode
Identify implicit context missing from a codebase that would most improve agent performance. Use whenever someone asks to audit, assess, or improve context for a codebase; asks 'what context is my codebase missing?', 'why do agents keep making mistakes here?', 'what should I put in my CLAUDE.md?', 'audit my codebase context', 'context gaps', or any variation. Also trigger when setting up agent context infrastructure for the first time, or when agent-generated code keeps violating implicit conventions.

0
installs
▌
Five Whys Root Cause · andurilcode
Apply 5 Whys and root cause analysis whenever a problem keeps recurring, a fix didn't hold, or the user is trying to understand why something went wrong. Triggers on phrases like "this keeps happening", "we fixed it but it came back", "why did this fail?", "what caused X?", "we keep having this issue", "post-mortem", "incident review", "the same bug appeared again", "why isn't this working?", or any situation where symptoms have been identified but root causes haven't. Also trigger when a proposed solution feels like a workaround rather than a fix — this skill helps validate whether the real cause has been found. Don't let the agent stop at symptoms.

0
installs
▌
Negotiation Strategy · andurilcode
Apply negotiation strategy whenever the user needs to prepare for, navigate, or debrief a negotiation — whether formal (contracts, salary, deals) or informal (resource allocation, scope disputes, partnership terms). Triggers on phrases like "how do I negotiate this?", "what's my BATNA?", "how do we reach agreement?", "they won't budge on", "what leverage do I have?", "finding common ground", "deal structure", "how do I handle this negotiation?". Use proactively when a user describes a situation with competing interests and an outcome that requires agreement between parties.

0
installs
▌
Code Review Amplifier · andurilcode
Apply this skill whenever the user asks to review code, a PR, a diff, or a merge request — or when they paste code and ask for feedback on it. Also trigger when someone asks to 'prepare a review', 'check this PR', 'review my changes', 'what do you think of this code', 'is this PR ready to merge', 'help me review', or any situation where code quality assessment is involved. This skill does NOT try to replace the human reviewer. It amplifies human reviewers by assembling context, pre-scanning surface issues, generating design coherence questions, and routing knowledge-transfer opportunities. Use this skill even for small snippets — the 7-dimension framework scales down gracefully. If the user says 'code review' in any form, trigger this skill.

0
installs
▌
Debugging Methodology · andurilcode
Apply debugging methodology whenever the user faces a software failure they cannot explain — a broken test, unexpected behavior, a regression, or an intermittent bug. Triggers on phrases like "why is this broken?", "how do I debug this?", "the test fails but I don't know why", "intermittent failure", "works on my machine", "this used to work", "regression". Use proactively when the user describes a symptom and jumps straight to a fix without isolating the root cause.

0
installs
▌
Decision Intelligence · andurilcode
Apply when ALL THREE conditions hold: (1) a single decision or belief is evaluated — not comparing multiple options; (2) probability and outcome magnitude are estimable; (3) human bias likely distorts reasoning — sunk costs, survivorship bias, intuition vs. math, or real money/time at stake. Triggers on 'should I do this?', 'is this worth it?', 'I've already put so much into this', or single-path decisions involving financial bets, career moves, or long-term commitments. NOT for comparing options (decision-synthesis), probability estimation (probabilistic-thinking), or estimation (fermi-estimation). Mandatory-process: applies all 6 models without exception.

0
installs
▌
Second Order Thinking · andurilcode
Apply second-order thinking whenever the user is making a decision, proposing a change, or evaluating an action — especially one that seems obviously good or obviously safe. Triggers on phrases like "let's just do X", "the obvious answer is", "we should change Y", "what happens if we do Z?", "should we implement this?", "will this work?", or any time a user proposes an intervention in a system involving people, incentives, markets, or complex processes. Also trigger when first-order analysis has already been done and the user needs to go deeper. Second-order thinking should be applied before any significant decision is made — don't wait to be asked.

0
installs
▌
Theory Of Constraints · andurilcode
Apply Theory of Constraints (TOC) whenever the user asks why a system, team, pipeline, or process isn't going faster, isn't scaling, keeps hitting the same ceiling, or feels like effort isn't translating into results. Triggers on phrases like "we're stuck", "why is this slow?", "we keep hitting a wall", "throughput is low", "we work hard but don't ship fast", "what's the bottleneck?", "how do we scale this?", or any situation where effort and output feel misaligned. Also trigger when evaluating workflows, delivery pipelines, agent pipelines, or organizational processes — always check for the constraint first before recommending optimizations.

0
installs
▌
Bisociative Creativity · andurilcode
Apply bisociative creativity whenever the user wants to generate genuinely novel ideas, concepts, names, narratives, metaphors, or creative directions. Triggers on phrases like "give me ideas for", "brainstorm", "I need something creative", "help me come up with", "what's a fresh angle on", "I want something original", "make this more interesting", "surprise me", "help me ideate", or any request where the deliverable is creative output rather than analytical output. Also trigger when ideas feel generic or like AI slop. This is the go-to skill for creative generation across any domain — naming, writing, product concepts, marketing, talk themes, visual concepts, anything. Distinct from lateral-thinking (escaping stuck patterns) and analogical-thinking (transferring structural solutions) — this skill generates novel ideas by colliding unrelated frames of reference.

0
installs
▌
Narrative Construction · andurilcode
Apply narrative-construction whenever the user needs to turn analysis, data, or ideas into a compelling story. Triggers on phrases like "tell the story of", "create a narrative", "make this compelling", "what's the story arc?", "thought leadership piece", "how do I frame this as a story?", "content strategy", "write a blog post about". Use proactively when the user has strong analytical output that needs to reach a non-expert audience.

0
installs
▌
Probabilistic Thinking · andurilcode
Apply probabilistic and Bayesian thinking whenever the user needs to reason under uncertainty, compare risks, prioritize between options, update beliefs based on new evidence, or make decisions without complete information. Triggers on phrases like "what are the odds?", "how likely is this?", "should I be worried about X?", "which risk is bigger?", "does this data change anything?", "is this a signal or noise?", "what's the probability?", "how confident are we?", or any situation where decisions are being made based on incomplete or ambiguous evidence. Also trigger when someone is treating uncertain outcomes as certainties, or when probability language is being used loosely ("probably", "unlikely", "very likely") without quantification. Don't leave uncertainty unexamined.

0
installs
▌
Reasoning Orchestrator · andurilcode
Apply this skill first whenever the user presents a problem, question, or situation that requires structured thinking — before reaching for any specific reasoning framework. Triggers on any substantive request to evaluate, analyze, diagnose, decide, design, improve, understand, or learn from something. This is the entry point for the reasoning skill collection. If you are unsure which reasoning skill to use, always start here.

0
installs
▌
Rule Quality Evaluator · andurilcode
Evaluate the quality of existing agent instruction rule sets — CLAUDE.md, AGENTS.md, .cursorrules, copilot-instructions.md, or any coding-agent context file. Use this skill whenever someone asks to audit, score, or improve their agent rules; wants to know if their instructions are effective; or describes rules that aren't changing agent behavior. Trigger on phrases like 'are my rules good?', 'why is the agent ignoring my instructions?', 'score my CLAUDE.md', 'audit my agent rules', 'are these instructions effective?', 'review my copilot-instructions.md', 'my rules aren't working', 'evaluate my context file', or any situation where a human has an existing instruction file and wants to know whether it will actually improve agent behavior. Also trigger when someone has just run agent-instruction-forge and wants to verify the output before committing.

0
installs
▌
Agent Instruction Forge · andurilcode bundle
Guide humans through creating effective instruction rules for coding agents (Copilot, Claude Code, Cursor, Windsurf, Aider, AGENTS.md, CLAUDE.md, .cursorrules, copilot-instructions.md). Trigger when someone asks to create, improve, or write agent instructions, copilot rules, AI coding guidelines, context files, or anything shaping agent behavior. Also trigger on 'agent keeps making mistakes', 'make Copilot follow our conventions', 'write rules for repo', 'set up agent context'. Runs an interactive extraction process — reads codebase first, then guides the human through targeted questions to surface implicit knowledge (past failures, non-obvious conventions, architectural decisions) that code alone can't tell an agent. For analyzing gaps in existing context, use context-gap-analyzer. This skill *creates* the rules.

0
installs
▌
Architecture Evaluation · andurilcode
Apply architecture evaluation whenever the user faces a system design decision — choosing between architectures, evaluating trade-offs, or documenting a technical direction. Triggers on phrases like "evaluate this architecture", "should we use microservices?", "what are the trade-offs?", "is this design scalable?", "architecture decision", "ADR", "system design review", "which database should we use?". Use proactively when the user is about to commit to a technical direction without explicit trade-off analysis.

0
installs
▌
Deep Document Processor · andurilcode
Apply disciplined multi-pass reading to extract token-efficient, decision-relevant context from large documents, codebases, or research papers. Use this skill whenever an agent needs to process a document longer than ~2000 tokens and produce a compressed context representation — not a summary for humans, but a context artifact optimized for downstream agent reasoning. Triggers on: "read this and extract what matters", "process this document for context", "what's relevant in this for our task?", "distill this", "context-extract", or any situation where a large input must be compressed into a smaller, high-signal context window. Also trigger when an agent is about to dump an entire document into context — this skill replaces naive full-inclusion with structured extraction. Do NOT use for simple summarization requests aimed at human readers — this skill optimizes for agent consumption.

0
installs
▌
Difficult Conversations · andurilcode
Apply difficult-conversations whenever the user needs to prepare for a conversation involving conflict, power dynamics, emotional stakes, or relationship risk. Triggers on phrases like "how do I bring this up?", "I need to give difficult feedback", "there's a conflict on the team", "how do I have this conversation?", "someone is underperforming", "I disagree with my manager", "how do I say no?", "this is going to be awkward". Use proactively when negotiation-strategy identifies emotional or identity stakes that pure interest-based negotiation cannot handle.

0
installs
▌
Game Theoretic Analysis · andurilcode
Apply game-theoretic analysis whenever multiple agents, actors, teams, or systems interact strategically — where each party's best move depends on what the others do. Triggers on "what's their incentive?", "why would they cooperate?", "how do we align incentives?", "coordination problem", "trust problem", or any situation involving negotiation, competition, cooperation under self-interest, or multi-agent interaction. Also trigger when designing multi-agent AI systems, agent negotiation protocols, or when a design fails because agents optimize for own payoffs rather than the system goal.

0
installs
▌
Business Logic Extractor · andurilcode
Extract and document business logic, domain models, and product rules from a codebase into a structured llms.txt-style reference. Use this skill whenever someone asks to 'document the business logic', 'extract domain rules', 'what are the business rules in this codebase', 'map the domain model', 'document product behavior', 'what does this system actually do', 'reverse-engineer the business rules', 'create a domain reference', 'what are the invariants', 'how does pricing work in this codebase', 'what validations exist', 'document entity relationships', or any request to make implicit product knowledge explicit from code. Also trigger when an agent or developer is onboarding to a codebase and needs to understand what the system does (not how it's built). This is the context engineer's domain knowledge extraction tool — it turns code into a product behavior reference.

0
installs
▌
Cognitive Bias Detection · andurilcode
Apply cognitive bias detection whenever the user (or Claude itself) is making an evaluation, recommendation, or decision that could be silently distorted by systematic thinking errors. Triggers on phrases like "I'm pretty sure", "obviously", "everyone agrees", "we already invested so much", "this has always worked", "just one more try", "I knew it", "the data confirms what we thought", "we can't go back now", or when analysis feels suspiciously aligned with what someone wanted to hear. Also trigger proactively when evaluating high-stakes decisions, plans with significant sunk costs, or conclusions that conveniently support the evaluator's existing position. The goal is not to paralyze — it's to flag where reasoning may be compromised so it can be corrected.

0
installs
▌
First Principles Thinking · andurilcode
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.

0
installs
▌
Professional Orchestrator · andurilcode
Entry point for professional skills — architecture, communication, process design, ethics, and leadership. Routes to the right skill based on what the user needs. Use this when the user's goal involves a professional discipline but they haven't named a specific skill.

0
installs
▌
Stakeholder Power Mapping · andurilcode
Apply stakeholder and power mapping whenever the user is navigating organizational decisions, driving change, launching a product, building alignment, or trying to understand why something keeps getting blocked. Triggers on phrases like "why won't people adopt this?", "who do I need to convince?", "this keeps getting blocked", "how do I get buy-in?", "who are the key players?", "there's political resistance", "how do I manage stakeholders?", "who has influence here?", "someone is sabotaging this", or any situation where human actors, organizational dynamics, or change management are involved. Also trigger when a technically sound plan is failing for non-technical reasons — the real constraint is often human, not systemic. Never skip this skill when organizational change or adoption is involved.

0
installs
▌
Retrospective Counterfactual · andurilcode
Apply retrospective and counterfactual reasoning whenever something has already happened and the user needs to understand why — or learn from it to improve future decisions. Triggers on phrases like "what went wrong?", "why did this fail?", "post-mortem", "incident review", "we just shipped and it didn't go well", "let's debrief", "what would we have done differently?", "should we have seen this coming?", "what did we miss?", "what would have happened if we'd done X instead?", or any after-the-fact analysis of a completed event. Also trigger to prevent survivorship bias in success analyses — "what made this succeed?" deserves as much causal scrutiny as failure. Look backwards with as much rigor as you look forward.

0
installs
▌
Context Engineering Orchestrator · andurilcode
Entry point for context engineering work. Routes to the right skill based on what the user needs — creating instructions, debugging agent failures, building documentation, or measuring outcomes. Use this when the user's goal involves agent context but they haven't named a specific skill.

0
installs

69 published skills