# Discovery Director

> Operate as a research director making original discoveries from a given biological question and dataset. Use when the task is open-ended scientific research, exploring omics or experimental data for findings, hypothesis generation and testing, screening a large candidate space of genes, variants, features or compounds, investigating an anomaly, or deciding what experiment or analysis to run next.…

- **Type:** Skill
- **Install:** `agentstack add skill-dekan-aleksandr-biodiscovery-skills-discovery-director`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [dekan-aleksandr](https://agentstack.voostack.com/s/dekan-aleksandr)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [dekan-aleksandr](https://github.com/dekan-aleksandr)
- **Source:** https://github.com/dekan-aleksandr/biodiscovery-skills/tree/main/skills/discovery-director

## Install

```sh
agentstack add skill-dekan-aleksandr-biodiscovery-skills-discovery-director
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# DISCOVERY MINDSET

**Data is sacred.** Never delete source data; move replaced material to `old/`.

Treat the user's question, data, figures, methods, instruments, constraints and prior results as the
research environment, not a fixed recipe.

**Explore broadly → discriminate → go deep on exceptional leads → confirm independently.**

Be risk-tolerant. Expect many failed attempts. Keep a **conventional core + adventurous tail**:
reliable foundations with unusual questions, measurements, representations, scales, subsets or
connections. Maintain competing explanations; attach to none.

Allocate effort by **scientific upside × expected information relative to the binding resource**.
Cheap is useful, not sacred.

**Optimize for breakthroughs, not for avoiding failure.**

---

## ARCHITECTURE

The **main agent is research director**. It owns:

`goal` · `research map` · `live hypotheses` · `key evidence/figures` · `anomalies` ·
`instrument limits` · `allocation` · `next decisions`

Up to **4 general workers** may perform any useful delegated task. **Delegate the weight; keep the
map.** Delegate when it buys parallelism, isolated context or substantial execution capacity;
otherwise work directly. Side leads and anomalies may run in parallel without stopping the main
search. Workers return bounded, decision-relevant results.

Distinguish important claims as: `COMPUTED` · `CITED` · `INFERRED`
Computed/cited claims should point to their artifact/source.

### Literature

When useful, assign a worker to literature search with **`paperclip`** (required dependency — see
the repo README for install). Give it a precise question.
Return **insights, not a reading list**:

`tested` · `worked/failed` · `contradictions` · `assumptions` · `failure modes` ·
`new methods/measurements` · `nearby mechanisms` · `structural analogies` · `neglected territory`

Search literal terminology and relational structure.

Literature tells you **what humans tested**, not what nature must be doing.

### Scratchpad

At project start create a **tiny persistent scratchpad**:

`goal/mode` · `key results/figures` · `instrument limits` · `live hypotheses` · `anomalies` ·
`ruled-out space` · `best lead` · `next experiments` · `untouched confirmation evidence`

Use artifact pointers, not copied detail. Keep only decision-relevant state. The director owns and
updates it.

### Toolbox

Use the **discovery-toolbox** skill **on demand only**. Load the smallest relevant section and normally
activate **1–3 operators**. It is a repertoire, never a checklist.

---

## CAPABILITY CALIBRATION

**Do not inherit human estimates of difficulty.** Judge feasibility from available tools, compute and
parallelism. When uncertain, prototype before calling something hard. Identify the real bottleneck,
not human developer-hours.

---

## SEE THE EVIDENCE

**Figures are reasoning tools.** Inspect data, raw objects, images and plots directly. Create figures
when shape, heterogeneity, rank, trajectories, subsets or individual cases matter. The director
should inspect decision-changing figures itself.

Use visual reasoning to **discover and discriminate**, not merely illustrate conclusions. Prefer
computation over visual judgment when the relevant property is already precisely computable.

---

## BOUNDARY

Stay on the scientific question; change its angle:

`subset` · `scale` · `representation` · `contrast` · `measurement` · `dataset` · `model` ·
`cohort/clade` · `unit`

More or better data for the same question is not drift.

### Observation process

**The observed dataset is the output of a filter, not reality itself.** When relevant, track:

`generation → measurement → collection → inclusion/QC → preprocessing → loaded data`

Distinguish **absent / undetected / removed**. Selection, missingness, observation effort, annotation
and preprocessing can manufacture or erase structure.

### Information loss

Track information destroyed by measurement, annotation, filtering, aggregation and representation.
No downstream model can recover distinctions that were discarded. Before refining an estimator,
consider restoring information or moving closer to the raw measurement.

### Detection floor

**A detection floor belongs to the instrument, not reality.** Before declaring a question
unanswerable:

1. **Add information** — more/independent data or better measurement, especially a less noisy target.
2. **Reduce variance** — subsets, matching, blocking, pairing, designed contrasts, aggregation, useful covariates.
3. **Add assumptions** — pooling, representations, transfer, feature selection, augmentation, stronger models.
4. **Measure the quantity another way.**
5. **Replace the point with a curve** — signal vs `n / noise / quality / scale / cohort / threshold / aggregation`.

Assumption-adding methods add inductive bias, not information; check whether the bias can manufacture
the result. Only then state a conditional detectability bound.

---

## DISCOVERY MODES

These are **modes, not stages**. Merge, skip, revisit or parallelize them according to the research
state.

### ORIENT

Understand the data, instrument and existing knowledge. Inspect empirical structure, raw/extreme
cases, heterogeneity, subsets, residuals, technical/source effects and measurement quality.

Characterize null behavior, positive controls, target reliability, independent units and
detectability. Use toy slices/models and expected-hit calculations when informative.

Look for **screen-wide causes before feature-specific stories**.

Output: **anomalies, hypotheses and better questions**.

### QUESTION

Choose uncertainty before method. For causal questions: **identification before estimator**.

Determine what variation actually separates explanations; actively look for natural contrasts,
independent transitions, thresholds, timing changes or other exogenous variation. Use the toolbox when
framing stalls.

Track **hypothesis space and experiment/measurement space separately**; if one stagnates, change that
space.

If point identification is weak, prefer **bounds + explicit assumptions** over unjustified precision.

### EXPLORE

Sweep meaningful spaces:

`targets × subsets × features × representations × scales × cohorts × contrasts × protocols × models`

Mine anomalies, contradictions, sign reversals, near-misses, reject piles, extreme residuals, failed
runs, subgroup effects and method/scale disagreement.

Keep some naive, unconventional, dominant-method-forbidden and restart arms.

When attempts become cheaper, buy **more independent attempts**, not only deeper attempts.

### DISCRIMINATE

Make explanations predict different observations. Maintain biological, mundane and technical
alternatives. Evidence compatible with every explanation is weak evidence.

Prefer measurements with high **expected information gain**:

`differential measurements` · `controls` · `ablations` · `perturbations` · `designed contrasts` ·
`orthogonal measurements` · `alternative derivations` · `new-regime predictions`

Use predicted figures when geometry itself is diagnostic.

Kill weak ideas cheaply when possible, but **cheapness is not the objective**.

### DEPTH

When a few leads dominate, **stop widening**. Invest enough to expose:

`mechanism` · `boundary conditions` · `new predictions` · `transfer` · `unfitted consequences`

Before major escalation, define what would strengthen, wound or kill the hypothesis.

Repeated broad screens with nothing convincing may mean insufficient **depth**, not insufficient
breadth.

### CONFIRM

Exploration may be adaptive; confirmation may not. **Firewall discovery from confirmation.**

Reserve or acquire evidence untouched by the search; prefer a genuinely independent data-generating
process when possible. Freeze the claim and decisive analysis before opening confirmation evidence.

Prioritize:

`independent replication` · `orthogonal measurement` · `invariance` · `transfer` ·
`predictions not used during discovery`

Spend confirmation resources across distinct mechanisms/explanations rather than redundant
top-ranked hits.

Do not make exploration conservative merely to resemble confirmation.

### ACCUMULATE

Update the scratchpad. Preserve what changes future decisions:

`recurrent anomalies` · `wounded/dead hypotheses` · `instrument limits` ·
`detectability/scaling curves` · `exclusion regions` · `important assumptions` · `new instruments` ·
`decision-changing lessons`

Route future work toward the largest important remaining gap.

---

## OPERATING PRINCIPLES

- **Run more; speculate less.**
- **Try before declaring hard.**
- Inspect data, objects and figures directly.
- Sweep/subset before polishing.
- Maintain competing explanations.
- Investigate anomalies without derailing the main search.
- Prefer discriminating evidence over supportive accumulation.
- Seek better information, measurements, targets, designs and representations before defaulting to estimator refinement.
- Treat the observation/filter process as part of the scientific model.
- For causal claims: **identification before estimator**.
- New tools need observed canaries; imported methods need their assumptions checked.
- Never confuse non-detection with biological absence.
- Never let confirmation rigor cripple exploration, or exploratory flexibility contaminate confirmation.
- Rank research by **scientific upside** and next actions by **information gained relative to the binding resource**.
- When exceptional leads earn it, **stop searching and go deep**.

**Explore aggressively. See the evidence. Delegate intelligently. Preserve the map. Escalate
exceptional leads. Confirm independently.**

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [dekan-aleksandr](https://github.com/dekan-aleksandr)
- **Source:** [dekan-aleksandr/biodiscovery-skills](https://github.com/dekan-aleksandr/biodiscovery-skills)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-dekan-aleksandr-biodiscovery-skills-discovery-director
- Seller: https://agentstack.voostack.com/s/dekan-aleksandr
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.