agentsclimarketplace

Statistical simulation execution

Skill HolobiomicsLab/asb-skill-collections/collections/metabolomics/v2/skills/statistical-simulation-execution

Use when you have access to a published repository containing simulation scripts (e.From its SKILL.md

Install
npx -y skills add HolobiomicsLab/asb-skill-collections --skill statistical-simulation-execution

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

One thing to look at

  • 15 stars15 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its file declares

Copied from the file, not written here

The file declares its own license as CC-BY-4.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

6.1 KB, 984 tokens by cl100k_base, as published. Nobody here has run it

statistical-simulation-execution

License: restricted — no clear open-source license detected for the underlying tool; verify licensing before commercial use or redistribution. <!-- asb-license-banner -->

Summary

Execute pre-built statistical simulation scripts to generate and validate Type I error rates and power estimates across tested scenarios. This skill reproduces computational results from a methodological repository by systematically running validated simulation code and collecting summary statistics.

When to use

You have access to a published repository containing simulation scripts (e.g., PaIRKAT) and need to: (1) verify that published Type I error and power claims can be regenerated, (2) obtain simulation-based summary statistics for methodological validation, or (3) serve as a reference execution before adapting simulations for new parameters or study designs.

When NOT to use

  • The simulation scripts are not executable or dependencies are unavailable and cannot be resolved.
  • You need to modify simulation parameters (effect sizes, sample sizes, test designs) — use script adaptation skills instead.
  • The repository has no documented simulation scripts or the README does not clearly identify which files contain Type I error or power code.

Inputs

  • Repository clone or downloaded source code (e.g., github.com/CharlieCarpenter/PaIRKAT)
  • Type I error simulation script (R or language-native)
  • Power simulation script (R or language-native)
  • Study design parameters embedded in or read by scripts (e.g., sample size, effect size, significance threshold)

Outputs

  • Type I error rate summary statistics (point estimates and confidence intervals)
  • Statistical power estimates across tested scenarios
  • Validation comparison table (generated vs. reported values)
  • Simulation logs or diagnostic plots documenting convergence and coverage

How to apply

Clone or download the target repository (e.g., github.com/CharlieCarpenter/PaIRKAT) and locate the designated simulation scripts (e.g., SimulationFunctions). Load and execute the Type I error simulation script to compute error rates and generate summary statistics across the predefined test scenarios. Then execute the power simulation script to compute statistical power under the same or related tested scenarios. Collect all generated outputs (numerical summaries, plots, or tables) and validate them against the reported values in the source article or repository documentation. Any discrepancies in summary statistics should be investigated for script modifications, dependency version changes, or random seed drift.

Related tools

Examples

# Source and execute Type I error simulation
source('PaIRKAT/SimulationFunctions/TypeISimulation.R')
run_typeI_simulation(n_replicates=10000, alpha=0.05)

# Source and execute power simulation
source('PaIRKAT/SimulationFunctions/PowerSimulation.R')
run_power_simulation(n_replicates=10000, effect_sizes=c(0.2, 0.5, 0.8))

Evaluation signals

  • Generated Type I error rates match reported values within expected Monte Carlo standard error (typically ±0.005–0.010 for 10,000+ replicates).
  • Power estimates are monotonically increasing or stable across effect size and sample size scenarios as expected by statistical theory.
  • All simulation output files are generated and contain non-null, numeric summary statistics with expected dimensionality.
  • Random seed reproducibility check: re-running with the same seed produces identical summary statistics.
  • No warnings or errors logged during script execution; any numerical edge cases (e.g., Inf, NaN) are documented and explained.

Limitations

  • Simulation results depend on random seed and number of replicates; minor numerical drift across runs and systems is expected.
  • The repository README does not document a changelog, so changes or corrections to simulation code may not be tracked in version history.
  • Validation against reported values requires access to the original article and reported summary statistics; missing or ambiguous reporting makes validation difficult.
  • Execution environment (R version, package versions) can affect numerical results; reproducibility may require pinning dependencies.

Evidence

  • [intro] The task focuses on reproducing Type I error and power simulation results from the SimulationFunctions scripts.: "TypeI and Power simulation scripts"
  • [other] The workflow explicitly includes executing both error and power simulations and collecting summary outputs.: "Execute the Type I error simulation script to compute error rates and generate summary statistics. 4. Execute the power simulation script to compute statistical power across tested scenarios and"
  • [readme] The repository is identified as the authoritative source for PaIRKAT simulation functions.: "Scripts for PaIRKAT functions with example work flow"

What ships with it

Read from the repository

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

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.