科研 Skill
研究流程阶段导航
using-research-powers
Maps a request to the skill governing its workflow phase and explains the soft-gate checkpoints. Use at the start when unsure which research-workflow skill fits.
SKILL.md
When a skill should fire
When a request falls into a research phase — idea, plan, literature work, source acquisition, ingest, analysis, manuscript, review, wrap-up — invoke the governing skill before you answer or edit. The skill carries what the phase needs and a general answer lacks: the checklist, the preconditions, the audit trail.
The test is what the request leaves behind. If it should change the project — a source page, an entity, a bib entry, a plan, a synthesis, a draft, a review — a skill governs it; use that skill. If the answer lives only in the chat — a single reference, a definition, a date, what a wiki page says, an edit the user dictates word for word — answer directly. A phase skill there is ceremony, and it can steer the user into a workflow (a brainstorming session, a plan) they did not ask for.
Instruction Priority
User instructions always take precedence:
- User's explicit instructions (CLAUDE.md, AGENTS.md, direct requests) — highest priority
- Research-superpowers skills — override default system behavior where they conflict
- Default system prompt — lowest priority
When the user says "skip brainstorming, just draft the chapter": follow the user, but name the skipped phase explicitly. The skill mechanism for these cases is the SOFT-GATE — it logs the decision to knowledge/_meta/gate-overrides.log rather than blocking.
The Research Workflow
Research projects move through phases. Each phase has a governing skill. Phases are gated — later phases cannot proceed without the artifacts the earlier phases produce.
brainstorming-research → input/ideas/<slug>-design.md (SOFT-GATE: design approval)
writing-research-plan → input/ideas/<slug>-plan.md
(SOFT-GATE: pre-registration only for methodology=quantitative/mixed;
for hermeneutic, status=ready is enough)
literature-review → input/bibliography/*, output/bibtex/references.bib (search only — no downloads)
acquire-sources → <library>/pdf/*.pdf, input/bibliography/acquisition-todo.md
(auto-download OA; manual worklist for paywalled; re-run to reconcile)
ingest-source (loop) → knowledge/sources/*, knowledge/entities/*
(HARD-STOP on a missing original — no silent preprint/review substitution)
executing-research-plan → output/data-analysis/*, knowledge/synthesis/*
(runs an acquisition gate before ingest tasks — invokes
acquire-sources automatically inside a plan run, not only interactively)
drafting-manuscript → output/**/*.qmd (SOFT-GATE: ≥1 stable synthesis + lint green)
revising-manuscript → revised text + <name>-revision.md ledger (decisions on disk, approved paragraphs frozen)
requesting-peer-review → review documents + revisions
finishing-a-research-project → rendered publication, archived data, grant follow-up
The phase graph is iterative, not linear. Legitimate back-edges:
ingest-source ↔ writing-research-plan (new reading revises the
hypothesis), executing-research-plan ↔ drafting-manuscript (an analysis
gap surfaced while writing). See docs/phase-flow.md.
Support skills are context-triggered, not phase-bound:
- scaffold-research-project — when the working directory is not yet a research project
- add-to-library — when adding one PDF straight to the shared library (verify + keyword it), outside the project ingest flow
- wiki-lint — before drafting, before finishing, after bulk ingest
- semantic-wiki-review — when the wiki's content needs auditing: contradictions, claims overtaken by newer sources, generic conclusions
- wiki-graph — to analyse the wiki's structure (god nodes, bridges, clusters) and export it as a graph
- drift-report — to check library and projects for accumulated drift (also runs at session start)
- grant-finder — when planning funding in parallel to publication
Two things are deliberately not skills of this plugin:
- Critical evaluation of evidence and method is a checklist inside
executing-research-plan(method selection) andrequesting-peer-review(evidence audit), not a separate skill. - Format utilities — OCR, geodata, image processing, file conversion — come
from the host, if installed. For scans,
ocrmypdfis the tool the drift report andbib-searchalready name.
Routing
digraph research_flow {
"User message received" [shape=doublecircle];
"Should it change the project?" [shape=diamond];
"Starts new research?" [shape=diamond];
"Existing design doc?" [shape=diamond];
"Existing research plan?" [shape=diamond];
"Answer directly" [shape=doublecircle];
"Invoke brainstorming-research" [shape=box];
"Invoke writing-research-plan" [shape=box];
"Invoke the phase's skill" [shape=box];
"Announce: 'Using [skill] to [purpose]'" [shape=box];
"Follow skill checklist" [shape=box];
"Respond" [shape=doublecircle];
"User message received" -> "Should it change the project?";
"Should it change the project?" -> "Answer directly" [label="no — chat-only answer"];
"Should it change the project?" -> "Starts new research?" [label="yes"];
"Starts new research?" -> "Invoke the phase's skill" [label="no — work inside an existing project"];
"Starts new research?" -> "Existing design doc?" [label="yes — a question, study, chapter, grant"];
"Existing design doc?" -> "Invoke brainstorming-research" [label="no"];
"Existing design doc?" -> "Existing research plan?" [label="yes"];
"Existing research plan?" -> "Invoke writing-research-plan" [label="no"];
"Existing research plan?" -> "Invoke the phase's skill" [label="yes"];
"Invoke brainstorming-research" -> "Announce: 'Using [skill] to [purpose]'";
"Invoke writing-research-plan" -> "Announce: 'Using [skill] to [purpose]'";
"Invoke the phase's skill" -> "Announce: 'Using [skill] to [purpose]'";
"Announce: 'Using [skill] to [purpose]'" -> "Follow skill checklist";
"Follow skill checklist" -> "Respond";
}
"Starts new research" means opening a question, study, chapter or grant. Finding literature for a running project, ingesting one more source or revising a section does not — those go straight to their phase skill.
Red Flags
Thoughts that, in this plugin's domain, come right before the failures it exists to prevent — a claim no source backs, a draft written from memory, a review that never happened:
| Thought | Reality |
|---|---|
| "The source is short, I'll skim it" | Ingest requires structured extraction. |
| "I know what the source says" | Knowing ≠ documented. Ingest the source. |
| "I'll just freewrite the draft" | Drafts pull from synthesis pages, not from memory. |
| "I have the hypothesis in my head" | Quantitative: written in the plan. Hermeneutic: research question + method sketch is enough. |
| "I'll clean up the wiki later" | Lint before draft — overrides get logged. |
| "Peer review is optional" | Not before publication, it isn't. |
| "This new project doesn't need a design doc" | Brainstorming first. The user may skip it — then name the skipped phase and log the reason (SOFT-GATE). |
Skill Priority (multiple skills could apply)
- Phase skills first (brainstorming-research, writing-research-plan, literature-review, acquire-sources, ingest-source, executing-research-plan, drafting-manuscript, revising-manuscript, requesting-peer-review, finishing-a-research-project) — these determine WHERE in the workflow you are
- Support skills second (wiki-lint, semantic-wiki-review, wiki-graph, drift-report, add-to-library, grant-finder) — these refine HOW you do a step
- Host utilities last (OCR, file conversion, …) — these handle format questions
Trigger examples:
- "Let's do research on X" → brainstorming-research
- "I have an idea/sketch" → brainstorming-research
- "Write a plan for the project" → writing-research-plan (if design doc exists) or brainstorming-research first
- "Find literature on X" → literature-review
- "Get / download the PDFs", "Quellen beschaffen" → acquire-sources
- "Ingest this source" → ingest-source
- "Add this PDF straight to the library", "in die Bibliothek aufnehmen" → add-to-library
- "Analyze the data" → executing-research-plan (if plan exists) else writing-research-plan first
- "Write the chapter" → drafting-manuscript (if synthesis pages stable) else back to synthesis
- "Let's go through the text paragraph by paragraph", "Absatz für Absatz überarbeiten" → revising-manuscript
- "Review the manuscript" → requesting-peer-review
- "Find funding" → grant-finder
- "Show me a knowledge graph / which entity bridges my sources / most-connected pages" → wiki-graph
- "Who wrote X, and when?" / "What does our page on Tel Rehov say?" → no skill — answer directly
Skill Types
Rigid (must follow the checklist exactly, do not skip steps):
- scaffold-research-project, brainstorming-research, writing-research-plan, acquire-sources, ingest-source, add-to-library, executing-research-plan, drafting-manuscript, revising-manuscript, finishing-a-research-project
Flexible (adapt principles to context):
- literature-review, requesting-peer-review, grant-finder, wiki-lint, semantic-wiki-review, wiki-graph, drift-report
The skill itself tells you which.
How to Access Skills
In Claude Code: Use the Skill tool. The skill content is presented to you — follow it. Never Read a skill file in place of invoking it.
In OpenCode: Skills load natively once installed (see opencode/README.md). Trigger them via natural language or the built-in skill tool (e.g. skill({ name: "ingest-source" })). Skill names carry no research-superpowers: prefix there. The subagents (source-ingester, drafter, …) are launched with the subagent tool.
"Task-list item" in a checklist means whatever task tracker the host gives you: TaskCreate / TaskUpdate in current Claude Code, TodoWrite in older Claude Code builds. OpenCode 2.x has no task tool — keep the list as a checklist in your reply or in the plan file. The skills name the concept, not the tool, so they survive a rename.
The Research Project Template
Every research project uses the same folder layout (from templates/research-project-template/):
project-root/
├── input/ # human-authored: bibliography, data, notes, ideas (design & plan docs live here)
├── knowledge/ # LLM-generated wiki: entities, concepts, sources, synthesis
├── output/ # publishable artifacts: publication (Quarto), data-analysis, bibtex
└── scripts/ # lint-wiki.py, wiki-to-graph.py, library.py, bib-subset.py, bib-search.py
If the working directory is not yet a research project, the first skill invocation should offer to scaffold it from the template.
The source PDFs are not in the repo. They live once, centrally, in the shared library — <library>/pdf/<bibkey>.pdf, where the filename is the citekey. The library path is machine-local: scripts/library.py resolves it (RESEARCH_LIBRARY → .research-library → ~/.config/research-superpowers/library), so never hard-code it. Two scripts read it:
python scripts/bib-subset.py # output/bibtex/references.bib ← the library
python scripts/bib-search.py index # build the full-text index (once, then incremental)
python scripts/bib-search.py "copper smelting" # → bibkey · physical PDF page · snippet
bib-search answers "where does anyone say this?" across every project's sources at once, and returns the page to open. It is the entry point for drafting-manuscript's reach-back when a wiki page carries no page anchor.
示例提示词
我刚开始这个研究对话,帮我判断现在该用哪个技能来推进项目。
所属插件
安装该插件会一并获得同领域的 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.
常见问题
研究流程阶段导航能做什么?
Maps a request to the skill governing its workflow phase and explains the soft-gate checkpoints. Use at the start when unsure which research-workflow skill fits。
如何安装研究流程阶段导航?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「研究流程阶段导航」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
研究流程阶段导航需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
研究流程阶段导航经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。