/boundary-analysis
Boundary Analysis Campaign — probe where methods fail, map validity envelopes,
$ npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill boundary-analysis --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/boundary-analysis
Context preview
The summary Claude sees to decide when to auto-load this skill.
Boundary Analysis Campaign — probe where methods fail, map validity envelopes,
SKILL.md
boundary-analysis.SKILL.mdname: boundary-analysis
description: Boundary Analysis Campaign — probe where methods fail, map validity envelopes,
test robustness, catalog failure modes, detect scaling limits. 5 strategies, 3 tactics,
11 subagent SOPs.
execution: campaign
dependencies:
strategies:
- boundary-critique
- deep-insight-validity-envelope-mapping
- failure-mode-analysis
- robustness-testing
- scaling-frontier
sops:
- boundary-synthesis
- context-checkpoint
- context-init
Boundary Analysis
Probe where methods fail — validity envelopes, robustness, failure modes, scaling limits.
Design Philosophy
This campaign is a strategy book — CC reads, internalizes, and autonomously constructs an approach. The SKILL.md files are textbooks, not scripts.
Strategy Routing
| Signal | Strategy | |--------|----------| | Valid conditions, applicability range, multi-axis variation, degradation curves | → validity-envelope-mapping | | Cross-method consistency, multi-model convergence, Wimsatt robustness | → robustness-testing | | System boundaries, inclusion/exclusion, CSH critique | → boundary-critique | | Failure modes, boundary inputs, distribution shift, adversarial | → failure-mode-analysis | | Scaling limits, scaling law, behavioral phase transitions, capacity | → scaling-frontier |
Available Tactics
- multi-model-convergence — Wimsatt-style cross-validation
- systematic-perturbation — multi-axis validity probing
- failure-mode-cataloging — systematic failure taxonomy
Available SOPs
**Import (5):** web-search, web-research, paper-overview, paper-search, paper-research
**Subagent (11):** assumption-enumeration, alternative-model-generation, convergence-assessment, fragility-flagging, variation-axis-definition, controlled-perturbation, validity-envelope-construction, edge-case-generation, failure-clustering, scaling-regime-detection, boundary-synthesis
**Shared (1):** evidence-synthesis
Context Management
context-checkpoint after each strategy completes.
<!-- BEGIN available-tables (generated) -->
Available Strategies
Optional, no fixed order; the final leaf is always a sop.
| Strategy | When to use | | --- | --- | | boundary-critique | Apply CSH boundary critique — what is included/excluded, who benefits/is harmed, what expertise is privileged/marginalized. Identifies opportunities at the boundaries. | | deep-insight-validity-envelope-mapping | Map multi-dimensional validity envelopes — define variation axes, perturb systematically, measure degradation, construct boundary surface. | | failure-mode-analysis | Systematically catalog failure modes — generate edge cases, observe failures, cluster by mechanism, identify triggers and frequency. | | robustness-testing | Test conclusion robustness via multi-model convergence — enumerate assumptions, generate alternatives, compare results, flag fragile conclusions. | | scaling-frontier | Analyze behavior across scales — detect regime changes, identify capacity limits, fit scaling laws within regimes. |
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use | | --- | --- | | boundary-synthesis | Compile all boundary analysis products into a coherent report — validity envelopes, robustness results, failure catalogs, scaling maps, safe operating conditions. | | context-checkpoint | Append research process and results to the current Phase's context file. Covers both process and results with genuine substance. Use this skill at plan-designated checkpoint points — typically after each strategy completes or at key decision nodes within a research Phase. | | context-init | Create a new context file for a research Phase. Called once at Phase start to initialize the file that subsequent context-checkpoint calls will append to. Use this skill whenever a new research Phase begins and a fresh context file is needed. |
<!-- END available-tables (generated) -->
Read more
name: boundary-analysis description: Boundary Analysis Campaign — probe where methods fail, map validity envelopes, test robustness, catalog failure modes, detect scaling limits. 5 strategies, 3 tactics, 11 subagent SOPs. execution: campaign dependencies: strategies: - boundary-critique - deep-insight-validity-envelope-mapping - failure-mode-analysis - robustness-testing - scaling-frontier sops: - boundary-synthesis - context-checkpoint - context-init
Boundary Analysis
Probe where methods fail — validity envelopes, robustness, failure modes, scaling limits.
Design Philosophy
This campaign is a strategy book — CC reads, internalizes, and autonomously constructs an approach. The SKILL.md files are textbooks, not scripts.
Strategy Routing
| Signal | Strategy | |--------|----------| | Valid conditions, applicability range, multi-axis variation, degradation curves | → validity-envelope-mapping | | Cross-method consistency, multi-model convergence, Wimsatt robustness | → robustness-testing | | System boundaries, inclusion/exclusion, CSH critique | → boundary-critique | | Failure modes, boundary inputs, distribution shift, adversarial | → failure-mode-analysis | | Scaling limits, scaling law, behavioral phase transitions, capacity | → scaling-frontier |
Available Tactics
- multi-model-convergence — Wimsatt-style cross-validation
- systematic-perturbation — multi-axis validity probing
- failure-mode-cataloging — systematic failure taxonomy
Available SOPs
**Import (5):** web-search, web-research, paper-overview, paper-search, paper-research
**Subagent (11):** assumption-enumeration, alternative-model-generation, convergence-assessment, fragility-flagging, variation-axis-definition, controlled-perturbation, validity-envelope-construction, edge-case-generation, failure-clustering, scaling-regime-detection, boundary-synthesis
**Shared (1):** evidence-synthesis
Context Management
context-checkpoint after each strategy completes.
<!-- BEGIN available-tables (generated) -->
Available Strategies
Optional, no fixed order; the final leaf is always a sop.
| Strategy | When to use | | --- | --- | | boundary-critique | Apply CSH boundary critique — what is included/excluded, who benefits/is harmed, what expertise is privileged/marginalized. Identifies opportunities at the boundaries. | | deep-insight-validity-envelope-mapping | Map multi-dimensional validity envelopes — define variation axes, perturb systematically, measure degradation, construct boundary surface. | | failure-mode-analysis | Systematically catalog failure modes — generate edge cases, observe failures, cluster by mechanism, identify triggers and frequency. | | robustness-testing | Test conclusion robustness via multi-model convergence — enumerate assumptions, generate alternatives, compare results, flag fragile conclusions. | | scaling-frontier | Analyze behavior across scales — detect regime changes, identify capacity limits, fit scaling laws within regimes. |
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use | | --- | --- | | boundary-synthesis | Compile all boundary analysis products into a coherent report — validity envelopes, robustness results, failure catalogs, scaling maps, safe operating conditions. | | context-checkpoint | Append research process and results to the current Phase's context file. Covers both process and results with genuine substance. Use this skill at plan-designated checkpoint points — typically after each strategy completes or at key decision nodes within a research Phase. | | context-init | Create a new context file for a research Phase. Called once at Phase start to initialize the file that subsequent context-checkpoint calls will append to. Use this skill whenever a new research Phase begins and a fresh context file is needed. |
<!-- END available-tables (generated) -->
The complete research orchestration system for AI-native science. What It Does Design Philosophy Architecture (v3.2.2) Quick Start Configuration Roadmap License DARE is not a tool that helps you do research. It is the researcher.
Repo: yogsoth-ai/de-anthropocentric-research-engine
Other skills on de-anthropocentric-research-engine.
- /formated-results
Closing skill for the research-executor, loaded as the last step of formated-specs. Summarize the design just produced into one research-result JSON fenced block in your reply. Do not execute the research.
Open skill - /formated-specs
Spec-slot skill for the research-executor. Emit the 4-layer DARE orchestration of the assigned topic as one research-graph JSON fenced block in your reply. Replaces the generic spec-writing step.
Open skill - /injection-fidelity
Loss-1 judge (codex role). Given one sample's de-identified dialogue and its PolicyCard, decide axis-by-axis whether the user-simulator enacted the card's per-axis pressure. Judge enactment of the card, never whether the research is good.
Open skill - /ladder-quality-order
Loss-2 judge (codex role). Over one topic's 6 shuffled research-design samples, pairwise-rank by quality using the D1–D5 standard. Emit the pairwise log; the harness computes the order and the ladder verdicts. Judge quality difference, never against academic standards.
Open skill - /optimization-loop
The optimizer brain for the ladder-foundry pretraining loop. Runs the two-level nested batch loop, delegates gating to gate_eval, attributes a failing batch to one weight (attribute-first), and recovers from disk after compaction. Control flow is fully scripted; only the
Open skill - /acu-nugget-recall
Tactic: Extract atomic units from one paper and score how much of a caller-supplied summary covers. Use for ACU-style binary or Nugget-style ternary recall checks; cannot run without a target summary.
Open skill

