科研 Skill
神学考古文献检索
literature-review
Searches and catalogues literature for theology, archaeology, and digital humanities into a graded source table. Use to build a literature guide before acquiring sources.
SKILL.md
Prerequisites and Limitations
This skill is part of the research-superpowers workflow family (see
using-research-powers). The checklist below assumes a project scaffolded by
scaffold-research-project, with scripts/bib-search.py and
scripts/forward-search.py present and a shared source library configured.
If those scripts are not present (a plain chat session, no scaffolded
project, no Python), use the manual fallbacks given inline at each step —
querying OpenAlex/Crossref/IxTheo/CORE/arXiv directly by URL, or the author's
own publication list — and say explicitly that the pass was manual. The
dispatch of a literature-scout subagent (step 4) is an optional optimisation
for context isolation, not a requirement; without subagent dispatch, run the
same database queries inline in the main conversation.
Boundary: literature-review → acquire-sources → ingest-source
literature-review runs SEARCH — discovers candidate sources, grades them, builds a strategic guide, produces BibTeX entries. Outputs land in input/bibliography/. It downloads no PDFs and creates no knowledge/sources/*.md. It records each candidate's oa_pdf / DOI so the next phase can fetch it. It searches the shared library first (step 3) — the master bibliography grows with every project, so a new question increasingly overlaps sources you already own, and those cost nothing to "acquire".
acquire-sources runs ACQUISITION — auto-downloads the Open-Access PDFs for the A+B set into input/bibliography/ and writes acquisition-todo.md, a manual-download worklist for everything paywalled or bot-blocked.
ingest-source runs INTAKE — takes ONE already-acquired source PDF and produces the wiki content (Source page, entities, BibTeX entry, log line).
The three skills are sequential, not overlapping. A typical session: literature-review once → acquire-sources once (re-run to reconcile) → ingest-source N times.
Literature Review (Superpowers-Wrapper)
This skill wraps the detailed workflow of research-skills/dao-literature-review (OpenAlex, IxTheo, Zenon-DAI, Propylaeum, Persée, OpenEdition, CORE, arXiv, DNB) with the research-superpowers discipline: checklist, SOFT-GATE against rushing, red-flags against "I have enough sources."
Announce at start: "Using literature-review to build a strategic literature guide for this project."
The threshold of 15 is a rule of thumb for a viable research base, not magic —
a tightly bounded niche topic justifies an undershoot, and a broad debate
demands more. If a condition is unmet: tell the user which, ask for a brief
reason (e.g. "narrow topic with small source corpus"), write it into
knowledge/_meta/gate-overrides.log, and close.
When to use
- User asks for a literature review, state of the field, Forschungsstand, "what has been written on X?"
- Design doc is approved and tasks in the research plan reference uningested sources
- Before drafting a Forschungsstand / state-of-the-field chapter — the chapter pulls from the literature guide
NOT for: single-paper lookups (direct metadata query), ingesting a source you already have (use ingest-source).
Checklist
- Confirm scope with user — field, time range, languages, geographic constraints
- Check for existing
literaturguide.mdininput/bibliography/— if it exists, offer to extend rather than redo - Query the shared library FIRST — before any external database, run
python scripts/bib-search.py "<terms>"over the master library. The library grows with every project, so a new question increasingly overlaps sources you already own — and an owned source needs no acquisition. Two rules make this pay:- Search for the concept, not one string. Enumerate the method's aliases, spelling variants and word stems and
ORthem into the query, and run it in every language the library holds — a German query does not reach an English source — the same discipline asdrafting-manuscript→ "Searching for a concept, not a string".bib-searchalso matches each source's curated keywords, which catch papers that describe a method in prose without ever naming it — exactly the sources a title/abstract search misses. - Aggregate, then screen.
bib-searchreturns page-level hits; collapse them bybibkeyto get the distinct works, then read the snippets and keep only those genuinely on-topic (a stray word match is not a source). Each kept work goes into the weighted table withOA/Zugang = ● Bibliothek(already owned, no acquisition), and itsbibkey+ DOI is passed to the scout in step 4 so the external search fills the gap instead of rediscovering it.
- Search for the concept, not one string. Enumerate the method's aliases, spelling variants and word stems and
- Dispatch
literature-scoutsubagent (seeagents/literature-scout.md) for database queries. Pass the step-3bibkey/DOI list as "already in the library" so the scout dedupes against it and spends its budget on what you don't have. - Screen results — titles first, then abstracts. Grade by relevance (A/B/C). Minimum 15 A/B sources before proceeding (library hits count toward the total).
- Forward pass (5a) — a topic search finds what was written about the question, not what was written in reply to a given work, and not the same author's later word on it. For every A-graded work that is not among the newest in the corpus, run
python scripts/forward-search.py <bibkey-or-doi> --authorand screen what comes back (see "The forward pass" below). Add the replies and later statements that bear on the question to the table, graded like any other candidate; record the outcome per work in the guide.
- Forward pass (5a) — a topic search finds what was written about the question, not what was written in reply to a given work, and not the same author's later word on it. For every A-graded work that is not among the newest in the corpus, run
- Generate
literaturguide.md— it opens with the weighted source table (required; columnsGrade | Autor Jahr | Kurztitel | OA/Zugang | DOI/Link— see "The weighted source table" below), followed by the 9 prose sections (research question, primary sources, debates, methods, open access, gaps, recommended reading order, follow-up searches, BibTeX overview) — the debates section is written in the order things were published and carries the forward-pass block (see "The forward pass"); prose layout per the canonical example (see "Reference Content"). Carry each candidate'soa_pdf/ DOI into the table for the acquisition phase; do not download here. - Export BibTeX → merge into
output/bibtex/references.bib(resolve key conflicts with user before merging) The guide ends with the section Was diese Suche nicht sehen kann (see What this search cannot see). - Write audit log →
input/bibliography/audit-log-<date>.json— include the forward pass: per work theforward-search.py --jsonresult (or "manual"), and which candidates were kept - Update
knowledge/_meta/log.mdwith date, query, result count, guide path - Transition: offer to run
acquire-sourceson the A+B set — it auto-downloads the Open-Access PDFs and writes a manual-download worklist (acquisition-todo.md) for the rest; theningest-sourceper acquired source. The● Bibliotheksources are already present, soacquire-sourcesskips them.
Process Flow
digraph literature_review {
"Confirm scope" [shape=box];
"Existing guide?" [shape=diamond];
"Query shared library (bib-search)" [shape=box];
"Dispatch literature-scout" [shape=box];
"Screen & grade" [shape=box];
"Forward pass on older A works" [shape=box];
"Enough A/B sources?" [shape=diamond];
"Generate literaturguide.md" [shape=box];
"Export BibTeX" [shape=box];
"Write audit log" [shape=box];
"Update _meta/log" [shape=box];
"Offer acquire-sources" [shape=doublecircle];
"Confirm scope" -> "Existing guide?";
"Existing guide?" -> "Query shared library (bib-search)" [label="no"];
"Existing guide?" -> "Query shared library (bib-search)" [label="yes, extend"];
"Query shared library (bib-search)" -> "Dispatch literature-scout" [label="pass owned bibkeys/DOIs"];
"Dispatch literature-scout" -> "Screen & grade";
"Screen & grade" -> "Forward pass on older A works";
"Forward pass on older A works" -> "Enough A/B sources?";
"Enough A/B sources?" -> "Dispatch literature-scout" [label="<15, widen search"];
"Enough A/B sources?" -> "Generate literaturguide.md" [label="≥15"];
"Generate literaturguide.md" -> "Export BibTeX";
"Export BibTeX" -> "Write audit log";
"Write audit log" -> "Update _meta/log";
"Update _meta/log" -> "Offer acquire-sources";
}
The weighted source table (required — section 1 of the guide)
literaturguide.md opens with one graded master table so the reader sees the
whole weighted corpus at a glance and acquire-sources can read the weighting
deterministically. The columns are fixed:
## 1. Quellentabelle (gewichtet)
| Grade | Autor Jahr | Kurztitel | OA/Zugang | DOI/Link |
|-------|------------|-----------|-----------|----------|
| A | Finkelstein 2003 | low-chronology | ✓ OA | [10.1179/…](https://doi.org/10.1179/…) |
| A | Mazar 2005 | chronology-debate | ◐ UB | [10.…](https://doi.org/10.…) |
| B | Finkelstein & Piasetzky 2011 | gap-narrowing | ✓ OA | [10.5615/…](https://doi.org/10.5615/…) |
| C | Kenyon 1957 | digging-up-jericho | ○ Fernleihe | — |
Legende — **Grade:** A core/must-read · B supporting · C peripheral/context.
**OA/Zugang:** ● Bibliothek (already in the shared library — no acquisition) · ✓ OA (auto-downloadable) · ◐ UB (university licence) · ○ Fernleihe (ILL/paywalled, manual) · ✗ (no copy located).
Column rules:
- Grade — relevance to this project's research question: A must-read /
core, B important / supporting, C peripheral / context. Sort A → B → C,
then by year. This is the column
acquire-sourcesfilters on (grade_scope, defaultA,B). - Autor Jahr — first author's surname + year, matching the
autor-jahrwiki slug / bibkey (letter suffix for clashes:Mazar 2011b). - Kurztitel — the same short title used in the PDF filename
autor-jahr-kurztitel.pdf(one to three significant words, hyphen-joined, lowercase). Keeps table row, downloaded file, and wiki page in lockstep. - OA/Zugang — access route, drives acquisition routing:
● Bibliothekalready owned (step 3 found it —acquire-sourcesskips it),✓ OAauto-download,◐ UB/○ Fernleihe→ manual worklist,✗→ no copy located yet. - DOI/Link — a clickable DOI (preferred) or landing / OA-PDF URL;
—if none.
The 9 prose sections (reading order, debates, methods, gaps, full bibliography, audit log) follow the table and add the qualitative depth. The guide closes with a required section on what the search could not see (below).
What this search cannot see (required — last section of the guide)
A search returns what its databases index, in the languages and document types they cover. A reader of the guide — the user, a supervisor, a reviewer — must be able to see the edges of the net, or the list reads as complete when it is not. Write it from this search's actual audit log, not as boilerplate:
## Was diese Suche nicht sehen kann
- **Durchsucht:** <databases actually queried, with date> · **nicht durchsucht:**
<relevant ones skipped or unavailable — e.g. ATLA, L'Année philologique,
JSTOR full text, paid indexes>
- **Sprachen:** queries run in <de, en, fr, …>; not covered: <e.g. Hebrew,
Italian, Spanish scholarship>
- **Dokumenttypen:** <how well monographs, edited volumes, Festschriften,
excavation reports, dissertations are covered — OpenAlex and Crossref are thin
on all of them>
- **Nicht digitalisiert / nicht offen:** <older literature, print-only series,
paywalled items not checked beyond metadata>
- **Ranking-Verzerrung:** citation-count and recency ordering favour the
most-cited, recent, English-language work; name any A-sources found only
through the forward pass or the library, not the topic search
- **Empfohlene Ergänzung:** <the manual routes that would close the gaps —
library catalogue (K10plus/DNB), a specialist bibliography, the reference lists
of the A-sources, asking a colleague>
A search is never "complete"; this section says how incomplete, and where. This table — not the prose-only canonical example — is the binding spec for the weighting; if the example shows an ungraded list, the table here takes precedence and is prepended.
The forward pass
Two sources in a corpus are not two equal voices: one was written knowing the other. A search by topic cannot see that. It returned a 2020 article in one live project while the chapter answering that position cited the author's 2022 restatement — which was in the library and had never been looked at. The forward pass closes that gap.
Which works. Every A-graded work that is not among the newest in the corpus. A work from the last two or three years has had no time to be answered; a work from 1999 that the whole argument leans on has. B-graded works when a debate turns on them.
How. python scripts/forward-search.py <bibkey-or-doi> [...] --author. For each
work it lists:
| List | Source | Tells you |
|---|---|---|
| Cited by | OpenAlex (cites:) | later works that cite it, newest first; ● marks the ones already in a .bib |
| Named in works you own | the library's full-text index | owned works whose text names it, with PDF pages to open |
| Later works by the author | OpenAlex (--author) | everything the first author published since — all topics |
Screening what comes back. The lists are candidates, not findings.
- From Cited by, keep works on this question; a citation in passing is not a reply. Add them to the weighted table and grade them like any other candidate.
- Named in works you own costs nothing to check: open the PDF at the page given and read the sentence. This is where replies in monographs and edited volumes turn up, which OpenAlex mostly lacks.
- From Later works by the author, pick the ones on this question. A later statement by the same author is the first place a changed mind shows — and when the author restates the position instead, that later statement is the one the debate answers.
Neither list is complete. OpenAlex's citation data is thin for monographs and edited volumes: on one checked case it listed 39 citing records and missed two chapters that demonstrably cite the work. The library index knows only what you own. Write "none found", never "unanswered".
In the guide. The debates section follows publication order, and closes with one block per work the pass ran on:
### Verlauf: Bartlett 1999 — Edomites and Idumaeans
- Antworten: Levin 2020 (widerspricht, Anm. 34) · Bienkowski 2025 (setzt eine andere
Deutung dagegen, S. 146) · Marciak 2026 (noch nicht gesichtet)
- Spätere Äußerung des Autors zur Frage: keine gefunden
- Forward pass: OpenAlex 11 Werke, Bibliothek 36 Treffer, 2026-11-10
Say what each reply does only as far as you have read it; "noch nicht gesichtet" is
an honest entry. The typed relation (responds-to / supersedes / revises) is
written at ingest, from the text — not here, from a citation list.
Without the script (no Python, no network): the same three questions by hand —
OpenAlex https://api.openalex.org/works?filter=cites:<work-id>&sort=publication_date:desc,
bib-search.py '"<Surname> <year>"', and the author's publication list. Record that
the pass was manual.
Reference Content
The weighted source table (above) is the binding spec for this skill's output
— it is reproduced here in full so this skill is self-contained. For the raw
API call syntax of each database (OpenAlex, Crossref, Unpaywall, CORE,
Semantic Scholar, arXiv, IxTheo, Zenon-DAI, etc.), query each database's own
REST documentation directly, or use the MCP tools below when available. This
skill does not ship a separate reference.md or example file — everything an
agent needs to run the workflow is in this document.
MCP Optimisation (recommended)
If
dao-paper-search-mcp(seedocs/recommended-mcps.md) is available in the project, use the MCP tools instead of the manual API calls above — they return structurally verified citation blocks (inline_citation.markdown,authoritative_bibliography_line) and prevent Author-Year hallucinations. Otherwise stay on the manual path.
Routing by source bucket:
| Bucket | MCP tools |
|---|---|
| DAO / Levant archaeology | search_zenon, search_iaa, search_adaj |
| Cross-platform (academic) | search_openalex, search_crossref, search_semantic_scholar, search_arxiv, search_core, search_zenodo, search_biorxiv |
| Theology / ancient studies | search_ixtheo, search_propylaeum, search_openedition, search_gnomon |
| Author / place disambiguation | resolve_author (Wikidata + GND), resolve_site (iDAI.gazetteer) |
When using MCPs, paste inline_citation.authoritative_bibliography_line verbatim into the BibTeX export step and feed audit.source_class / audit.warn_marker into the A/B/C grading (aggregator → downgrade to C, suspect → exclude entirely).
Red Flags (rationalisations)
| Thought | Reality |
|---|---|
| "15 sources are enough for now" | 15 is the MINIMUM, not the goal. |
| "English-only is faster" | German and French scholarship goes missing systematically. |
| "I'll search for the people who work on this" | An author-targeted query finds the people you already know, and the corpus then reproduces your reading list. Query the method, not the surname. Replacing three author queries with method-term queries in one review took a corpus from 15 to 27. |
| "One term is enough, it's the standard name" | It is the standard name in your discipline. Spelling variants alone decide hits: on a real library "random labelling" and "random labeling" each found a paper the other missed. |
| "Straight to OpenAlex" | Query the shared library first (step 3). With hundreds of sources already collected, a new question overlaps what you own — and an owned source needs no acquisition. Skipping the local pass re-finds and re-downloads what is already on disk. |
| "I already know the debate" | Knowing it doesn't replace a documented search — reproducibility. |
| "The topic search already found the debate" | It found what is about the question. Replies to a specific work, and the author's own later word, come from the forward pass — a 2022 restatement sat unread in the library of a project whose wiki argued against the 2020 version. |
| "OpenAlex lists no citing works, so nobody answered" | OpenAlex is thin on monographs and edited volumes, where much of this field replies. Check the library's full text, and write "none found". |
| "The audit log is bureaucracy" | Without it the search isn't replicable. |
| "Let me just download the PDFs while I'm here" | Not in this skill — search is download-free now. Record each oa_pdf/DOI; acquire-sources does the fetching. |
Key Principles
- Library first, then the world —
bib-searchthe master library before any external database; the growing shared corpus means a new question increasingly overlaps sources you already own, and those need no acquisition. Feed the owned bibkeys/DOIs to the scout so it fills the gap, not the overlap. - Strategic guide, not a paper dump — structure reading order, debates, gaps
- Query the method, not the author — and give each method every name it has: the other disciplines' term for it, the US and UK spelling, the German/French form. A method is renamed by everyone who borrows it, so a single-term query measures your own vocabulary rather than the field's. Record which term produced which hit — that is a finding about the field, not search bookkeeping.
- German + English + French where the field demands — discipline-specific
- Forward, not only sideways — for the works the argument leans on, ask who answered them and what their author said next; a corpus without that shows positions, not a debate
- OA-first metadata — record each candidate's
oa_pdf/DOI;acquire-sourcesdoes the downloading - Transparency — audit log is a mandatory output
- Keep the handoff open — the A+B set flows into
acquire-sourcesnext, theningest-source
示例提示词
帮我系统检索关于死海古卷年代争议的最新研究现状。
所属插件
安装该插件会一并获得同领域的 62 个 Skill / MCP。
同插件的其他科研 Skill
- 学术文献获取下载Auto-downloads open-access PDFs for graded sources and writes a manual worklist for paywalled items. Use after literature-review, before ingest-source.
- 单篇文献入库管理Adds one verified PDF to a shared bibliography library, computing its citation key and keywords. Use to register a single document outside the full workflow.
- 数字人文计算方法Surveys computational DH methods: text mining, NLP, corpus linguistics, archive standards, GIS, network analysis, and OCR. Use for an overview of available DH tools.
- 考古地理信息系统分析Runs archaeological GIS analysis with GeoPandas: catchment analysis, viewshed, kernel density, spatial statistics. Use for mapping archaeological site locations.
- 论证结构提取可视化Extracts and visualizes argument structure: Toulmin reconstruction, support/attack graphs, circularity detection. Use to diagram an argument’s logical structure.
- 考古遗物类型学分析Performs artifact analysis: typological classification, ceramic attribute coding, lithic reduction analysis. Use when classifying excavated artifacts statistically.
- 引文与出处核查Checks citations, quotations, page numbers, and bibliography entries for accuracy and source fit. Use before submission to verify source-supported claims.
- 研究选题构思设计Explores research intent, field state, methodology, and ethics, then writes an approved design doc. Use before starting a new research question or chapter.
- 术语译名一致性检查Audits a manuscript for terms, translations, abbreviations, and names whose forms must stay stable. Use when terminology drift could undermine an argument.
- 计算语用学分析Runs computational pragmatics: speech act classification, implicature detection, discourse coherence, politeness analysis. Use for language-use-and-meaning studies.
- 文献综述学术对话构建Turns verified sources into a structured scholarly conversation among positions, not a chronological summary. Use when synthesizing literature into a debate narrative.
- 语料库语言学分析Performs corpus analysis with NLTK/spaCy: collocation, keyword analysis, KWIC concordance, word2vec, diachronic trends. Use for quantitative text-corpus research.
- 数字档案馆资源检索Queries digital archive REST APIs: Europeana, Chronicling America, Internet Archive, HathiTrust, DPLA, OAI-PMH. Use when searching or harvesting heritage metadata.
- 学术手稿章节撰写Drafts a chapter or article section by section from synthesized wiki content, agreeing each section’s argument first. Use to turn stable research synthesis into prose.
- 研究项目漂移状态检测Checks a shared source library and registered projects for drift: un-indexed PDFs, unmerged keywords, bibkey collisions. Use to audit a multi-project research setup.
- EMI课堂语料转写分析Segments and annotates classroom transcripts, coding language choice and discourse function with anonymised output. Use to quantify classroom talk or translanguaging.
- 人工智能伦理分析Analyzes AI ethics: algorithmic fairness metrics, bias auditing, value alignment, moral philosophy reasoning. Use to evaluate an AI system’s ethical dimensions.
- 研究计划任务执行Executes a ready research plan task by task, gating acquisition before ingest and dispatching analysis. Use after writing-research-plan to run the planned work.
- 研究项目结项清单Runs the final completion checklist: rendering, bibliography, wiki, data, reproducibility, archiving. Use when a manuscript is finalized and ready to publish.
- 形式逻辑自动推理Applies formal logic tools: Z3 SMT solver, modal logic S5, SAT encoding, Lean4 proof verification. Use to formalize or mechanically check a logical argument.
- 研究问题凝练构建Turns a broad topic or intuition into a precise, contestable, researchable question. Use at the start of a project when no defensible question yet exists.
- 历史地理信息系统分析Performs historical GIS work: georeferencing old maps, digitizing boundaries, temporal territory overlays, population interpolation. Use for historical spatial analysis.
- 历史语言学比较分析Analyzes historical linguistics in Python: sound correspondences, cognate detection, phylogenetic trees, Swadesh lists. Use when reconstructing language relationships.
- 历史社会网络分析Builds historical network analyses: correspondence networks, prosopography, temporal community detection, Gephi export. Use to map relationships among historical actors.
常见问题
神学考古文献检索能做什么?
Searches and catalogues literature for theology, archaeology, and digital humanities into a graded source table. Use to build a literature guide before acquiring sources。
如何安装神学考古文献检索?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「神学考古文献检索」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
神学考古文献检索需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
神学考古文献检索经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。