科研 Skill
研究项目模板初始化
scaffold-research-project
Creates a new research project folder from a template via guided conversation on name, methodology, and languages. Use when starting a project without manual copying.
SKILL.md
Scaffold a Research Project
Create a new research project from the research-project-template without leaving the chat. Designed for users on Cowork (no terminal) and for Claude Code users who prefer a guided setup.
Announce at start: "Using scaffold-research-project to set up <project_name> at <parent_directory>."
When to use
- User says "start a new research project", "scaffold a project on X", "create a new project", "set up a research project about Y"
- User on Cowork (no shell) or anyone who prefers a guided setup over
cp -rand manual frontmatter editing - First-time users who haven't seen the template structure yet
NOT for: modifying an existing project (edit CLAUDE.md directly), copying parts of the template in isolation (use the relevant skill — e.g. ingest-source will create the wiki structure on demand).
Checklist
Create a task-list item for each. Complete in order; do not write files until all inputs are collected and confirmed.
-
Ask for project name. Require kebab-case (lowercase, hyphens, no spaces). Reject
MyProjectormy project— request a slug likeiron-age-chronologyornegev-fortresses-debate. Validate against the regex^[a-z][a-z0-9-]*$. -
Ask for parent directory. Offer
~/Documentsas default (expand via the Bash tool if available). If Bash is not available, ask the user to paste an absolute path. Verify the directory exists; if not, ask whether to create it. -
Ask for methodology. Present the three options briefly:
hermeneutic— default. Theology, exegesis, source criticism, interpretive archaeology. No frozen hypothesis; the plan documents research question + method sketch + expected sources.quantitative— geostatistics, 14C Bayesian, quantitative DH. Full pre-registration (hypothesis, operationalisation, stop criterion).mixed— per-sub-study; quantitative tasks opt into pre-registration individually. If the user is unsure, recommendhermeneuticand note that they can change it later.
-
Ask for discipline. Free text. Offer examples:
"Biblical Archaeology","Theology / Old Testament","Ancient History","Digital Humanities". The string is used in the project's CLAUDE.md frontmatter. -
Ask for languages. Default
[en]. Offer[de, en]for German-speaking research. Other ISO 639-1 codes welcome. -
Confirm the plan with the user. Present a single block:
"I'll create
<parent_directory>/<project_name>/with methodology<methodology>, discipline<discipline>, languages<languages>. Proceed?" Wait for explicit confirmation. Do not write any files before confirmation. -
Locate the template. Try, in order:
- Plugin root:
${CLAUDE_PLUGIN_ROOT:-$RESEARCH_SUPERPOWERS_DIR}/templates/research-project-template/(Claude Code setsCLAUDE_PLUGIN_ROOT, the OpenCode plugin setsRESEARCH_SUPERPOWERS_DIR). Failing that, the Claude Code plugin cache:~/.claude/plugins/cache/<marketplace>/research-superpowers/templates/research-project-template/. Use Bashlsto confirm if Bash is available; otherwise try common marketplace names (leiverkus-research,claude-plugins-community). - User-supplied path: if the user has the plugin checked out as a development clone, ask for the path.
- Fallback: fetch each template file from GitHub raw URLs (
https://raw.githubusercontent.com/leiverkus/research-superpowers/main/templates/research-project-template/...) via theWebFetchtool. Slower but works without any local clone.
- Plugin root:
-
Copy the template tree file-by-file using
Read(from the located template path) andWrite(to the new project path). Preserve directory structure exactly. Copy these top-level entries:CLAUDE.mdREADME.md.vscode/settings.jsonand.vscode/tasks.json.gitignore.gitlab-ci.ymlschema/knowledge-frontmatter.schema.jsonscripts/library.py— resolves the shared source library. Without it nothing can find a PDF.scripts/bib-subset.py— writesoutput/bibtex/references.bibas the cited subset of the libraryscripts/bib-search.py— page-level full-text search across the library (SQLite FTS5; the index is a local cache, never in the synced folder)scripts/check-pdf-version.py— flags manuscript-vs-published PDFs before ingestscripts/add-to-library.py— adds one PDF directly to the shared master library (theadd-to-libraryskill drives it)scripts/lint-wiki.pyscripts/wiki-to-graph.pyscripts/graph_mcp.py— stdlib MCP server exposing the graph queriesscripts/vendor/cytoscape.min.js(+scripts/vendor/README.md) — bundled offline lib for the HTML graph viz.mcp.json— registers thewiki-graphMCP server for Claude Codeinput/(with itsbibliography/,data/,description/,ideas/,notes/subdirectories — thedescription/project-description.mdtemplate file goes too)knowledge/(plain Markdown wiki —_meta/, the four_example-*.mdfiles inentities/,concepts/,sources/,synthesis/, plus an emptyassets/and_meta/log.md,_meta/index.md; no_quarto.ymlorMakefile— the wiki has no build step)output/(bibtex/references.bib,bibtex/csl/,article/article.qmd,book/_quarto.ymland chapters,presentation/talk.qmd, plus their Makefiles; and the emptyarticle/outline/+book/outline/dirs wheredrafting-manuscriptkeeps each manuscript's argument architecture — not rendered, never listed in_quarto.yml)
-
Patch CLAUDE.md frontmatter with the user's answers. Read the new
CLAUDE.md, replace the placeholder frontmatter block at the top:--- methodology: <user-answer> discipline: "<user-answer>" languages: <user-answer> plugin_version: "<version from .claude-plugin/plugin.json>" ---Use the Edit tool with the original placeholder block as
old_string.plugin_versionis not a user answer — read it from${CLAUDE_PLUGIN_ROOT:-$RESEARCH_SUPERPOWERS_DIR}/.claude-plugin/plugin.jsonand copy theversionstring verbatim. It records which plugin version this project's copiedschema/andscripts/came from, and it is what letsscripts/sync-project.pytell an old copy from a local patch later. Leaving it at0.0.0is not fatal — the project is then simply treated as behind — but it costs the user a false "local edit" warning on every file they never touched. -
Point the project at the shared library. Source PDFs do not live in the project — they live in one shared folder (
<library>/pdf/<bibkey>.pdf), so the same paper exists once across every project. Write its path into.research-library(one line, no trailing slash). Without this the project has no sources:ingest-sourcewill hard-stop on the very first ingest.- If
~/.config/research-superpowers/libraryalready exists, offer its contents as the default — most users have one library for everything. - Otherwise ask: "Where is your shared source library? (e.g.
~/UOLcloud/Bibliothek). Leave blank to set it later." - The file is gitignored — the path is machine-local and differs between machines, so committing it would break every other checkout.
- If
-
Optionally init git. If the Bash tool is available, ask: "Initialise a git repository here? (recommended; lets you track changes and roll back.)" If yes, run:
cd <parent_directory>/<project_name> git init -b main git add . git commit -m "Scaffold research project from research-superpowers template"If Bash is not available or the user declines, skip — note that git can be initialised later.
-
Register the project and audit its join keys. Append the new project's absolute path to
~/.config/research-superpowers/projects(one path per line; create the file if missing — the session-start drift check also auto-registers, but only once a session starts in the project). If the registry now lists ≥ 2 projects, runpython scripts/wiki-global-graph.py bibkeys <all registry roots>— a new project is exactly when its own doc says to run the audit, because no single project's CI can see a cross-project COLLISION or SPLIT. -
Confirm completion. Tell the user:
"Project created at
<parent_directory>/<project_name>/. Next steps:- Open
CLAUDE.mdto see the project's conventions - Point the project at the shared library (one line in
.research-library), then say 'ingest ' to populate the wiki - For the full walkthrough, see the plugin's
docs/tutorial.md"
- Open
Process Flow
digraph scaffold {
"Ask project name" [shape=box];
"Valid kebab-case?" [shape=diamond];
"Ask parent directory" [shape=box];
"Ask methodology" [shape=box];
"Ask discipline" [shape=box];
"Ask languages" [shape=box];
"Confirm plan" [shape=box];
"User confirms?" [shape=diamond];
"Locate template" [shape=box];
"Template found?" [shape=diamond];
"Fallback to WebFetch" [shape=box];
"Copy files via Read+Write" [shape=box];
"Patch CLAUDE.md frontmatter" [shape=box];
"Bash available?" [shape=diamond];
"Offer git init" [shape=box];
"User wants git?" [shape=diamond];
"git init + commit" [shape=box];
"Confirm + next steps" [shape=doublecircle];
"Ask project name" -> "Valid kebab-case?";
"Valid kebab-case?" -> "Ask project name" [label="no, retry"];
"Valid kebab-case?" -> "Ask parent directory" [label="yes"];
"Ask parent directory" -> "Ask methodology";
"Ask methodology" -> "Ask discipline";
"Ask discipline" -> "Ask languages";
"Ask languages" -> "Confirm plan";
"Confirm plan" -> "User confirms?";
"User confirms?" -> "Ask project name" [label="no, restart"];
"User confirms?" -> "Locate template" [label="yes"];
"Locate template" -> "Template found?";
"Template found?" -> "Fallback to WebFetch" [label="no"];
"Fallback to WebFetch" -> "Copy files via Read+Write";
"Template found?" -> "Copy files via Read+Write" [label="yes"];
"Copy files via Read+Write" -> "Patch CLAUDE.md frontmatter";
"Patch CLAUDE.md frontmatter" -> "Bash available?";
"Bash available?" -> "Offer git init" [label="yes"];
"Bash available?" -> "Confirm + next steps" [label="no"];
"Offer git init" -> "User wants git?";
"User wants git?" -> "git init + commit" [label="yes"];
"User wants git?" -> "Confirm + next steps" [label="no"];
"git init + commit" -> "Confirm + next steps";
}
Red Flags
| Thought | Reality |
|---|---|
| "I'll skip the methodology question and default to hermeneutic" | No — ask explicitly. Methodology drives writing-research-plan and executing-research-plan behaviour; assuming wrong wastes the user's time later. |
"I can just cp -r the template" | Not in Cowork (no Bash). The Read+Write approach works everywhere. |
| "Partial copy is fine, the user can fix it" | No — failed mid-copy leaves a confusing half-state. Either complete or roll back. |
| "I'll write files before the user confirms" | No — explicit confirmation is the gate between Q&A and disk writes. |
Key Principles
- Ask everything first, then write — atomic-feeling. The user types answers, sees the plan, confirms once, then files appear.
- No bash in the core path — only optional git init uses Bash. The scaffold itself works in any tool environment.
- Template lookup is graceful — plugin cache → user clone → GitHub fetch. Don't fail because the cache path varies.
- Frontmatter is patched, not regenerated — preserves the rest of the template's CLAUDE.md (architecture docs, workflow conventions).
- Git is optional — recommend it, never require it. A research project without git still works.
- One project per invocation — never batch.
示例提示词
帮我按模板新建一个数字人文研究项目并配置好项目目录和语言设置。
所属插件
安装该插件会一并获得同领域的 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.
常见问题
研究项目模板初始化能做什么?
Creates a new research project folder from a template via guided conversation on name, methodology, and languages. Use when starting a project without manual copying。
如何安装研究项目模板初始化?
在科搭 Codar 左侧点击「插件」,在「组件」页签搜索「研究项目模板初始化」并安装;在 Claude Code 或 Codex 中可以发送本页的安装提示词,或下载 Skill 包后解压到 ~/.claude/skills 或 ~/.codex/skills。
研究项目模板初始化需要哪些权限?
该科研 Skill没有声明额外权限;执行具体操作时仍由 Agent 按自身规则请求确认。
研究项目模板初始化经过官方审核吗?
是。SpeedSkills 收录的每个版本都会记录内容摘要与权限声明,当前版本已通过安全审核。