Agent skill

Methods Reverse Engineer

by aipoch in aipoch/medical-research-skills

Reverse-engineers the methods section of a biomedical paper into a structured, reproducible workflow.

MITAuto-check passedResearch & Science

Install Methods Reverse Engineer

skills CLI
$ npx skills add aipoch/medical-research-skills --skill methods-reverse-engineer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aipoch/medical-research-skills methods-reverse-engineer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aipoch/medical-research-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/'awesome-med-research-skills/Evidence Insight/methods-reverse-engineer' .claude/skills/methods-reverse-engineer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
methods-reverse-engineer
GitHub stars
2k
Token cost
~4k tokens
SKILL.md length
1,819 words
Files
13 (incl. references)
Skills in repo
567
Repo updated
First seen
Licence
MIT

At a glance

Reverse-engineers the methods section of a biomedical paper into a structured, reproducible workflow.

  • Works in 10 steps: Determine Input Coverage and… → Identify the Underlying Study Design… → Extract the Study Objective and Primary… → …
  • A user wants to understand how a study was actually executed
  • SKILL.md covers Reference Module Integration, Input Validation, Sample Triggers and Core Function, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Methods Reverse Engineer is an agent skill from aipoch/medical-research-skills. 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…

Its SKILL.md is about 4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including reference files (for example `eval_report_methods-reverse-engineer_result.json`, `references/analysis-pipeline-reconstruction-rules.md` and `references/data-and-sample-extraction-rules.md`).

It sits in Research & Science, covering Summarization, Reproducible research and Database administration. The repository describes itself as: Hundreds of agent skills for medical research, including protocol design, data analysis, evidence insights, and academic writing. The licence is MIT.

When your agent uses it

  • A user wants to understand how a study was actually executed
  • Extract data sources
  • Inclusion/exclusion logic
  • Analytical sequence

Example prompts

  • “/methods-reverse-engineer”

Workflow steps

10 steps, taken from the step headings in SKILL.md.

  1. Determine Input Coverage and Reconstruction Depth
  2. Identify the Underlying Study Design Family
  3. Extract the Study Objective and Primary Comparison Logic
  4. Reconstruct Data / Sample Acquisition and Eligibility Logic
  5. Reconstruct the Operational Pipeline in Order
  6. Extract Tools, Software, Assays, and Parameter-Critical Details
  7. Reconstruct Quality Control and Validation Logic
  8. Build the Replication Checklist
  9. Audit Reproducibility Gaps and Hidden Assumptions
  10. State Reproduction Readiness

What it can do on your machine

Read from SKILL.md and the folder at commit 686e09d. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Methods Reverse Engineer loads about 4k tokens when it runs, and up to ~5.6k if it reads all its reference files. Until then it costs about 202 tokens; SKILL.md has 1,819 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~202
When it runs · the whole SKILL.md, loaded when a task matches
~4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aipoch/medical-research-skills at commit 686e09d, republished under its MIT licence (© aipoch). 1,819 words, ~3,990 tokens.

Download SKILL.mdSave it as .claude/skills/methods-reverse-engineer/SKILL.md (or your agent's skills folder). This skill also uses 12 other files; get the full folder from GitHub.
name
methods-reverse-engineer
description
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.
license
MIT
author
AIPOCH

Source: 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
Show full SKILL.md (718 more words)Show less
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.

© aipoch, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 12 other files (references) in awesome-med-research-skills/Evidence Insight/methods-reverse-engineer of aipoch/medical-research-skills.

  • SKILL.md
  • eval_report_methods-reverse-engineer_result.json
  • references/analysis-pipeline-reconstruction-rules.md
  • references/data-and-sample-extraction-rules.md
  • references/input-coverage-and-boundary-rules.md
  • references/literature-integrity-rules.md
  • references/methods-decomposition-framework.md
  • references/output-section-guidance.md
  • references/reproducibility-gap-rules.md
  • references/software-parameter-and-environment-rules.md
  • references/study-design-routing-rules.md
  • references/validation-and-quality-control-rules.md
  • references/workflow-step-template.md

Open the folder on GitHubat commit 686e09d

Compare with similar skills

Methods Reverse Engineer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Methods Reverse Engineer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Methods Reverse Engineer this skillaipoch/medical-research-skills2k—~4kAutomated safety check: PassMIT
Audit Replicationbrycewang-stanford/Auto-Empirical-Research-Skills4.5k—~984Automated safety check: NotesCustom licence
Ectheory Replication And Data Policyfranklee16/academic-research-skills2231 repos~983Automated safety check: PassNone
Qe Replication And Data Policyfranklee16/academic-research-skills2231 repos~1.2kAutomated safety check: PassNone
Rss Reproducibilitybrycewang-stanford/Awesome-Journal-Skills1.2k—~1.5kAutomated safety check: PassMIT
Audit Reproducibilitypedrohcgs/claude-code-my-workflow1.6k—~6.4kAutomated safety check: NotesMIT

Similar skills

  • Audit Replication

    brycewang-stanford/Auto-Empirical-Research-Skills

    Validate the replication package for the sewage-house-prices project.

    4.5k GitHub stars~984 tokensUpdated 2 days ago
    Research & ScienceAuto-check: notes
  • Ectheory Replication And Data Policy

    franklee16/academic-research-skills

    A skill your agent uses to handle reproducibility and the supplementary-material file for an Econometric Theory (ET) paper — ET has no mandatory data/code archive (theory journal); the relevant…

    223 GitHub starsUsed in 1 repo~983 tokens
    Research & ScienceAuto-check passed
  • Qe Replication And Data Policy

    franklee16/academic-research-skills

    A skill your agent uses to assemble a Quantitative Economics (QE) replication package that passes the Econometric Society Data Editor's pre-acceptance reproducibility check — raw data, code…

    223 GitHub starsUsed in 1 repo~1.2k tokens
    Research & ScienceAuto-check passed
  • Rss Reproducibility

    brycewang-stanford/Awesome-Journal-Skills

    A skill your agent uses when strengthening the reproducibility of an RSS (Robotics: Science and Systems) paper whose evidence lives partly on hardware — platform disclosure ledgers, log-backed trial…

    1.2k GitHub stars~1.5k tokensUpdated 10 days ago
    Research & ScienceAuto-check passed
  • Audit Reproducibility

    pedrohcgs/claude-code-my-workflow

    Enforce the replication-protocol.md rule by cross-checking numeric claims in a manuscript against the actual R / Stata / Python outputs.

    1.6k GitHub stars~6.4k tokensUpdated 10 days ago
    Research & ScienceAuto-check: notes
  • Apsr Transparency And Data Policy

    franklee16/academic-research-skills

    A skill your agent uses when preparing the reproducibility / replication materials for an American Political Science Review (APSR) manuscript.

    223 GitHub starsUsed in 1 repo~1.1k tokens
    DatabasesAuto-check passed

More from aipoch/medical-research-skills

All 567 skills in this repo
  • Academic Poster Generator

    aipoch/medical-research-skills

    Complete workflow for generating academic research posters from PDF literature; use when you need to extract paper content from PDFs and produce a LaTeX-based poster…

    2k GitHub stars~2.2k tokensUpdated 20 days ago
    Auto-check passed
  • Diagnostic Study Quality Assessment Quadas

    aipoch/medical-research-skills

    Analyzes clinical diagnostic accuracy studies for bias using the QUADAS-2 tool.

    2k GitHub stars~1.4k tokensUpdated 20 days ago
    Auto-check passed
  • Exploratory Data Analysis

    aipoch/medical-research-skills

    Perform comprehensive exploratory data analysis on scientific data files across 200+ file formats.

    2k GitHub stars~3.7k tokensUpdated 20 days ago
    Auto-check passed
  • Iso Certification

    aipoch/medical-research-skills

    A toolkit for preparing ISO 13485:2016 certification documentation for medical device QMS.

    2k GitHub stars~1.8k tokensUpdated 20 days ago
    Auto-check passed
  • Journal Skills

    aipoch/medical-research-skills

    Recommends target journals for manuscript submission by analyzing the paper topic/abstract and the journal distribution of similar PubMed literature; use when users ask for journal…

    2k GitHub stars~1.7k tokensUpdated 20 days ago
    Auto-check passed
  • Latex Posters

    aipoch/medical-research-skills

    Creates academic-poster writing packages for LaTeX using beamerposter, tikzposter, or baposter.

    2k GitHub stars~1.3k tokensUpdated 20 days ago
    Auto-check passed

Questions about Methods Reverse Engineer

What does Methods Reverse Engineer do?

Reverse-engineers the methods section of a biomedical paper into a structured, reproducible workflow. Methods Reverse Engineer is an agent skill from aipoch/medical-research-skills. Reverse-engineers the methods section of a biomedical paper into a structured, reproducible workflow.

When should I use Methods Reverse Engineer?

Methods Reverse Engineer fits situations like: A user wants to understand how a study was actually executed; extract data sources; inclusion/exclusion logic; analytical sequence.

How do I install Methods Reverse Engineer in Claude Code?

Run `npx skills add aipoch/medical-research-skills --skill methods-reverse-engineer -a claude-code`. Or copy the skill folder (awesome-med-research-skills/Evidence Insight/methods-reverse-engineer in aipoch/medical-research-skills) into .claude/skills/methods-reverse-engineer in your project. Claude Code loads it when a task matches its description.

How do I install Methods Reverse Engineer in Codex?

Run `npx skills add aipoch/medical-research-skills --skill methods-reverse-engineer -a codex`. Or copy the skill folder (awesome-med-research-skills/Evidence Insight/methods-reverse-engineer in aipoch/medical-research-skills) into .agents/skills/methods-reverse-engineer in your project. Codex loads it when a task matches its description.

Can I use Methods Reverse Engineer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aipoch/medical-research-skills --skill methods-reverse-engineer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/methods-reverse-engineer, .gemini/skills/methods-reverse-engineer, .github/skills/methods-reverse-engineer and .opencode/skills/methods-reverse-engineer in your project.

What does Methods Reverse Engineer need to run?

SKILL.md names no scripts, command-line tools or credentials: Methods Reverse Engineer is instructions for the agent only.

Does Methods Reverse Engineer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Methods Reverse Engineer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Methods Reverse Engineer use?

Methods Reverse Engineer is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Methods Reverse Engineer use?

About 4k tokens (SKILL.md is roughly 16k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.6k tokens, read only when the agent opens those files.

What are the alternatives to Methods Reverse Engineer?

Skills that share tags, products or a category with Methods Reverse Engineer: Audit Replication (brycewang-stanford/Auto-Empirical-Research-Skills, 4.5k stars), Ectheory Replication And Data Policy (franklee16/academic-research-skills, 223 stars), Qe Replication And Data Policy (franklee16/academic-research-skills, 223 stars) and Rss Reproducibility (brycewang-stanford/Awesome-Journal-Skills, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Methods Reverse Engineer?

aipoch (a GitHub organization) maintains it in aipoch/medical-research-skills, which has 1,973 GitHub stars. The repository holds 567 skills in this directory. The repository was last updated on September 17, 2026.

Source: aipoch/medical-research-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.