科研 Skill
研究项目结项清单
finishing-a-research-project
Runs the final completion checklist: rendering, bibliography, wiki, data, reproducibility, archiving. Use when a manuscript is finalized and ready to publish.
SKILL.md
Finishing a Research Project
The project is done only when the last checklist is green. This skill walks the final mile: rendering, archiving, DOI, submission, and optional grant follow-up.
Announce at start: "Using finishing-a-research-project to close out <slug>."
For unmet items: tell the user which, ask for a short reason per skipped item,
write reasons into knowledge/_meta/gate-overrides.log, and mark the project
in the log as either status: done (with documented omissions) or
status: paused. Hidden partial completion is not closure — explicit
justification is.
Closing Checklist
- Manuscript renders cleanly —
make renderinoutput/<book|article>/exits 0; PDF/HTML opens without warnings - Wiki lint green —
python scripts/lint-wiki.pyexits 0 - BibTeX consistent — every citation key in the manuscript exists in
references.bib; no unused keys (or unused are intentional) - Peer review done — both constructive and adversarial reviewer reports archived under
output/<target>/reviews/; all Major issues resolved or explicitly deferred with rationale - Hypothesis addressed — pre-registered Hypothesis is explicitly confirmed, refuted, or marked "inconclusive — exploratory" in the manuscript
- Data reproducibility —
output/data-analysis/hasrequirements.txtorenvironment.yml; a README says "runpython main.pyto reproduce"; seeds are fixed - Data archive — raw datasets in
input/data/are licensed; derivatives inoutput/data-analysis/results/are documented - Synthesis stable — all
knowledge/synthesis/*.mdreferenced by the manuscript havestatus: stable - AI-use disclosed — the manuscript (or its front matter / supplement) carries an AI-use statement in the form the target venue requires, drafted from the project's own records (see AI-Use Disclosure) and confirmed by the user
- Log closing entry in
knowledge/_meta/log.md:
- YYYY-MM-DD · finish · <slug> · output=<path>
- Publication archive (DOI) — offer to deposit on Zenodo (or institution repository); update the log with DOI
- Decision: submission / follow-up — journal / publisher / conference? grant renewal?
- If follow-up grant: route to
grant-finder - If done done: commit everything (
git add . && git commit -m "finish: <slug>"), tag the release
Process Flow
digraph finishing {
"Render check" [shape=box];
"Wiki lint" [shape=box];
"BibTeX consistency" [shape=box];
"Peer review archived" [shape=box];
"Hypothesis resolution" [shape=box];
"Data reproducibility" [shape=box];
"Data archive" [shape=box];
"Synthesis stable" [shape=box];
"AI-use disclosed" [shape=box];
"Any check fail?" [shape=diamond];
"Fix and re-check" [shape=box];
"Log closing entry" [shape=box];
"DOI / archive publication" [shape=box];
"Follow-up grant?" [shape=diamond];
"Invoke grant-finder" [shape=box];
"Commit & tag" [shape=box];
"Done" [shape=doublecircle];
"Render check" -> "Wiki lint";
"Wiki lint" -> "BibTeX consistency";
"BibTeX consistency" -> "Peer review archived";
"Peer review archived" -> "Hypothesis resolution";
"Hypothesis resolution" -> "Data reproducibility";
"Data reproducibility" -> "Data archive";
"Data archive" -> "Synthesis stable";
"Synthesis stable" -> "AI-use disclosed";
"AI-use disclosed" -> "Any check fail?";
"Any check fail?" -> "Fix and re-check" [label="yes"];
"Fix and re-check" -> "Render check";
"Any check fail?" -> "Log closing entry" [label="no"];
"Log closing entry" -> "DOI / archive publication";
"DOI / archive publication" -> "Follow-up grant?";
"Follow-up grant?" -> "Invoke grant-finder" [label="yes"];
"Follow-up grant?" -> "Commit & tag" [label="no"];
"Invoke grant-finder" -> "Commit & tag";
"Commit & tag" -> "Done";
}
AI-Use Disclosure
Authorship stays with the humans: an AI system cannot be an author, because authorship presupposes accountability (DFG statement on generative models, 2023). What good scientific practice asks for instead is transparency proportionate to the use — which tools did which kinds of work, and that the authors checked the result and carry responsibility for it (Buck 2026, ch. 3.4). A full prompt log is not the standard: in a workflow where the model touches many steps, single prompts are no longer attributable to single passages, and the venue rarely asks for them.
Binding rules come first. Read the ## AI-Use Rules section of
input/ideas/<slug>-design.md (recorded during brainstorming-research). If it
is missing, ask the user once: which publisher / journal / university / funder
rules apply, and which form do they require? Their rules override this template.
Draft from the record, not from memory. The project already documents what the model did:
knowledge/_meta/log.md— every ingest, synthesis, draft, review pass, with date- frontmatter
author: human | llm | mixedon wiki pages, andbased_on:on substitute sources output/<target>/outline/*.md— which sections went through the drafting stagesoutput/<target>/reviews/— the AI review passes and the user's decisions on themknowledge/_meta/gate-overrides.log— where a gate was skipped (e.g. a straight-run draft)
Summarise by task, not by prompt: literature search, source acquisition, source extraction (ingest), synthesis, drafting, internal review, language editing. Name the model(s) and the host (Claude Code / OpenCode, provider). State what the humans did: chose the question and the thesis, read the sources the argument rests on, approved each argument and section, revised the prose.
Pick the form the venue wants — default to (a) if nothing is specified:
(a) Statement in the manuscript (acknowledgements, a footnote, or a section before the references):
## Use of AI tools
In preparing this <article / chapter / book>, <model, e.g. Claude Opus 5.5>
was used via <host> for: <literature search in <databases>>; <extracting
claims from sources into a project wiki, with page references>; <drafting
sections from an outline whose thesis and argument the author set and
approved section by section>; <internal review of the draft>. All sources
cited were checked against the original publications. The author(s)
reviewed and revised all AI-assisted content and take full responsibility
for the text.
(b) Tool overview page at the front of a thesis / dissertation: a table task → tool/model → purpose → how the output was checked.
(c) AI Usage Card (Wahle et al. 2023) as an appendix — a semi-standardised questionnaire; offer it for dissertations and where the institution asks for detailed documentation.
Present the draft, let the user correct it, and write the final text where the venue expects it. Do not cite the model as a source in the references — AI output is cited only where it is itself the object of study.
Reproducibility Statement Template
Drop into the manuscript (or supplementary material):
## Reproducibility
All analyses are reproducible from `output/data-analysis/`:
- **Code:** <files>
- **Data inputs:** `input/data/<files>` (licenses: <list>)
- **Environment:** Python <version>, see `output/data-analysis/requirements.txt`
- **Entry point:** `python output/data-analysis/main.py`
- **Random seed:** <fixed value>
- **Repository:** <git URL or Zenodo DOI>
Archive / DOI
Options:
- Zenodo — free, accepts datasets + code + manuscripts; gives DOI immediately
- Institutional repository — university OA repository
- GitHub Release + Zenodo-GitHub integration — tag release, Zenodo creates DOI automatically
Pick one with user, update log entry with DOI.
Submission Handoff
If submission targeted:
- Identify journal / publisher / conference CfP
- Check author guidelines — may require format conversion (
quarto render --to docx/--to latex, or pandoc) - Produce cover letter draft
- Confirm corresponding author + ORCID
- Do NOT submit on the user's behalf — prepare and hand over
Red Flags
| Thought | Reality |
|---|---|
| "Wiki-lint is just a detail, I'll skip it" | Broken wikilinks are the #1 reviewer feedback point. |
| "The hypothesis was wrong, I'll just reword it" | Pre-registration principle: document honestly. The result is what it is. |
| "I'll do the Zenodo DOI later" | Later = never. Now, or explicitly into the log. |
| "Follow-up grants are separate projects" | Now is the best moment — the story is fresh in your head. |
| "It's just a working paper, not a publication" | Even unpublished work must be reproducibly archived. |
| "AI use is obvious from the workflow, no need to state it" | Readers and examiners cannot see the workflow. Undisclosed AI-generated text is a breach of good scientific practice, and most venues now require a statement. |
| "I'll attach the full prompt history to be safe" | Not attributable in a multi-step workflow and rarely required. Disclose by task, in the form the venue asks for. |
Key Principles
- The checklist is the closure — not "feels done"
- Hypothesis honesty — what was predicted, what came out, what's open
- Reproducibility — manuscript AND data AND code AND environment
- AI use is disclosed, authorship is not shared — proportionate, task-level transparency; the humans are the authors and carry the responsibility
- DOI before submission — an archived version exists before the publisher process
- Log entry is the final artefact — the project is closed in the log
示例提示词
我的手稿已通过评审,帮我跑一遍结项清单检查渲染、数据和归档。
所属插件
安装该插件会一并获得同领域的 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.
- 形式逻辑自动推理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.
- 历史文献OCR识别Transcribes printed and handwritten historical documents with Tesseract/Kraken OCR, confidence filtering, spell correction. Use for digitizing scanned historical text.
常见问题
研究项目结项清单能做什么?
Runs the final completion checklist: rendering, bibliography, wiki, data, reproducibility, archiving. Use when a manuscript is finalized and ready to publish。
如何安装研究项目结项清单?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「研究项目结项清单」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
研究项目结项清单需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
研究项目结项清单经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。