By jackwillis
Frameworks for modeling systems before intervening: epistemic discipline (Hacking), regulatory analysis (Ashby), causal identification (Pearl), and frame-assumption auditing (Fodor/Dennett).
Use when evaluating whether evidence supports a causal claim or designing a study to test one. Triggers on "does X cause Y", "should we change X to improve Y", "we noticed X and Y move together", "the data shows...", "our A/B test found...", auditing causal reasoning in a document or analysis, drawing conclusions from observational data, confounders, selection bias.
Use when reasoning or acting on assumptions that may no longer hold — especially after time has passed, the user has acted between turns, prior actions had untraced side effects, or when accepting a problem framing without questioning it. Triggers on stale state, unexamined non-effects, inherited problem framing, confidence without re-verification, and any gap between when information was gathered and when it's being used.
Use when something is broken or behaving unexpectedly and you need to understand why before fixing it. Triggers on "why is this happening", "help me debug", "it's not working", unexplained gaps between expected and observed behavior, a fix that didn't work, multiple simultaneous changes with unclear results.
Use when designing, evaluating, or diagnosing control and regulation systems — especially when asking "why can't we control this?", "why does this regulator fail?", "is our defense sufficient?", or when facing a system too large to regulate by brute force. Triggers on regulation failure, alert fatigue, oscillating controllers, defense ceilings, scaling limits, "we keep adding rules/alerts but it's not working", whack-a-mole against adaptive adversaries, reactive controls hitting a ceiling.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Claude Code plugins that make the agent stop and think before changing your code.
Experimental. These plugins work but are under active development. Expect rough edges.
AI coding agents are biased toward action. They'll try a fix before understanding why something broke, add more rules when the problem is that rules can't keep up, or assume one thing causes another just because they happen together. These are the same mistakes humans make, just faster.
The systems-analysis plugin adds four skills that come back to one question: do you understand the system you're about to change? Skills activate automatically when Claude detects a matching situation, and can also be called directly with slash commands. A second plugin, text-utils, adds utilities for working with web content and PDFs.
You tell Claude a test passes locally but fails 30% of the time in CI. Without this plugin, it guesses "race condition" and starts adding sleep calls and retries.
With the plugin installed, Claude states two competing models — missing ORDER BY (CI uses a parallel test runner) vs. actual race condition — and picks the cheapest test that distinguishes them: check CI config for a parallel runner. Confirms it's parallel. Adds ORDER BY. Runs 50 iterations. All green.
The difference: instead of guessing and retrying, Claude writes down what it thinks is happening, names what would prove it wrong, and tests that first.
| Skill | Command | What it does | Auto-triggers on |
|---|---|---|---|
| Debug with a model | /representing-and-intervening | Write down your model before debugging | "why is this happening", unexplained behavior |
| Check your controls | /requisite-variety | Check if your defenses can keep up with what they're defending against | regulation failure, alert fatigue |
| Verify causal claims | /causal-analysis | Verify the data supports a cause-and-effect claim | "does X cause Y", observational data |
| Surface stale assumptions | /frame-problem | Name assumptions that may no longer hold | stale state, inherited framing |
| Fetch markdown | /fetch-markdown | Get clean markdown from a URL | fetching web content |
| Markdown to PDF | /markdown-to-pdf | Render markdown to styled PDF | "make a PDF", "export as PDF" |
| PDF to text | /pdf-to-text | Extract text from PDFs (digital or scanned) | "read this PDF", scanned documents |
| Riff | /riff | Generate name/phrase variations via diverge/converge rounds | Invoke explicitly |
Add the marketplace, then install either plugin:
/plugin marketplace add https://github.com/jackwillis/claude-plugins.git
Restart Claude Code after installing plugins to load new skills.
/plugin install systems-analysis@jackwillis
/representing-and-intervening — Hacking (1983), Schon (1983), Argyris & Schon (1978)
Stop debugging by trial and error. This skill makes Claude write down what it thinks is happening and what it expects to see before touching anything — so when a test surprises you, you know whether the mental model is wrong or just needs tuning.
/requisite-variety — Ashby (1956), Conant & Ashby (1970)
Stop adding more rules when rules can't keep up. This skill checks whether your controls can actually handle the range of problems they'll face, whether they model how the system actually works, and whether there's structure in the problem you can exploit instead of brute-forcing it.
/causal-analysis — Pearl & Mackenzie (2018)
Stop assuming that correlation means causation. Whether you're designing a study or auditing someone else's causal reasoning, this skill makes Claude place claims on Pearl's causal ladder, draw the causal structure, and check whether the data can actually answer the question.
/frame-problem — Fodor (1987), Dennett (1984), Hayes (1973)
Stop acting on assumptions that may no longer hold. Every action assumes things that stay the same — this skill makes Claude name those assumptions and check whether they're still true. It catches three failure modes: ignoring side effects, trying to consider everything, and getting stuck deciding what's relevant.
npx claudepluginhub jackwillis/claude-plugins --plugin systems-analysisFailure-mode-first test design: predict how code breaks, write the guard, mutate to verify (DeMillo/Hoare/Ashby).
Efficient text extraction and format conversion: fetch markdown from URLs, render markdown to PDF, extract text from PDFs, generate name/phrase variations, introduce strategic disfluency.
Use when debugging, investigating root causes, designing experiments, or performing scientific analysis — enforces hypothesis-driven reasoning, evidence-first observation, causality validation, and structured output templates. Use when facing unknowns, repeated failures, or complex investigations requiring rigorous methodology.
Self-documenting, self-improving framework for analytical repositories
Achieve certain comprehension of AI work — /grasp (κατάληψις: a grasping firmly)
Systematic debugging, root cause analysis, log analysis, profiling, binary search debugging, and postmortem analysis.
Decision-support framework evaluating systems through entropy (decay) vs negentropy (growth) while surfacing tacit knowledge gaps.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.