Skill Tracer
Skills › Scientific Agent Skills › hypothesis-generation › literature_search_strategies.md

literature_search_strategies.md

208 lines · skills/hypothesis-generation/references/literature_search_strategies.md at 5f2bc03

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1# Evidence Search and Source Traceability
2

Evidence Search and Source Traceability

Raw lines 1 to 2
3## Scope
4
5This workflow supports hypothesis formulation. It is not automatically a systematic review, evidence-grade, patentability search, regulatory determination, or proof of novelty.
6

Scope

This workflow supports hypothesis formulation. It is not automatically a systematic review, evidence-grade, patentability search, regulatory determination, or proof of novelty.

Raw lines 3 to 6
7## Data and confidentiality gate
8
9Before searching:
11- remove confidential identifiers, unpublished results, proprietary sequences, exact vulnerabilities, and controlled operational details from queries;
12- confirm that external search is authorized;
13- translate sensitive observations into the minimum non-sensitive concepts needed;
14- use approved local or institutional search tools when policy requires;
15- record what was withheld and how that limits the search.
17Do not send unpublished or sensitive data to an external search engine, AI service, citation service, or model without explicit authorization.

Data and confidentiality gate

Before searching:

  • remove confidential identifiers, unpublished results, proprietary sequences, exact vulnerabilities, and controlled operational details from queries;
  • confirm that external search is authorized;
  • translate sensitive observations into the minimum non-sensitive concepts needed;
  • use approved local or institutional search tools when policy requires;
  • record what was withheld and how that limits the search.

Do not send unpublished or sensitive data to an external search engine, AI service, citation service, or model without explicit authorization.

Raw lines 7 to 18
19## Frame the search
21Separate search objectives:
231. **Phenomenon:** Has the observation or a close analogue been reported?
242. **Mechanism:** Which processes could explain it?
253. **Rivals:** Which alternative mechanisms, artifacts, or biases are documented?
264. **Measurement:** How have the constructs been operationalized and validated?
275. **Design:** Which tests discriminate the candidates?
286. **Contrary evidence:** What findings challenge each candidate?
297. **Safety and governance:** Which ethical, biosafety, dual-use, data, or regulatory rules apply?
308. **Priority/novelty:** What prior work, registrations, preprints, patents, and grey literature address the same claim?
32Use separate queries so a mechanism search is not mistaken for a novelty search.

Frame the search

Separate search objectives:

  1. Phenomenon: Has the observation or a close analogue been reported?
  2. Mechanism: Which processes could explain it?
  3. Rivals: Which alternative mechanisms, artifacts, or biases are documented?
  4. Measurement: How have the constructs been operationalized and validated?
  5. Design: Which tests discriminate the candidates?
  6. Contrary evidence: What findings challenge each candidate?
  7. Safety and governance: Which ethical, biosafety, dual-use, data, or regulatory rules apply?
  8. Priority/novelty: What prior work, registrations, preprints, patents, and grey literature address the same claim?

Use separate queries so a mechanism search is not mistaken for a novelty search.

Raw lines 19 to 33
34## Question structures
36Choose a structure matched to the question:
38- PICO/PICOT: population, intervention, comparator, outcome, optional time;
39- PECO: population, exposure, comparator, outcome;
40- diagnostic: population, index test, reference standard, target condition;
41- prognostic: population, prognostic factor, outcome, time;
42- qualitative: population/sample, phenomenon, context;
43- mechanistic: system, perturbation/condition, mediator/process, observable outcome;
44- computational/theoretical: model class, assumptions, parameter regime, predicted observable.
46Cochrane uses PICO for intervention-effect review questions and distinguishes review PICO, PICO for each synthesis, and PICO of included studies. Do not force PICO onto every domain.

Question structures

Choose a structure matched to the question:

  • PICO/PICOT: population, intervention, comparator, outcome, optional time;
  • PECO: population, exposure, comparator, outcome;
  • diagnostic: population, index test, reference standard, target condition;
  • prognostic: population, prognostic factor, outcome, time;
  • qualitative: population/sample, phenomenon, context;
  • mechanistic: system, perturbation/condition, mediator/process, observable outcome;
  • computational/theoretical: model class, assumptions, parameter regime, predicted observable.

Cochrane uses PICO for intervention-effect review questions and distinguishes review PICO, PICO for each synthesis, and PICO of included studies. Do not force PICO onto every domain.

Raw lines 34 to 47
48## Source priority
50Prefer the source closest to the claim:
521. law, regulation, official policy, or current institutional guidance for governance claims;
532. original paper, protocol, dataset, standard, or methods source for primary claims;
543. current reporting guideline and explanation/elaboration for reporting expectations;
554. systematic review or consensus report for landscape orientation;
565. narrative review for terminology and citation mining;
576. preprint or conference abstract, clearly labeled, for recent unreviewed work;
587. secondary webpages only when they point to a primary source or document current implementation.
60Authority does not replace critical appraisal. A primary study may be weak, and a current official policy may be jurisdiction-specific.

Source priority

Prefer the source closest to the claim:

  1. law, regulation, official policy, or current institutional guidance for governance claims;
  2. original paper, protocol, dataset, standard, or methods source for primary claims;
  3. current reporting guideline and explanation/elaboration for reporting expectations;
  4. systematic review or consensus report for landscape orientation;
  5. narrative review for terminology and citation mining;
  6. preprint or conference abstract, clearly labeled, for recent unreviewed work;
  7. secondary webpages only when they point to a primary source or document current implementation.

Authority does not replace critical appraisal. A primary study may be weak, and a current official policy may be jurisdiction-specific.

Raw lines 48 to 61
62## Search sequence

Search sequence

Raw lines 62 to 63
64### 1. Broad orientation
66- Search the phenomenon and field terminology.
67- Locate one or more current reviews or consensus documents.
68- Extract synonyms, controlled vocabulary, candidate mechanisms, and landmark sources.

1. Broad orientation

  • Search the phenomenon and field terminology.
  • Locate one or more current reviews or consensus documents.
  • Extract synonyms, controlled vocabulary, candidate mechanisms, and landmark sources.
Raw lines 64 to 69
70### 2. Primary evidence
72- Search each candidate mechanism separately.
73- Search the original observation and closest analogues.
74- Search prospective, experimental, longitudinal, and replication evidence where relevant.
75- Search measurement-validation papers for each operationalization.

2. Primary evidence

  • Search each candidate mechanism separately.
  • Search the original observation and closest analogues.
  • Search prospective, experimental, longitudinal, and replication evidence where relevant.
  • Search measurement-validation papers for each operationalization.
Raw lines 70 to 76
77### 3. Rival and falsification search
79For every candidate, run terms such as:
81- alternative explanation;
82- confounding;
83- selection bias;
84- collider bias;
85- reverse causation;
86- measurement error/artifact;
87- negative control;
88- failed replication;
89- null or contradictory result;
90- boundary condition/effect modification.
92Record whether a source challenges the mechanism, the measurement, the design, or only its generalizability.

3. Rival and falsification search

For every candidate, run terms such as:

  • alternative explanation;
  • confounding;
  • selection bias;
  • collider bias;
  • reverse causation;
  • measurement error/artifact;
  • negative control;
  • failed replication;
  • null or contradictory result;
  • boundary condition/effect modification.

Record whether a source challenges the mechanism, the measurement, the design, or only its generalizability.

Raw lines 77 to 93
94### 4. Foundational and historical search
96Use backward citation tracing from methods and review papers. Search original titles, authors, books, standards, and DOI/PMID records. Recency is not a proxy for relevance.

4. Foundational and historical search

Use backward citation tracing from methods and review papers. Search original titles, authors, books, standards, and DOI/PMID records. Recency is not a proxy for relevance.

Raw lines 94 to 97
98### 5. Forward citation and registration search
100Use citation indexes, trial registries, preregistration repositories, preprint servers, data/code repositories, and correction/retraction records as appropriate.

5. Forward citation and registration search

Use citation indexes, trial registries, preregistration repositories, preprint servers, data/code repositories, and correction/retraction records as appropriate.

Raw lines 98 to 101
102### 6. Policy search
104Use current official sites and record:
106- jurisdiction and applicability;
107- effective or revision date;
108- superseded documents;
109- local implementation requirements;
110- date checked.
112For high-consequence work, a search result is not legal, regulatory, ethics, biosafety, or dual-use clearance.

6. Policy search

Use current official sites and record:

  • jurisdiction and applicability;
  • effective or revision date;
  • superseded documents;
  • local implementation requirements;
  • date checked.

For high-consequence work, a search result is not legal, regulatory, ethics, biosafety, or dual-use clearance.

Raw lines 102 to 113
114## Search documentation
116Complete `assets/search_boundary_template.json`. At minimum include:
118- `search_boundary_id`;
119- `searched_on`;
120- purpose;
121- databases/indexes;
122- exact queries or reproducible query descriptions;
123- date/language/source-type limits;
124- inclusion and exclusion scope;
125- stop rule or last result screened;
126- known access and coverage limitations;
127- novelty status.
129Use `novelty_status: not_assessed` unless a qualified human has reviewed a fit-for-purpose search. Even a comprehensive search supports only a bounded statement.

Search documentation

Complete assets/search_boundary_template.json. At minimum include:

  • search_boundary_id;
  • searched_on;
  • purpose;
  • databases/indexes;
  • exact queries or reproducible query descriptions;
  • date/language/source-type limits;
  • inclusion and exclusion scope;
  • stop rule or last result screened;
  • known access and coverage limitations;
  • novelty status.

Use novelty_status: not_assessed unless a qualified human has reviewed a fit-for-purpose search. Even a comprehensive search supports only a bounded statement.

Raw lines 114 to 130
131## Evidence ledger
133Complete `assets/evidence_ledger_template.csv` with one row per source:
135- stable source ID;
136- linked claim IDs;
137- title and author/organization;
138- publication date;
139- source type and identifier;
140- canonical HTTPS URL;
141- access date;
142- relation: supportive, challenging, contextual, method, safety, or mixed;
143- design/document type;
144- limitations and notes.
146The audit validates structure and links only:
148```bash
149python3 scripts/audit_evidence_ledger.py \
150 local-evidence-ledger.csv \
151 local-search-boundary.json \
152 --record local-hypothesis-record.json
153```
155It does not visit URLs, verify existence, appraise evidence, or decide whether a citation supports a claim.

Evidence ledger

Complete assets/evidence_ledger_template.csv with one row per source:

  • stable source ID;
  • linked claim IDs;
  • title and author/organization;
  • publication date;
  • source type and identifier;
  • canonical HTTPS URL;
  • access date;
  • relation: supportive, challenging, contextual, method, safety, or mixed;
  • design/document type;
  • limitations and notes.

The audit validates structure and links only:

python3 scripts/audit_evidence_ledger.py \
  local-evidence-ledger.csv \
  local-search-boundary.json \
  --record local-hypothesis-record.json

It does not visit URLs, verify existence, appraise evidence, or decide whether a citation supports a claim.

Raw lines 131 to 156
Runs code python3 scripts/audit_evidence_ledger.py :149
157## Claim-to-source notes
159For each consequential claim, record:
161- the exact source location (section, table, figure, page, or quoted sentence);
162- whether the evidence is direct, indirect, analogous, or contradictory;
163- study design and target population/system;
164- magnitude and uncertainty actually reported;
165- key limitations and conflicts;
166- applicability to the candidate.
168Verify every identifier and claim against the source. Do not rely on search snippets or AI-generated citations.

Claim-to-source notes

For each consequential claim, record:

  • the exact source location (section, table, figure, page, or quoted sentence);
  • whether the evidence is direct, indirect, analogous, or contradictory;
  • study design and target population/system;
  • magnitude and uncertainty actually reported;
  • key limitations and conflicts;
  • applicability to the candidate.

Verify every identifier and claim against the source. Do not rely on search snippets or AI-generated citations.

Raw lines 157 to 169
170## Search stopping
172Use a documented stop rule, such as:
174- all prespecified databases searched;
175- a fixed result depth screened per query;
176- forward/backward citation tracing completed for named seed sources;
177- predefined date and language boundary reached;
178- saturation documented for terminology or mechanisms.
180Do not stop merely because:
182- preferred evidence was found;
183- new results seem repetitive;
184- a citation count is high;
185- a source appears in a prestigious venue.

Search stopping

Use a documented stop rule, such as:

  • all prespecified databases searched;
  • a fixed result depth screened per query;
  • forward/backward citation tracing completed for named seed sources;
  • predefined date and language boundary reached;
  • saturation documented for terminology or mechanisms.

Do not stop merely because:

  • preferred evidence was found;
  • new results seem repetitive;
  • a citation count is high;
  • a source appears in a prestigious venue.
Raw lines 170 to 186
187## Reporting bounded conclusions
189Use:
191> Searches were conducted on YYYY-MM-DD in [indexes] using [queries/strategy]. Within the documented date, language, access, and screening limits, we located [scope]. This does not establish universal absence, priority, or novelty.
193For gaps:
195> No directly matching source was located within the documented search boundary. Related work was found on [near neighbors]. A broader specialist search is required before making a novelty claim.

Reporting bounded conclusions

Use:

Searches were conducted on YYYY-MM-DD in [indexes] using [queries/strategy]. Within the documented date, language, access, and screening limits, we located [scope]. This does not establish universal absence, priority, or novelty.

For gaps:

No directly matching source was located within the documented search boundary. Related work was found on [near neighbors]. A broader specialist search is required before making a novelty claim.
Raw lines 187 to 196
197## Common failures
199- Treating impact factor or citation count as study validity
200- Searching only for support
201- Using only one database
202- Ignoring terminology changes or historical work
203- Citing a review for a claim that should cite the primary study
204- Treating preprints as peer-reviewed
205- Omitting corrections, retractions, or protocol/registration records
206- Searching confidential text verbatim
207- Claiming an exhaustive search without a reproducible protocol
208- Conflating “not found” with “does not exist”

Common failures

  • Treating impact factor or citation count as study validity
  • Searching only for support
  • Using only one database
  • Ignoring terminology changes or historical work
  • Citing a review for a claim that should cite the primary study
  • Treating preprints as peer-reviewed
  • Omitting corrections, retractions, or protocol/registration records
  • Searching confidential text verbatim
  • Claiming an exhaustive search without a reproducible protocol
  • Conflating “not found” with “does not exist”
Raw lines 197 to 208