ma-end-to-end

Automate end-to-end meta-analysis orchestration from TOPIC.txt to manuscript and reviewer responses.

115|45|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/htlin222/meta-pipe --skill ma-end-to-end
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ma-end-to-end
Source: https://github.com/htlin222/meta-pipe/tree/main/ma-end-to-end
Command: npx skills add https://github.com/htlin222/meta-pipe --skill ma-end-to-end

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bibtexparser, and includes scripts (resource) and references (resource) components.

What problem does it solve?

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.

Core Features & Use Cases

  • End-to-end orchestration of the 9-stage meta-analysis pipeline from TOPIC.txt to final manuscript.
  • Project scaffolding and standard directory layout to ensure consistency across analyses.
  • Topic-driven automation that tracks progress and outputs manuscript-ready results and reviewer notes.

Quick Start

Create a project with TOPIC.txt at the root and ask Claude to start the end-to-end meta-analysis workflow.

Frequently Asked Questions about ma-end-to-end

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate a reproducible meta-analysis workflow from topic to manuscript?

You can automate a reproducible meta-analysis workflow by creating a project with a TOPIC.txt file at the root. This orchestrates the 9-stage pipeline from protocol creation and screening to manuscript rendering and reviewer responses.

What is the best way to manage a full meta-analysis project directory layout?

Managing a full meta-analysis project requires standard directory scaffolding to ensure consistency. This pipeline coordinates a numbered project structure that predictably outputs standardized artifacts and tracks progress transparently.

Does the end-to-end meta-analysis pipeline work with both Python and R tooling?

Yes, the end-to-end meta-analysis pipeline enables both Python and R tooling. It coordinates the environment to run statistical analysis and data extraction while relying on the bibtexparser dependency for references.

Can I generate reviewer responses automatically after finishing a meta-analysis?

Yes, you can generate reviewer responses automatically. The workflow orchestrates the pipeline past manuscript rendering to produce final reviewer notes and inquiries, ensuring a complete end-to-end production-grade output.

Do I need a specific file format to start the meta-analysis automation process?

You need a TOPIC.txt file at the project root to start the meta-analysis automation process. This topic-driven approach triggers the full workflow, moving from protocol creation through searches to the final paper.

What are the limitations of using a single workflow for meta-analysis project management?

The pipeline is limited to its defined 9-stage structure and standardized directory layout. Users needing custom workflow stages or non-standard artifact formats may find the predictable directory constraints too rigid for alternative project management approaches.