/competitive-scenario
What will competitors do? — Competitive method progress prediction and
$ npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill competitive-scenario --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
/competitive-scenario
Context preview
The summary Claude sees to decide when to auto-load this skill.
What will competitors do? — Competitive method progress prediction and
SKILL.md
competitive-scenario.SKILL.mdname: competitive-scenario
description: What will competitors do? — Competitive method progress prediction and
time window analysis
version: 1.0.0
category: experiment-execution
type: strategy
sops:
- scenario-driver-identification
- competitive-move-prediction
- timeline-projection
- scenario-impact-assessment
- robustness-scoring
- scenario-synthesis
tactics:
- strategy-robustness-testing
dependencies:
sops:
- competitive-move-prediction
- robustness-scoring
- scenario-driver-identification
- scenario-impact-assessment
- scenario-synthesis
- timeline-projection
tactics:
- strategy-robustness-testing
Strategy: Competitive Scenario
Methodology
Competitive Intelligence Scenario Planning. Predict competitor progress, publication timelines, and methodological breakthroughs that could affect our research positioning. Assess time windows of opportunity and first-mover advantages.
Key principles:
- **Actor-based thinking**: Model specific competitors and their capabilities
- **Publication signals**: Use publication patterns to predict future directions
- **Time windows**: Identify windows of opportunity that may close
- **Preemption risk**: Assess probability of being scooped or rendered redundant
Execution Flow
1. **Identify competitive drivers** → spawn `scenario-driver-identification`
- Input: research field, known competitors, publication landscape
- Output: competitive uncertainty drivers
2. **Predict competitor moves** → spawn `competitive-move-prediction` (×3-5 competitors)
- Input: competitor profile, publication history, resource level
- Output: predicted actions and timelines per competitor
3. **Project timelines** → spawn `timeline-projection`
- Input: competitor predictions, technology maturity
- Output: competitive timeline with key milestones
4. **Assess impact** → spawn `scenario-impact-assessment` (per competitive scenario)
- Input: competitive scenario, our research approach
- Output: positioning impact, window analysis
5. **Score robustness** → spawn `robustness-scoring`
- Input: all competitive assessments
- Output: competitive robustness index
6. **Synthesize** → spawn `scenario-synthesis`
- Input: competitive scenarios, timelines, robustness
- Output: competitive strategy report
Budget Gate
| Step | Token Budget | Notes | |------|-------------|-------| | Driver identification | 8K | Competitor-focused | | Move prediction | 10K × N | N = 3-5 key competitors | | Timeline projection | 12K | Multi-horizon | | Impact assessment | 10K × N | Per competitive scenario | | Robustness scoring | 8K | Competitive positioning | | Synthesis | 12K | Strategy recommendations |
<!-- BEGIN available-tables (generated) -->
Available Tactics
Optional, no fixed order; the final leaf is always a sop.
| Tactic | When to use | | --- | --- | | strategy-robustness-testing | Orchestrates impact assessment and robustness scoring to evaluate research approach resilience across scenarios |
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use | | --- | --- | | competitive-move-prediction | Predict competitor progress, publications, and strategic moves | | robustness-scoring | Compute robustness index across scenarios with sensitivity analysis | | scenario-driver-identification | Identify key uncertainty drivers using PESTEL framework scanning | | scenario-impact-assessment | Assess each scenario's impact on the research approach across multiple dimensions | | scenario-synthesis | Comprehensive scenario analysis report synthesizing all scenario work | | timeline-projection | Extrapolate research landscape timelines using trend analysis and milestone projection |
<!-- END available-tables (generated) -->
Read more
name: competitive-scenario description: What will competitors do? — Competitive method progress prediction and time window analysis version: 1.0.0 category: experiment-execution type: strategy sops: - scenario-driver-identification - competitive-move-prediction - timeline-projection - scenario-impact-assessment - robustness-scoring - scenario-synthesis tactics: - strategy-robustness-testing dependencies: sops: - competitive-move-prediction - robustness-scoring - scenario-driver-identification - scenario-impact-assessment - scenario-synthesis - timeline-projection tactics: - strategy-robustness-testing
Strategy: Competitive Scenario
Methodology
Competitive Intelligence Scenario Planning. Predict competitor progress, publication timelines, and methodological breakthroughs that could affect our research positioning. Assess time windows of opportunity and first-mover advantages.
Key principles:
- **Actor-based thinking**: Model specific competitors and their capabilities
- **Publication signals**: Use publication patterns to predict future directions
- **Time windows**: Identify windows of opportunity that may close
- **Preemption risk**: Assess probability of being scooped or rendered redundant
Execution Flow
1. **Identify competitive drivers** → spawn `scenario-driver-identification`
- Input: research field, known competitors, publication landscape
- Output: competitive uncertainty drivers
2. **Predict competitor moves** → spawn `competitive-move-prediction` (×3-5 competitors)
- Input: competitor profile, publication history, resource level
- Output: predicted actions and timelines per competitor
3. **Project timelines** → spawn `timeline-projection`
- Input: competitor predictions, technology maturity
- Output: competitive timeline with key milestones
4. **Assess impact** → spawn `scenario-impact-assessment` (per competitive scenario)
- Input: competitive scenario, our research approach
- Output: positioning impact, window analysis
5. **Score robustness** → spawn `robustness-scoring`
- Input: all competitive assessments
- Output: competitive robustness index
6. **Synthesize** → spawn `scenario-synthesis`
- Input: competitive scenarios, timelines, robustness
- Output: competitive strategy report
Budget Gate
| Step | Token Budget | Notes | |------|-------------|-------| | Driver identification | 8K | Competitor-focused | | Move prediction | 10K × N | N = 3-5 key competitors | | Timeline projection | 12K | Multi-horizon | | Impact assessment | 10K × N | Per competitive scenario | | Robustness scoring | 8K | Competitive positioning | | Synthesis | 12K | Strategy recommendations |
<!-- BEGIN available-tables (generated) -->
Available Tactics
Optional, no fixed order; the final leaf is always a sop.
| Tactic | When to use | | --- | --- | | strategy-robustness-testing | Orchestrates impact assessment and robustness scoring to evaluate research approach resilience across scenarios |
Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use | | --- | --- | | competitive-move-prediction | Predict competitor progress, publications, and strategic moves | | robustness-scoring | Compute robustness index across scenarios with sensitivity analysis | | scenario-driver-identification | Identify key uncertainty drivers using PESTEL framework scanning | | scenario-impact-assessment | Assess each scenario's impact on the research approach across multiple dimensions | | scenario-synthesis | Comprehensive scenario analysis report synthesizing all scenario work | | timeline-projection | Extrapolate research landscape timelines using trend analysis and milestone projection |
<!-- 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

