agentsclimarketplace

Research methodology

Skill itallstartedwithaidea/agent-skills/skills/scientific-research/research-methodology

Research Methodology guides the agent through the complete scientific research lifecycle: hypothesis generation from literature gaps, experimental design with proper controls, systematic literature review, data collection protocols, and peer review preparation.From its SKILL.md

Install
npx -y skills add itallstartedwithaidea/agent-skills --skill research-methodology

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

6.5 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it

Research Methodology

Part of Agent Skills™ by googleadsagent.ai™

Description

Research Methodology guides the agent through the complete scientific research lifecycle: hypothesis generation from literature gaps, experimental design with proper controls, systematic literature review, data collection protocols, and peer review preparation. The agent functions as a research collaborator that enforces methodological rigor at every stage.

Weak methodology invalidates results regardless of how sophisticated the analysis is. This skill prevents common methodological failures: hypotheses that are unfalsifiable, experiments without proper controls, sample sizes without power analysis, and conclusions that overreach the data. The agent asks the hard questions early—before time and resources are committed to a flawed design.

The skill also covers the practical aspects of research preparation: structuring literature searches with Boolean queries, maintaining citation databases, designing reproducible experimental protocols, preparing materials for ethical review boards, and formatting submissions to meet journal-specific requirements. It bridges the gap between knowing what good research looks like and executing it systematically.

Use When

  • Formulating research questions and hypotheses
  • Designing experiments with proper controls and sample sizes
  • Conducting systematic literature reviews
  • Preparing manuscripts for peer review submission
  • Writing grant proposals or research proposals
  • Evaluating the methodology of existing papers

How It Works

graph TD
    A[Research Question] --> B[Literature Review]
    B --> C[Identify Knowledge Gap]
    C --> D[Formulate Hypothesis]
    D --> E[Design Experiment]
    E --> F[Power Analysis: Sample Size]
    F --> G[Define Controls + Variables]
    G --> H[Ethical Review Preparation]
    H --> I[Data Collection Protocol]
    I --> J[Analysis Plan: Pre-registered]
    J --> K[Execute + Collect Data]
    K --> L[Analyze per Pre-registered Plan]
    L --> M[Write Manuscript]
    M --> N[Peer Review Preparation]

The methodology flow is sequential with gates: the hypothesis must be falsifiable before designing the experiment, the experiment must have adequate power before collecting data, and the analysis plan must be pre-registered before execution begins.

Implementation

class ResearchProtocol:
    def formulate_hypothesis(self, observation: str, literature: list[str]) -> dict:
        return {
            "null_hypothesis": "There is no significant difference between...",
            "alternative_hypothesis": "Treatment X increases Y by at least Z...",
            "falsifiability": "This hypothesis is falsifiable because...",
            "variables": {
                "independent": ["Treatment type (A vs B vs control)"],
                "dependent": ["Measured outcome Y"],
                "controlled": ["Age, sex, baseline Z"],
                "confounding": ["Prior exposure to X"],
            },
        }

    def power_analysis(self, effect_size: float, alpha: float = 0.05, power: float = 0.80) -> dict:
        from statsmodels.stats.power import TTestIndPower
        analysis = TTestIndPower()
        n = analysis.solve_power(effect_size=effect_size, alpha=alpha, power=power)
        return {
            "required_n_per_group": int(np.ceil(n)),
            "total_n": int(np.ceil(n)) * 2,
            "effect_size": effect_size,
            "alpha": alpha,
            "power": power,
            "recommendation": f"Recruit {int(np.ceil(n * 1.2))} per group to account for 20% attrition",
        }

    def literature_search(self, topic: str) -> dict:
        return {
            "databases": ["PubMed", "Scopus", "Web of Science"],
            "query": f'("{topic}") AND (randomized OR controlled) AND ("2020"[Date] : "2026"[Date])',
            "inclusion_criteria": [
                "Peer-reviewed original research",
                "English language",
                "Human subjects",
                "Published 2020-2026",
            ],
            "exclusion_criteria": [
                "Review articles (captured separately)",
                "Case reports (n < 10)",
                "Non-peer-reviewed preprints",
            ],
            "prisma_flow": "Record screening, eligibility, and inclusion counts per PRISMA 2020",
        }

    def experimental_design(self, hypothesis: dict) -> dict:
        return {
            "design": "Randomized controlled trial, double-blind, parallel group",
            "randomization": "Block randomization with variable block sizes (4, 6, 8)",
            "blinding": "Participants and assessors blinded; unblinded statistician",
            "primary_outcome": hypothesis["variables"]["dependent"][0],
            "secondary_outcomes": [],
            "timeline": "Baseline → 4 weeks intervention → 8 weeks follow-up",
            "analysis_plan": "Pre-registered at OSF.io before data collection",
        }

Best Practices

  • Pre-register analysis plans before data collection to prevent p-hacking
  • Conduct power analysis during design, not after collecting data
  • Use PRISMA guidelines for systematic reviews and CONSORT for clinical trials
  • Maintain a living literature database with citation manager (Zotero, Mendeley)
  • Separate exploratory analyses from confirmatory analyses in reporting
  • Include a limitations section that honestly addresses methodological weaknesses

Platform Compatibility

PlatformSupportNotes
CursorFullProtocol + analysis code
VS CodeFullLaTeX + Python integration
WindsurfFullResearch workflow support
Claude CodeFullMethodology guidance
ClineFullResearch protocol generation
aiderPartialCode-level support

Related Skills

Keywords

research-methodology hypothesis-generation experimental-design literature-review power-analysis pre-registration peer-review prisma


© 2026 googleadsagent.ai™ | Agent Skills™ | MIT License

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most literature review skills give in ~1.3k tokens

Counted across 185 of the 191 authors here whose files we hold, read 2026-09-06

  • Screen sources by title, abstract, then full textin 16 of 185, across 9 files
  • Create a search protocol before collecting sourcesin 11 of 185, across 5 files
  • Convert the prompt into a searchable research questionin 11 of 185, across 5 files
  • Keep a reproducible search login 11 of 185, across 5 files
  • Group evidence by theme, not per paperin 11 of 185, across 5 files
  • Ask the user which review rigor level is neededin 11 of 185, across 5 files
  • Use a structured extraction tablein 11 of 185, across 5 files
  • Separate claims by confidence levelin 10 of 185, across 4 files
  • Deduplicate by DOI, identifier, then titlein 10 of 185, across 4 files
  • Record exclusion reasons at each screening stagein 9 of 185, across 3 files
  • Verify citation identifiers before finalizingin 9 of 185, across 4 files
  • Search a minimum of three databasesin 7 of 185, across 6 files

Said here and by no other author read

  • Formulate falsifiable hypotheses before designing experiments
  • Conduct power analysis before collecting data
  • Pre-register the analysis plan before data collection
  • Define controls and variables in the experimental design
  • Structure literature searches with Boolean queries
  • Use PRISMA for systematic reviews and CONSORT for trials

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.