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…
Which assumptions are most fragile? — Vulnerability ranking + impact
$ npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill assumption-constraint --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/assumption-constraintContext preview
The summary Claude sees to decide when to auto-load this skill.
Which assumptions are most fragile? — Vulnerability ranking + impact
name: assumption-constraint description: Which assumptions are most fragile? — Vulnerability ranking + impact assessment of experiment assumptions version: 1.0.0 category: experiment-execution type: strategy sops: - assumption-challenging - resource-quantification tactics: - sensitivity-ranking dependencies: sops: - assumption-challenging - resource-quantification tactics: - sensitivity-ranking
Systematic assumption vulnerability analysis:
Assumption categories: | Category | Examples | |----------|----------| | Technical | Method convergence, architecture suitability | | Data | Availability, quality, representativeness | | Resource | Sufficiency of compute, time, expertise | | Environmental | Tool stability, API access, policy | | Theoretical | Effect existence, measurability, magnitude |
1. **Challenge Assumptions** → call `assumption-challenging` SOP
2. **Quantify Validation Cost** → call `resource-quantification` SOP
3. **Rank Sensitivity** → invoke `sensitivity-ranking` tactic
4. **Report** → synthesize vulnerability assessment
| Resource | Budget | Notes | |----------|--------|-------| | Subagent calls | ≤5 | 2 SOPs + synthesis | | Iterations | ≤2 | Re-rank if new assumptions surface | | Output size | ≤3000 tokens | Ranked table + validation plan |
<!-- BEGIN available-tables (generated) -->
Optional, no fixed order; the final leaf is always a sop.
| Tactic | When to use | | --- | --- | | sensitivity-ranking | Rank constraints by sensitivity — which ones most impact the outcome if they shift |
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use | | --- | --- | | assumption-challenging | Challenge each assumption's validity — shared cross-repo SOP | | resource-quantification | Quantify resource demand vs supply vs gap for each resource category |
<!-- 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
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…
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.…
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…
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…
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…
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…