/cold-start
Full crystallization strategy for users who have no research direction
$ npx -y skills add yogsoth-ai/de-anthropocentric-research-engine --skill cold-start --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
/cold-start
Context preview
The summary Claude sees to decide when to auto-load this skill.
Full crystallization strategy for users who have no research direction
SKILL.md
cold-start.SKILL.mdname: cold-start
description: Full crystallization strategy for users who have no research direction
at all. Covers actor profiling, landscape reconnaissance, direction narrowing, obstacle
analysis, goal decomposition, and north-star synthesis. Use when the user's first
message reveals zero specificity about what they want to research.
dependencies:
tactics:
- actor-profiling
- direction-narrowing
- goal-decomposition
- landscape-reconnaissance
- north-star-synthesis
- obstacle-analysis
Cold Start Strategy
The user knows nothing — they want to publish at a top venue but have no idea what to research.
Questioning Protocol
All SOPs in this strategy follow these rules:
- One question at a time — never overwhelm with multiple questions
- Prefer multiple choice when possible — easier to answer
- Always allow "unsure" / "TBD" as legitimate answers
- Always ask WHY — not just "what do you want" but "why do you want it"
- After user answers: confirm understanding before continuing
- If user's answer reveals new information: immediately follow up
- If user declines to answer (privacy): accept, note that downstream work becomes broader/more iterative
Available Tactics
| Tactic | Purpose | |--------|---------| | actor-profiling | Understand who the user is | | landscape-reconnaissance | Broad, shallow field exploration | | direction-narrowing | Focus within chosen field(s) | | obstacle-analysis | Identify and mitigate barriers | | goal-decomposition | KAOS-style AND/OR goal structuring | | north-star-synthesis | Converge into North Star + ResearchBrief |
Default Flow (reference only)
actor-profiling → landscape-reconnaissance → direction-narrowing
→ obstacle-analysis → goal-decomposition → north-star-synthesis
This is a reference, not a mandate. You decide the actual execution path.
Iteration Points
- From obstacle-analysis: may return to landscape-reconnaissance, direction-narrowing, or obstacle-analysis itself
- From goal-decomposition: may return to landscape-reconnaissance, direction-narrowing, obstacle-analysis, or goal-decomposition itself
How to Use This Strategy
You are the general. This strategy gives you: 1. A default flow as starting reference 2. Available tactics with their purposes 3. Iteration points where backtracking makes sense
What you decide:
- Whether to execute a tactic fully or partially
- Whether to skip a tactic entirely
- Whether to invoke individual SOPs directly (bypassing tactic framing)
- When to iterate and where to return to
- When enough information exists to move forward
The only non-negotiable: the process ends with north-star-synthesis producing a North Star + ResearchBrief that the user confirms.
<!-- BEGIN available-tables (generated) -->
Available Tactics
Optional, no fixed order; the final leaf is always a sop.
| Tactic | When to use | | --- | --- | | actor-profiling | Understand who the user is — background, resources, constraints, and deep motivations. Produces an ActorProfile that informs all downstream decisions. Use this tactic at the start of any crystallization process to build a model of the user's capabilities, limitations, and intent. | | direction-narrowing | Focus within the user's chosen field(s). Identify specific sub-directions through deep paper and web research, then present ranked candidates. Use after landscape-reconnaissance has identified fields of interest. | | goal-decomposition | Structure the user's chosen direction into a formal goal tree using KAOS-style AND/OR decomposition. Validate feasibility against ActorProfile and ObstacleReport. Use after obstacle-analysis confirms the direction is viable. | | landscape-reconnaissance | Broad, shallow exploration of candidate research fields. Understand what's out there before narrowing. Use when the user needs to discover which fields are available to them — especially in cold-start and warm-start scenarios. | | north-star-synthesis | Converge all accumulated context into a crystallized North Star statement and structured ResearchBrief. Performs self-review before presenting to user. Use as the final tactic in any start mode — this is where everything comes together. | | obstacle-analysis | Identify what blocks the user from pursuing their chosen direction, assess severity, propose mitigations with search-validated evidence, and get user acceptance. Use after direction-narrowing has identified a specific direction. |
<!-- END available-tables (generated) -->
Read more
name: cold-start description: Full crystallization strategy for users who have no research direction at all. Covers actor profiling, landscape reconnaissance, direction narrowing, obstacle analysis, goal decomposition, and north-star synthesis. Use when the user's first message reveals zero specificity about what they want to research. dependencies: tactics: - actor-profiling - direction-narrowing - goal-decomposition - landscape-reconnaissance - north-star-synthesis - obstacle-analysis
Cold Start Strategy
The user knows nothing — they want to publish at a top venue but have no idea what to research.
Questioning Protocol
All SOPs in this strategy follow these rules:
- One question at a time — never overwhelm with multiple questions
- Prefer multiple choice when possible — easier to answer
- Always allow "unsure" / "TBD" as legitimate answers
- Always ask WHY — not just "what do you want" but "why do you want it"
- After user answers: confirm understanding before continuing
- If user's answer reveals new information: immediately follow up
- If user declines to answer (privacy): accept, note that downstream work becomes broader/more iterative
Available Tactics
| Tactic | Purpose | |--------|---------| | actor-profiling | Understand who the user is | | landscape-reconnaissance | Broad, shallow field exploration | | direction-narrowing | Focus within chosen field(s) | | obstacle-analysis | Identify and mitigate barriers | | goal-decomposition | KAOS-style AND/OR goal structuring | | north-star-synthesis | Converge into North Star + ResearchBrief |
Default Flow (reference only)
actor-profiling → landscape-reconnaissance → direction-narrowing → obstacle-analysis → goal-decomposition → north-star-synthesis
This is a reference, not a mandate. You decide the actual execution path.
Iteration Points
- From obstacle-analysis: may return to landscape-reconnaissance, direction-narrowing, or obstacle-analysis itself
- From goal-decomposition: may return to landscape-reconnaissance, direction-narrowing, obstacle-analysis, or goal-decomposition itself
How to Use This Strategy
You are the general. This strategy gives you: 1. A default flow as starting reference 2. Available tactics with their purposes 3. Iteration points where backtracking makes sense
What you decide:
- Whether to execute a tactic fully or partially
- Whether to skip a tactic entirely
- Whether to invoke individual SOPs directly (bypassing tactic framing)
- When to iterate and where to return to
- When enough information exists to move forward
The only non-negotiable: the process ends with north-star-synthesis producing a North Star + ResearchBrief that the user confirms.
<!-- BEGIN available-tables (generated) -->
Available Tactics
Optional, no fixed order; the final leaf is always a sop.
| Tactic | When to use | | --- | --- | | actor-profiling | Understand who the user is — background, resources, constraints, and deep motivations. Produces an ActorProfile that informs all downstream decisions. Use this tactic at the start of any crystallization process to build a model of the user's capabilities, limitations, and intent. | | direction-narrowing | Focus within the user's chosen field(s). Identify specific sub-directions through deep paper and web research, then present ranked candidates. Use after landscape-reconnaissance has identified fields of interest. | | goal-decomposition | Structure the user's chosen direction into a formal goal tree using KAOS-style AND/OR decomposition. Validate feasibility against ActorProfile and ObstacleReport. Use after obstacle-analysis confirms the direction is viable. | | landscape-reconnaissance | Broad, shallow exploration of candidate research fields. Understand what's out there before narrowing. Use when the user needs to discover which fields are available to them — especially in cold-start and warm-start scenarios. | | north-star-synthesis | Converge all accumulated context into a crystallized North Star statement and structured ResearchBrief. Performs self-review before presenting to user. Use as the final tactic in any start mode — this is where everything comes together. | | obstacle-analysis | Identify what blocks the user from pursuing their chosen direction, assess severity, propose mitigations with search-validated evidence, and get user acceptance. Use after direction-narrowing has identified a specific direction. |
<!-- 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

