/appropriateness-bounding
Establish acceptability standards through RAND/UCLA Appropriateness Method
$ npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill appropriateness-bounding --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
/appropriateness-bounding
Context preview
The summary Claude sees to decide when to auto-load this skill.
Establish acceptability standards through RAND/UCLA Appropriateness Method
SKILL.md
appropriateness-bounding.SKILL.mdname: appropriateness-bounding
description: Establish acceptability standards through RAND/UCLA Appropriateness Method
or Consensus Conference protocols.
dependencies:
tactics:
- iterative-convergence-round
- threshold-calibration
sops:
- consensus-synthesis
Appropriateness Bounding
**Purpose:** Determine what is appropriate, acceptable, or indicated for a given context. Uses the RAND/UCLA Appropriateness Method (rating + discussion + re-rating) or Consensus Conference (citizen jury) format to establish boundaries of acceptability.
**When to use:**
- Medical guideline development (appropriate indications)
- Regulatory standard setting
- Establishing acceptable thresholds for action
- Any question of the form "is X appropriate when Y?"
Budget
| Parameter | Constraint | |-----------|-----------| | Rounds | 2 (rate → discuss → re-rate) | | Perspectives | ≥4 (ideally 7–15 for RAND/UCLA) | | Rating scale | 1–9 (inappropriate to appropriate) | | Agreement threshold | Median ≥7 without disagreement |
State Ledger
| Key | Type | Description | |-----|------|-------------| | indications | array | List of scenarios to rate | | perspectives | array | Panel member perspectives | | round_1_ratings | array | Initial ratings per indication | | discussion_notes | string | Key points from discussion | | round_2_ratings | array | Post-discussion ratings | | classifications | object | Appropriate/uncertain/inappropriate per item |
Available Tactics
- **iterative-convergence-round** — Two-round rate-discuss-rerate cycle
- **threshold-calibration** — Determine where appropriateness boundaries fall
Available SOPs
- judgment-collection
- feedback-distribution
- consensus-measurement
- round-decision
- threshold-sweep
- consensus-classification
- consensus-synthesis
Execution Guidance
1. Define indications/scenarios clearly (clinical scenarios, use cases) 2. Collect Round 1 ratings (1–9 scale) with brief rationale 3. Distribute feedback showing distribution of ratings 4. Facilitate structured discussion of disagreements 5. Collect Round 2 ratings 6. Classify each indication: appropriate (median 7–9), uncertain (4–6), inappropriate (1–3) 7. Flag items with disagreement (where panel lacks agreement despite median)
Output Format
classifications:
appropriate: [{indication, median, agreement_level}, ...]
uncertain: [{indication, median, agreement_level}, ...]
inappropriate: [{indication, median, agreement_level}, ...]
disagreement_items: [{indication, reason}, ...]
panel_size: <int>
method: RAND/UCLA | Consensus Conference<!-- BEGIN available-tables (generated) -->
Available Tactics
Optional, no fixed order; the final leaf is always a sop.
| Tactic | When to use | | --- | --- | | iterative-convergence-round | Execute one full Delphi round — collect judgments, distribute anonymous feedback, measure consensus, decide whether to continue. | | threshold-calibration | Systematically sweep consensus thresholds to observe which items achieve consensus at what level, producing a threshold-consensus curve. |
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use | | --- | --- | | consensus-synthesis | Synthesize all rounds into a final consensus report documenting agreements, dissent, and process. |
<!-- END available-tables (generated) -->
Read more
name: appropriateness-bounding description: Establish acceptability standards through RAND/UCLA Appropriateness Method or Consensus Conference protocols. dependencies: tactics: - iterative-convergence-round - threshold-calibration sops: - consensus-synthesis
Appropriateness Bounding
**Purpose:** Determine what is appropriate, acceptable, or indicated for a given context. Uses the RAND/UCLA Appropriateness Method (rating + discussion + re-rating) or Consensus Conference (citizen jury) format to establish boundaries of acceptability.
**When to use:**
- Medical guideline development (appropriate indications)
- Regulatory standard setting
- Establishing acceptable thresholds for action
- Any question of the form "is X appropriate when Y?"
Budget
| Parameter | Constraint | |-----------|-----------| | Rounds | 2 (rate → discuss → re-rate) | | Perspectives | ≥4 (ideally 7–15 for RAND/UCLA) | | Rating scale | 1–9 (inappropriate to appropriate) | | Agreement threshold | Median ≥7 without disagreement |
State Ledger
| Key | Type | Description | |-----|------|-------------| | indications | array | List of scenarios to rate | | perspectives | array | Panel member perspectives | | round_1_ratings | array | Initial ratings per indication | | discussion_notes | string | Key points from discussion | | round_2_ratings | array | Post-discussion ratings | | classifications | object | Appropriate/uncertain/inappropriate per item |
Available Tactics
- **iterative-convergence-round** — Two-round rate-discuss-rerate cycle
- **threshold-calibration** — Determine where appropriateness boundaries fall
Available SOPs
- judgment-collection
- feedback-distribution
- consensus-measurement
- round-decision
- threshold-sweep
- consensus-classification
- consensus-synthesis
Execution Guidance
1. Define indications/scenarios clearly (clinical scenarios, use cases) 2. Collect Round 1 ratings (1–9 scale) with brief rationale 3. Distribute feedback showing distribution of ratings 4. Facilitate structured discussion of disagreements 5. Collect Round 2 ratings 6. Classify each indication: appropriate (median 7–9), uncertain (4–6), inappropriate (1–3) 7. Flag items with disagreement (where panel lacks agreement despite median)
Output Format
classifications:
appropriate: [{indication, median, agreement_level}, ...]
uncertain: [{indication, median, agreement_level}, ...]
inappropriate: [{indication, median, agreement_level}, ...]
disagreement_items: [{indication, reason}, ...]
panel_size: <int>
method: RAND/UCLA | Consensus Conference<!-- BEGIN available-tables (generated) -->
Available Tactics
Optional, no fixed order; the final leaf is always a sop.
| Tactic | When to use | | --- | --- | | iterative-convergence-round | Execute one full Delphi round — collect judgments, distribute anonymous feedback, measure consensus, decide whether to continue. | | threshold-calibration | Systematically sweep consensus thresholds to observe which items achieve consensus at what level, producing a threshold-consensus curve. |
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use | | --- | --- | | consensus-synthesis | Synthesize all rounds into a final consensus report documenting agreements, dissent, and process. |
<!-- 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

