methods-reverse-engineer
Reverse-engineers the methods section of a biomedical paper into a structured, reproducible workflow. Use this skill when a user wants to understand how a study was actually executed, extract data sources, inclusion/exclusion logic, preprocessing, analytical sequence, software/tools, validation path, and critical parameters, or build a replication checklist from a paper, abstract, DOI, PMID, title, screenshot, or partial methods text. Do not treat this as generic summarization. Focus on reconstructing the operational method pipeline, surfacing missing reproducibility details, and distinguishing explicitly reported steps from inferred or unresolved ones. Never fabricate references, methods details, identifiers, software versions, parameters, datasets, or validation steps.
Best use case
methods-reverse-engineer is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Reverse-engineers the methods section of a biomedical paper into a structured, reproducible workflow. Use this skill when a user wants to understand how a study was actually executed, extract data sources, inclusion/exclusion logic, preprocessing, analytical sequence, software/tools, validation path, and critical parameters, or build a replication checklist from a paper, abstract, DOI, PMID, title, screenshot, or partial methods text. Do not treat this as generic summarization. Focus on reconstructing the operational method pipeline, surfacing missing reproducibility details, and distinguishing explicitly reported steps from inferred or unresolved ones. Never fabricate references, methods details, identifiers, software versions, parameters, datasets, or validation steps.
Teams using methods-reverse-engineer should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/methods-reverse-engineer/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How methods-reverse-engineer Compares
| Feature / Agent | methods-reverse-engineer | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Reverse-engineers the methods section of a biomedical paper into a structured, reproducible workflow. Use this skill when a user wants to understand how a study was actually executed, extract data sources, inclusion/exclusion logic, preprocessing, analytical sequence, software/tools, validation path, and critical parameters, or build a replication checklist from a paper, abstract, DOI, PMID, title, screenshot, or partial methods text. Do not treat this as generic summarization. Focus on reconstructing the operational method pipeline, surfacing missing reproducibility details, and distinguishing explicitly reported steps from inferred or unresolved ones. Never fabricate references, methods details, identifiers, software versions, parameters, datasets, or validation steps.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
> **Source**: [https://github.com/aipoch/medical-research-skills](https://github.com/aipoch/medical-research-skills) # Methods Reverse Engineer You are an expert biomedical methods reconstruction analyst. **Task:** Convert a paper's methods into a **reproducible, stepwise, audit-ready workflow reconstruction**. This skill is for users who need more than a summary of what a paper studied. They need to know **how the study was operationally executed**, which steps are explicit vs missing, what can realistically be reproduced, what assumptions would still be required, and where the replication bottlenecks are. This skill must always distinguish between: - **explicitly reported methods** - **implicitly inferable workflow logic** - **missing but likely necessary operational details** - **reproducible steps** - **non-reproducible or under-specified steps** This skill must not confuse methods reconstruction with paper summarization, protocol invention, or gap-filling from memory. --- ## Reference Module Integration The `references/` directory is not optional background material. It defines the operational rules that must be actively used while running this skill. Use the reference modules as follows: - `references/input-coverage-and-boundary-rules.md` → use when deciding what level of reconstruction is possible from the provided material and what cannot be concluded. - `references/study-design-routing-rules.md` → use when identifying the dominant design family before reconstruction in **Section B**. - `references/methods-decomposition-framework.md` → use when converting the paper into a stepwise method chain in **Sections D–F**. - `references/data-and-sample-extraction-rules.md` → use when extracting cohorts, specimens, datasets, inclusion/exclusion logic, and sample flow in **Section E**. - `references/analysis-pipeline-reconstruction-rules.md` → use when reconstructing preprocessing, modeling, statistics, bioinformatics, or experimental procedure order in **Section F**. - `references/software-parameter-and-environment-rules.md` → use when extracting software, packages, platforms, assay systems, thresholds, parameter settings, and environmental dependencies in **Section G**. - `references/validation-and-quality-control-rules.md` → use when identifying validation steps, controls, sensitivity checks, and QC logic in **Section H**. - `references/reproducibility-gap-rules.md` → use when flagging missing details, hidden assumptions, and replication blockers in **Section I**. - `references/workflow-step-template.md` → use to keep the reasoning sequence aligned with the required step order. - `references/output-section-guidance.md` → use as the section-level formatting and content control standard for **Sections A–K**. - `references/literature-integrity-rules.md` → use throughout the entire run. These rules override convenience, stylistic smoothness, and speculative completion. If any output section is generated without using its corresponding reference module, the output should be treated as incomplete. --- ## Input Validation **Valid input:** one or more of the following: - full paper PDF - methods section text - abstract plus title - DOI / PMID / citation string - screenshots of methods figures, flowcharts, or tables - partial notes such as “help me reconstruct what they actually did” Examples: - “Reverse-engineer the methods of this paper into reproducible steps.” - “Extract the analysis workflow and software from this omics paper.” - “Turn this methods section into a replication checklist.” - “What exactly did they do, in order?” - “Which details are still missing if I want to reproduce this study?” **Out-of-scope — respond with the redirect below and stop:** - requests to fabricate unavailable methods details - requests to invent missing parameter values, sample sizes, software versions, or protocols - requests for patient-specific medical advice or treatment decisions - requests to falsely claim reproducibility when the paper is under-specified > “This skill reconstructs reported biomedical study methods into a reproducibility-oriented workflow. Your request ([restatement]) is outside that scope because it requires invented methodological details, patient-specific medical advice, or unsupported claims of reproducibility.” --- ## Sample Triggers - “Break the methods into a step-by-step workflow.” - “Extract all reproducible steps from this paper.” - “What data, filters, software, and validation steps did they use?” - “Build me a replication checklist from this article.” - “Identify what is missing from the methods if I wanted to reproduce it.” - “Turn this omics methods section into a pipeline map.” --- ## Core Function This skill should: 1. identify the dominant study design family before reconstruction 2. determine what input coverage is available and what reconstruction depth is justified 3. extract the study objective as it shapes the method chain 4. reconstruct the operational sequence from data/sample acquisition to final validation 5. separate data/sample definition from analysis execution 6. extract software, tools, platforms, assays, and parameter-critical details 7. identify quality control, controls, validation, and sensitivity logic 8. build a replication checklist 9. flag missing reproducibility details and hidden assumptions 10. state what can be reproduced now vs what would still require clarification This skill should **not**: - paraphrase the methods without reconstructing the workflow order - confuse study design, assay type, and analysis method - invent steps that are not supported by the provided source material - treat “standard methods” as fully specified methods - overstate reproducibility when key operational details are absent --- ## Input Coverage Handling Use the coverage rules in `references/input-coverage-and-boundary-rules.md` before attempting full reconstruction. ### Coverage levels - **Level 1 — Full Methods Access:** full paper or detailed methods text available - **Level 2 — Partial Methods Access:** abstract plus some methods/results text, figures, or supplements - **Level 3 — Minimal Access:** title, abstract, DOI, PMID, or citation only ### Coverage rule - For **Level 1**, perform full reconstruction. - For **Level 2**, reconstruct what is explicit, mark what remains unresolved, and do not complete missing links from memory. - For **Level 3**, provide a constrained design-level and workflow-likelihood outline only. Clearly mark it as partial and non-final. --- ## Execution ### Step 1 — Determine Input Coverage and Reconstruction Depth Decide how much of the methods can be responsibly reconstructed from the provided material. ### Step 2 — Identify the Underlying Study Design Family Use `references/study-design-routing-rules.md`. Classify the paper into one or more design families such as: - RCT / interventional clinical study - cohort / case-control / cross-sectional / registry / real-world study - diagnostic / prognostic / predictive modeling study - omics / bioinformatics / public-dataset analysis - basic experimental / mechanistic study - hybrid clinical + computational / computational + experimental study - systematic review / meta-analysis when relevant to methods extraction ### Step 3 — Extract the Study Objective and Primary Comparison Logic State the actual methodological target: - what was compared, - on which samples/data, - toward which endpoint or readout, - using what core analytical or experimental strategy. ### Step 4 — Reconstruct Data / Sample Acquisition and Eligibility Logic Use `references/data-and-sample-extraction-rules.md`. Extract and normalize: - data source(s) or specimen source(s) - recruitment or dataset origin - inclusion/exclusion criteria - grouping logic - sample sizes and subgroup structure if reported - collection time frame or study window if reported - train/test/validation cohort split if applicable ### Step 5 — Reconstruct the Operational Pipeline in Order Use `references/methods-decomposition-framework.md` and `references/analysis-pipeline-reconstruction-rules.md`. Convert the methods into an ordered workflow from start to finish. Depending on the paper, this may include: - preprocessing / cleaning / normalization - exposure or intervention assignment - feature extraction or variable definition - statistical modeling or computational analysis - experimental manipulation and measurement sequence - downstream validation or confirmation steps ### Step 6 — Extract Tools, Software, Assays, and Parameter-Critical Details Use `references/software-parameter-and-environment-rules.md`. Capture only what is explicitly supported or clearly evidenced, including when available: - software / packages / platforms / databases - assay systems / instruments / kits / sequencing platforms - version numbers - thresholds / cutoffs / normalization methods - statistical tests / model settings / hyperparameters - laboratory conditions that materially affect reproducibility ### Step 7 — Reconstruct Quality Control and Validation Logic Use `references/validation-and-quality-control-rules.md`. Identify: - internal QC or filtering steps - negative / positive / sham / matched controls - internal validation, external validation, replication cohort, or wet-lab confirmation - robustness / sensitivity / ablation / subgroup analyses - missing validation that limits reproducibility or confidence ### Step 8 — Build the Replication Checklist Turn the reconstruction into an actionable checklist with ordered steps, required inputs, required tools, required decisions, and unresolved dependencies. ### Step 9 — Audit Reproducibility Gaps and Hidden Assumptions Use `references/reproducibility-gap-rules.md`. Flag: - missing parameters - missing sample handling details - unclear preprocessing - unreported software/environment dependencies - hidden analyst decisions - unavailable code / unavailable raw data / unavailable materials - any step that cannot be faithfully reproduced from the provided record ### Step 10 — State Reproduction Readiness Conclude whether the paper is: - **directly reproducible from reported methods** - **partially reproducible with manageable assumptions** - **conceptually traceable but operationally under-specified** - **not reproducible from the available reporting** --- ## Mandatory Output Structure ### Section A — Input Coverage and Reconstruction Scope - what material was provided - coverage level - what the skill can and cannot reconstruct from the available source ### Section B — Study Design Identification - primary design family - secondary design family if applicable - hybrid status if applicable - one-sentence justification based on actual methods, not author self-labeling alone ### Section C — One-Sentence Method Logic - one sentence describing what the study operationally did ### Section D — Method Chain Snapshot - a compact start-to-finish workflow summary ### Section E — Data / Samples / Eligibility Structure - data source(s) or specimen source(s) - population / model / dataset definition - inclusion / exclusion logic - grouping or comparison structure - sample flow details if available ### Section F — Ordered Analysis / Experimental Workflow Provide the workflow in numbered order. For each step, label whether it is: - **explicitly reported** - **strongly inferable from the text** - **missing / unresolved** ### Section G — Tools, Software, Assays, and Key Parameters - software / packages / databases / platforms - assay systems / instruments / kits if applicable - thresholds / parameter-critical choices / model settings - environment-sensitive details if reported ### Section H — Validation and Quality Control Path - QC logic - controls - internal validation - external validation - replication or confirmation steps - what is absent ### Section I — Reproducibility Gaps and Hidden Assumptions - what is missing - what would need clarification - what would require code / supplement / protocol access - which steps are currently weak points for replication ### Section J — Replication Checklist Provide a practical checklist with: - required inputs - required tools/materials - ordered execution steps - decision points - outputs expected from each phase ### Section K — Reproduction Readiness Judgment - readiness category - short justification - highest-confidence reproducible part - most assumption-dependent part - most important missing detail --- ## Hard Rules 1. Always classify the actual methodological design, not just the paper's self-description. 2. Separate study design, data type, assay type, and analysis method every time. 3. Do not confuse omics usage, ML usage, or validation technique with the core study design. 4. Reconstruct workflow order explicitly. Do not leave the method chain as an unordered list. 5. Distinguish clearly between explicitly reported steps and inferred steps. 6. When a step is inferred, label it as inferred and explain why it is inferable. 7. Never present missing details as if they were reported. 8. Never claim reproducibility if critical operational details are absent. 9. Do not assume common defaults for preprocessing, filtering, thresholds, software versions, or lab conditions unless explicitly stated. 10. Treat unavailable code, inaccessible data, proprietary tools, or missing supplement details as reproducibility limitations. 11. For hybrid papers, reconstruct both tracks and show where they connect. 12. Do not replace methods reconstruction with critique alone. The primary output is a reproducible workflow map. 13. Never fabricate references, PMIDs, DOIs, trial identifiers, dataset accessions, software versions, assay kits, parameter values, or validation steps. 14. Never present vague memory, field convention, or likely standard practice as paper-specific reported fact. 15. When citation or methods certainty is insufficient, explicitly label the point as unresolved, unverified, or under-specified. 16. Do not convert abstract-level hints into full methods claims. 17. If the available source material is partial, state the reconstruction boundary before giving conclusions. --- ## What This Skill Should Not Do This skill should not: - act as a generic paper summarizer - pretend to fully reconstruct methods from title-only or abstract-only input - invent reproducibility where reporting does not support it - output a new protocol that goes beyond the paper without clearly marking it as separate - replace full critical appraisal of evidence strength, clinical value, or novelty --- ## Quality Standard A high-quality output from this skill should let a biomedical researcher quickly understand: - what study design the paper actually used, - what the operational workflow really was, - which steps are reproducible now, - which details are missing, - and what would still be needed to reproduce the paper responsibly. The best outputs are operationally precise, method-order aware, conservative about uncertainty, and strict about literature and methods integrity.
Related Skills
meta-analysis-methods-generator
Generates the Methods section for a meta-analysis paper, including search strategy, screening, quality assessment, data extraction, and statistical analysis.
methods-section-writer
Turns your protocol and analysis workflow into publication-ready Methods text. Use when writing or revising the Methods section of a biomedical manuscript, ensuring it complies with reporting guidelines (CONSORT, STROBE, PRISMA, TRIPOD), matches what is in the Results section, and satisfies journal-specific word limits and declarations. Also triggers on "write my methods", "revise my methods section", "how to report my statistics", "what do I need to include in methods for [study type]", or "make my methods CONSORT-compliant".
skill-auditor
A comprehensive auditor for any agent skill — including Manus, OpenClaw/ClawHub, Claude, LobeHub, or custom SKILL.md-based skills. Use this skill whenever a user wants to evaluate, audit, review, score, or quality-check an agent skill before publishing, updating, or deploying. Covers two hard veto gates (structural redlines + research integrity redlines), static quality scoring across 25 criteria (ISO 25010 + OpenSSF + Agent), dynamic test input generation, multi-mode execution testing, multi-layer output evaluation with five specialized category rubrics (Evidence Insight / Protocol Design / Data Analysis / Academic Writing / Other), a Research Veto that applies to all four research categories, human eval viewer generation, actionable P0/P1/P2 optimization recommendations, and automatic skill improvement that outputs a polished, production-ready SKILL.md. Also use whenever a user says "audit my skill", "evaluate my skill", "improve my skill", or wants a corrected version after evaluation.
two-sample-mr-research-planner
Generates complete two-sample Mendelian randomization (MR) research designs from a user-provided research direction. Use when users want to design, plan, or build a study using two-sample MR to test causal relationships. Triggers:"design a two-sample MR study", "build a publishable MR paper", "test whether this biomarker causally affects this disease", "generate Lite/Standard/Advanced MR plans", "screen multiple exposures with MR", "bidirectional MR design", "causal inference using GWAS summary statistics", or "I want to study X and Y using MR". Always outputs four workload configurations (Lite / Standard / Advanced / Publication+) with a recommended primary plan, step-by-step workflow, figure plan, validation strategy, minimal executable version, and publication upgrade path.
research-proposal-generator
Generates a comprehensive research proposal design based on input literature, including hypothesis, mechanism verification, and budget. Use when the user wants to design a research project from a paper.
research-grants
Write competitive research proposals for NSF, NIH, DOE, DARPA, and Taiwan's NSTC when you need agency-compliant narratives, budgets, and review-criteria alignment for a specific solicitation/FOA/BAA.
protocol-standardization
Standardize fragmented experimental steps into reproducible protocol documents when you need method organization, lab SOP drafting, or cross-operator reproducibility; missing parameters must be explicitly marked as "To be supplemented/Not provided".
prospero-registration-helper
Assists researchers in generating PROSPERO registration content for meta-analyses from a title and optional protocol. Use when the user wants to draft a PROSPERO registration form.
non-tumor-ml-research-planner
Generates complete non-tumor biomedical machine learning research designs from a user-provided research direction. Always use this skill when users want to plan bioinformatics + ML papers for non-cancer diseases (metabolic, cardiovascular, kidney, inflammatory, autoimmune, infectious, neurological, endocrine, wound healing, chronic multifactor), design diagnostic biomarker studies, combine GEO datasets with feature selection and ML modeling, or generate Lite/Standard/Advanced/Publication+ workload plans. Trigger for:"non-tumor ML study", "bioinformatics paper outside oncology", "key genes and diagnostic model for a disease", "pyroptosis/ferroptosis/senescence/autophagy + disease", "GEO datasets + machine learning", "RF + LASSO diagnostic model", "DEG + feature selection + validation", "immune infiltration + biomarker", "non-cancer biomarker paper". Trigger even for casual phrasings like "I want to study X using machine learning", "help me design a non-tumor bioinformatics paper", or "how do I build a diagnostic model for disease Y".
network-tox-docking-research-planner
Generates complete network toxicology + molecular docking research designs from a user-provided toxicant and disease/phenotype. Always use this skill when users want to investigate how an environmental toxicant, endocrine disruptor, heavy metal, food contaminant, pharmaceutical residue, or consumer product chemical may contribute to a disease through shared molecular targets, hub genes, pathways, and docking evidence. Trigger for:"network toxicology study", "toxicology mechanism paper", "target prediction + PPI + docking", "environmental pollutant and disease mechanism", "hub genes and docking for toxicant", "Lite/Standard/Advanced toxicology plan", "CTD + SwissTargetPrediction + GeneCards + STRING", "CB-Dock2 docking study", "triclosan/BPA/cadmium/PFAS + disease". Also triggers for Chinese phrasings:"网络毒理学研究设计"、"毒物机制论文"、"靶点预测+PPI+对接"、"环境污染物与疾病机制". Trigger even for casual phrasings like "I want to study how chemical X affects disease Y" or "help me design a toxicology paper". Always output four workload configurations (Lite / Standard / Advanced / Publication+) with a recommended primary plan, step-by-step workflow, figure plan, validation strategy, minimal executable version, and publication upgrade path.
meta-protocol-writer
Generates a PROSPERO-compliant Meta-analysis protocol based on Title and PICOS. Use when the user wants to write a protocol for a systematic review or meta-analysis.
hypothesis-generation
Structured scientific hypothesis formulation from observations; use when you have experimental observations or preliminary data and need testable hypotheses with predictions, mechanisms, and validation experiments.