Agent skill

Method Audit

by flonat in flonat/flonat-research

Extract and compare data-collection methods across a set of empirical papers.

MITAuto-check passed

Install Method Audit

skills CLI
$ npx skills add flonat/flonat-research --skill method-audit -a claude-code

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

GitHub CLI
$ gh skill install flonat/flonat-research method-audit --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/flonat/flonat-research.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/method-audit .claude/skills/method-audit && 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
method-audit
GitHub stars
145
Token cost
~1.7k tokens
SKILL.md length
598 words
Files
1
Skills in repo
83
Repo updated
First seen
Licence
MIT

At a glance

Extract and compare data-collection methods across a set of empirical papers.

  • Works in 4 steps: Corpus Assembly → Method Extraction → Comparative Analysis → …
  • The user needs a cross-paper methods matrix
  • SKILL.md covers Output Path, When to Use, When NOT to Use and Input, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Method Audit is an agent skill from flonat/flonat-research. Extract and compare data-collection methods across a set of empirical papers. Use when the user needs a cross-paper methods matrix or wants to assess how a literature gathers evidence.

Its SKILL.md is about 1.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Shareable Claude Code + Codex infrastructure for PhD researchers — skills, agents, hooks, and rules for academic workflows. The licence is MIT.

When your agent uses it

  • The user needs a cross-paper methods matrix
  • Wants to assess how a literature gathers evidence

Example prompts

  • “/method-audit”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Glob, Grep, Bash(uv*), Bash(uv:*), Task, WebSearch, WebFetch, Bash(paperpile*)

Workflow steps

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

  1. Corpus Assembly
  2. Method Extraction
  3. Comparative Analysis
  4. Output

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Glob
    • Grep
    • Bash(uv*)
    • Bash(uv:*)
    • Task
    • WebSearch
    • WebFetch

    …and 1 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

    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

Method Audit loads about 1.7k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 598 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~49
When it runs · the whole SKILL.md, loaded when a task matches
~1.7k

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 flonat/flonat-research at commit da27600, republished under its MIT licence (© flonat). 598 words, ~1,669 tokens.

Download SKILL.mdSave it as .claude/skills/method-audit/SKILL.md (or your agent's skills folder).
name
method-audit
description
Extract and compare data-collection methods across a set of empirical papers. Use when the user needs a cross-paper methods matrix or wants to assess how a literature gathers evidence.
allowed-tools
Read, Write, Edit, Glob, Grep, Bash(uv*), Bash(uv:*), Task, WebSearch, WebFetch, Bash(paperpile*)
argument-hint
[topic, .bib file, or paper directory]
skill-dependencies
causal-design, split-pdf

Method Audit

Reverse-engineer the data collection and empirical methods across a corpus of papers. Produce a critical comparison table that surfaces methodological blind spots.

Output Path

Per rules/review-artefact-routing.md (auto-loads in research projects (path-scoped to paper-*/ and paper/)):

  • Source slug: method-audit
  • Write reports to: reviews/_project/method-audit/<YYYY-MM-DD-HHMM>.md inside the project. Path is relative to the research project root, not the Task-Management repo.
  • Never at project root (./CRITIC-REPORT.md-style filenames are forbidden — pre-rule layout).
  • Idempotency: timestamps include hour+minute (HHMM) to disambiguate same-day runs; never overwrite an earlier run's report.
  • Index update: if reviews/INDEX.md exists, write a one-line entry under "Latest per source" pointing at the new file. Otherwise review-recap will rebuild the index next time it runs.
  • Infrastructure repos (Task-Management, atlas-workspace, etc.): this section does not apply — the path-scoped rule won't load there.

When to Use

  • Writing a methodology section — need to justify your approach relative to the literature
  • Reviewing empirical papers — need to compare data quality across studies
  • Identifying methodological gaps — what approach has nobody tried yet?
  • Preparing a replication or extension — need to understand exactly how prior work was done

When NOT to Use

  • Theoretical papers — use an installed theoretical-comparison workflow instead
  • Single-paper deep read — use split-pdf
  • Your own research design — use causal-design or experiment-design
  • Code review — use the code-review agent

Input

A .bib file, PDF directory, topic description, or list of papers. If ambiguous, ask.

Workflow

Phase 1: Corpus Assembly

Assemble 10-20 empirical papers from the supplied bibliography or directory, or through configured scholarly-search tools. Prioritise papers with empirical content and filter out pure theory, editorials, and commentaries.

Phase 2: Method Extraction

For each paper, read using split-pdf methodology. Extract:

  1. Research design — experimental, quasi-experimental, observational, survey, qualitative, mixed
  2. Data source — where the data comes from (name the dataset, survey instrument, or archive)
  3. Sample
    • Population and sampling frame
    • Sample size (N)
    • Unit of observation
    • Time period
    • Response rate (if survey)
    • Attrition (if longitudinal)
  4. Variables
    • Dependent variable(s) and how measured
    • Key independent variable(s) and how measured
    • Controls included
  5. Estimation strategy
    • Statistical method (OLS, IV, DiD, RCT, qualitative coding, etc.)
    • Identification strategy (what makes the estimate causal, if claimed)
    • Robustness checks reported
  6. Biases acknowledged — what limitations the authors discuss
  7. Biases NOT acknowledged — what you can spot that they don't mention
Show full SKILL.md (226 more words)Show less
Phase 3: Comparative Analysis
3.1 Methods Comparison Table
PaperDesignData SourceNPeriodMethodID StrategyResponse Rate

Sort by sample size (largest first).

3.2 Technique Distribution

Count how many papers use each:

  • Design type (experimental, observational, etc.)
  • Estimation method (OLS, IV, DiD, etc.)
  • Data type (survey, admin, experimental, scraped, etc.)

Flag any technique that is dominant (>60% of papers) — this signals a methodological monoculture.

3.3 Bias Audit

For each paper, classify biases:

PaperBiases AcknowledgedBiases MissedSeverity

Common missed biases to check for:

  • Selection bias — non-random sampling without correction
  • Measurement error — self-reported outcomes, proxy variables
  • External validity — single-country, single-firm, WEIRD samples
  • Survivorship bias — studying only firms/people that survived
  • Publication bias — significant results overrepresented
  • Endogeneity — causal claims without credible identification
  • Multiple testing — many outcomes tested without correction
3.4 Methodological Gaps
  • Designs nobody has tried (e.g., no RCT in a field of observational studies)
  • Data sources nobody has used (e.g., admin data when everyone uses surveys)
  • Robustness checks nobody runs (e.g., no placebo tests, no sensitivity analysis)
  • Populations understudied (e.g., only US data in a global phenomenon)
Phase 4: Output

Write to METHOD-AUDIT.md in the project directory.

Output Format

markdown
# Method Audit: [Topic]

**Date:** YYYY-MM-DD
**Corpus:** [N] empirical papers
**Dominant design:** [Most common research design]
**Dominant method:** [Most common estimation method]

## Comparison Table

| Paper | Design | Data | N | Period | Method | ID Strategy | Biases Noted |
|-------|--------|------|---|--------|--------|-------------|-------------|

## Technique Distribution

| Category | Count | Papers |
|----------|-------|--------|

## Bias Audit

### Commonly Acknowledged
- [Bias type] — mentioned by [N] papers

### Commonly Missed
- [Bias type] — present in [N] papers but acknowledged by [M]
  - **Why it matters:** [Impact on findings]
  - **Papers affected:** [List]

## Methodological Gaps

1. **No [design/method] studies** — [Why this matters]
2. **Understudied population:** [Who is missing]
3. **Missing robustness check:** [What should be tested]

## Implications for Your Research

- **Opportunity:** [What methodological gap you could fill]
- **Risk:** [What bias to watch for in your own design]
- **Benchmark:** [What sample size / design quality is expected in this field]

Cross-References

SkillWhen to use instead/alongside
Installed theoretical-comparison workflowFor theoretical rather than methodological comparison
causal-designTo design your own identification strategy
experiment-designTo design experiments or surveys
replication-auditTo check which findings have been replicated

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

Files

Just SKILL.md in skills/method-audit of flonat/flonat-research.

Open the folder on GitHubat commit da27600

Compare with similar skills

Method Audit 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.

Method Audit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Method Audit this skillflonat/flonat-research145—~1.7kAutomated safety check: PassMIT
Java Refactoring Extract Methodgithub/awesome-copilot40k1 repos~873Automated safety check: PassMIT
Extractalirezarezvani/claude-skills28k—~1.4kAutomated safety check: PassMIT
Brand Extractnexu-io/open-design100k—~3.1kAutomated safety check: PassApache-2.0
Design Extractnexu-io/open-design100k—~549Automated safety check: PassApache-2.0
Refactor Method Complexity Reducegithub/awesome-copilot40k1 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Java Refactoring Extract Method

    github/awesome-copilot

    Official

    Refactoring using Extract Methods in Java Language. An agent skill from github/awesome-copilot.

    40k GitHub starsUsed in 1 repo~873 tokens
    DevelopmentAuto-check passed
  • Extract

    alirezarezvani/claude-skills

    Turn a proven pattern or debugging solution into a standalone reusable skill with SKILL.md, reference docs, and examples.

    28k GitHub stars~1.4k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • Brand Extract

    nexu-io/open-design

    Extract a complete Brand Kit from a live website by driving the in-app browser.

    100k GitHub stars~3.1k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Design Extract

    nexu-io/open-design

    Extract design tokens (color / typography / spacing) from imported source code, screenshots, or Figma exports into the canonical token bag token-map consumes.

    100k GitHub stars~549 tokensUpdated today
    Frontend & DesignAuto-check passed
  • Refactor Method Complexity Reduce

    github/awesome-copilot

    Official

    Refactor given method ${input:methodName} to reduce its cognitive complexity to ${input:complexityThreshold} or below, by extracting helper methods.

    40k GitHub starsUsed in 1 repo~1.1k tokens
    DevelopmentAuto-check passed
  • Kg Extract

    ruvnet/ruflo

    Extract entities and relations from source files to build a knowledge graph

    74k GitHub stars~751 tokensUpdated today
    Knowledge ManagementAuto-check: notes

More from flonat/flonat-research

All 83 skills in this repo
  • Latex Posters

    flonat/flonat-research

    Create a large-format academic poster in LaTeX using beamerposter, tikzposter, or baposter.

    145 GitHub stars~1.5k tokensUpdated 8 days ago
    Auto-check: notes
  • Skill Creator

    flonat/flonat-research

    Create, revise, and evaluate reusable AI workflow skills, including trigger-quality tests.

    145 GitHub stars~4.4k tokensUpdated 8 days ago
    Auto-check passed
  • DOCX

    flonat/flonat-research

    Create, read, edit, or convert Microsoft Word documents while preserving professional document structure.

    145 GitHub stars~1.2k tokensUpdated 8 days ago
    Auto-check passed
  • PDF

    flonat/flonat-research

    Read, create, combine, split, rotate, OCR, watermark, secure, or extract content from PDF files.

    145 GitHub stars~488 tokensUpdated 8 days ago
    Auto-check passed
  • Init Project Orchestration

    flonat/flonat-research

    Create or migrate project-level agents, repeatable project workflows, and planning state from one client-neutral contract, then render repository-scoped adapters for both Claude Code and Codex.

    145 GitHub stars~1.6k tokensUpdated 8 days ago
    Auto-check passed
  • Pre Commit Audit

    flonat/flonat-research

    Deliver a fast pre-commit safety scan: file size, anonymity (author / affiliation strings in tex/bib), hardcoded secrets, and invisible-Unicode carriers.

    145 GitHub stars~2.8k tokensUpdated 8 days ago
    Auto-check: notes

Questions about Method Audit

What does Method Audit do?

Extract and compare data-collection methods across a set of empirical papers. Method Audit is an agent skill from flonat/flonat-research. Extract and compare data-collection methods across a set of empirical papers.

When should I use Method Audit?

Method Audit fits situations like: the user needs a cross-paper methods matrix; wants to assess how a literature gathers evidence.

How do I install Method Audit in Claude Code?

Run `npx skills add flonat/flonat-research --skill method-audit -a claude-code`. Or copy the skill folder (skills/method-audit in flonat/flonat-research) into .claude/skills/method-audit in your project. Claude Code loads it when a task matches its description.

How do I install Method Audit in Codex?

Run `npx skills add flonat/flonat-research --skill method-audit -a codex`. Or copy the skill folder (skills/method-audit in flonat/flonat-research) into .agents/skills/method-audit in your project. Codex loads it when a task matches its description.

Can I use Method Audit 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 flonat/flonat-research --skill method-audit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/method-audit, .gemini/skills/method-audit, .github/skills/method-audit and .opencode/skills/method-audit in your project.

What does Method Audit need to run?

SKILL.md names no scripts, command-line tools or credentials: Method Audit is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Glob, Grep, Bash(uv*), Bash(uv:*), Task, WebSearch, WebFetch, Bash(paperpile*).

Does Method Audit 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 Method Audit 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 Method Audit use?

Method Audit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Method Audit use?

About 1.7k tokens (SKILL.md is roughly 6.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Method Audit?

Skills that share tags, products or a category with Method Audit: Java Refactoring Extract Method (github/awesome-copilot, 40k stars), Extract (alirezarezvani/claude-skills, 28k stars), Brand Extract (nexu-io/open-design, 100k stars) and Design Extract (nexu-io/open-design, 100k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Method Audit?

flonat (a GitHub user) maintains it in flonat/flonat-research, which has 145 GitHub stars. The repository holds 83 skills in this directory. The repository was last updated on September 29, 2026.

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