agentleFS
JunMA98JunMA98/Computer-science-claude-skills/skills/statistical-analysis/SKILL.md

statistical-analysis

Skill3 starsChanged 8 months agoMITView on GitHub

Choose and report statistical analyses for CS experiments, benchmarks, user studies, and offline evaluations. Use when selecting tests, checking assumptions, comparing multiple runs or seeds, estimating uncertainty, reporting effect sizes, or deciding whether differences in results are credible.

46 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use evidence-driven-writing, experiment-results-planning and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • Norman-burySkill

    evidence-driven-writing

    Use when writing or revising Introduction, Related Work, background, literature synthesis, or any section where references must drive claims

    Also in 3 projects that use this

  • Norman-burySkill

    experiment-results-planning

    Use when designing experiments, result tables, mock planning data, evaluation protocols, or results sections before real data are final

    Also in 3 projects that use this

  • +10 more from Norman-bury

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 39 edited versions we read keep these.

  • 7

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill for analysis planning and result interpretation in computing experiments.

    line 8
  2. Distinctive:

    Check whether samples are paired, repeated, hierarchical, or independent.

    line 22
  3. Distinctive:

    Prefer paired analyses when systems are evaluated on the same items.

    line 38
  4. Distinctive:

    Treat multi-seed results as repeated measurements, not independent benchmarks.

    line 39
  5. Distinctive:

    Use bootstrap or permutation methods when classical assumptions are weak.

    line 41
  6. Distinctive:

    Do not reuse APA-style prose as the default.

    line 42
  7. Distinctive:

    When the user asks for statistical guidance without a required format, return:

    line 46

“Common” is measured: kept by at least 6 in 10 of the 39 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Statistical Analysis

Use this skill for analysis planning and result interpretation in computing experiments.

Common CS Cases

  • compare models across multiple seeds
  • assess whether an ablation difference is meaningful
  • analyze benchmark subsets or error slices
  • evaluate user-study outcomes in HCI or interactive systems
  • report uncertainty for retrieval, ranking, generation, or systems metrics
  • choose between parametric, nonparametric, permutation, bootstrap, or Bayesian approaches

Workflow

  1. Define the unit of analysis correctly.
  2. Check whether samples are paired, repeated, hierarchical, or independent.
  3. Choose tests that match the design and metric distribution.
  4. Report uncertainty and effect size, not only p-values.
  5. State what the analysis does and does not justify.

Local Resources

  • references/test_selection_guide.md
  • references/assumptions_and_diagnostics.md
  • references/effect_sizes_and_power.md
  • references/reporting_standards.md
  • references/bayesian_statistics.md
  • scripts/assumption_checks.py

CS-Specific Rules

  • Prefer paired analyses when systems are evaluated on the same items.
  • Treat multi-seed results as repeated measurements, not independent benchmarks.
  • Report variance and confidence intervals when benchmark scores are unstable.
  • Use bootstrap or permutation methods when classical assumptions are weak.
  • Do not reuse APA-style prose as the default; write for technical readers.

Default Output

When the user asks for statistical guidance without a required format, return:

  1. recommended analysis plan
  2. assumptions to verify
  3. what to report in the paper or report
  4. caveats that limit interpretation

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.