菜单
Intake a meta-analysis topic from TOPIC.txt, translate it into a PICO or PECO protocol, and define eligibility, outcomes, and search scope. Use when starting a new meta-analysis project or refining a research question.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Define extraction schema, extract study data from full texts, and store it in a structured database for meta-analysis. Use when moving from full-text collection to statistical analysis.
End-to-end AI-assisted meta-analysis pipeline orchestration from TOPIC.txt to final manuscript and reviewer responses. Use when the user provides a topic and wants the full meta-analysis workflow, tracking, and final paper.
Orchestrate agent team for meta-analysis pipeline. Creates team, spawns teammates, manages task list and handoffs between pipeline stages.
Collect and manage full-text PDFs for included studies, track provenance, and prepare documents for extraction. Use when moving from screening to data extraction.
Conduct literature searches for meta-analysis using Python with uv, query PubMed and other databases, deduplicate results, and store round-based bibliographies with notes. Use when building or updating the evidence corpus.
Draft and render a meta-analysis manuscript with Quarto using an IMRaD structure and embedded figures/tables. Use when preparing the final paper from analysis outputs.
| name | ma-topic-intake |
| description | Intake a meta-analysis topic from TOPIC.txt, translate it into a PICO or PECO protocol, and define eligibility, outcomes, and search scope. Use when starting a new meta-analysis project or refining a research question. |
Turn the raw topic into a formal protocol and a search-ready research question.
TOPIC.txt01_protocol/pico.yaml (includes analysis_type.preliminary: pairwise or nma_candidate)01_protocol/eligibility.md01_protocol/outcomes.md01_protocol/search-plan.md01_protocol/decision-log.md01_protocol/analysis-type-decision.md (Stage 1 filled)TOPIC.txt and restate the question in PICO or PECO form.01_protocol/pico.yaml (L10-14: outcomes.primary/secondary fields)01_protocol/outcomes.md
2b. Preliminary analysis type assessment (provisional — confirmed after screening):analysis_type.preliminary: nma_candidate in pico.yaml (L22: analysis_type.preliminary field)analysis_type.preliminary: pairwise in pico.yaml (L22: analysis_type.preliminary field)01_protocol/decision-log.mdreferences/analysis-type-decision-template.md → 01_protocol/analysis-type-decision.md and fill Stage 1nma_candidate is NOT confirmed NMA — it requires a confirmation gate after screening (see /ma-screening-quality step 8)01_protocol/pico.yaml (L18-20: study_types.include/exclude fields)01_protocol/eligibility.md01_protocol/search-plan.md01_protocol/decision-log.mdreferences/pico-template.yaml provides a structured PICO scaffold.references/analysis-type-decision-template.md documents the two-stage NMA vs Pairwise decision.01_protocol/decision-log.md.| Step | Skill | Stage |
|---|---|---|
| Prev | /brainstorm-topic | Pre-pipeline topic development |
| Next | /ma-search-bibliography | 02 Search & Bibliography |
| All | /ma-end-to-end | Full pipeline orchestration |