agentleFS
Sign inStart free
pedrohcgspedrohcgs/claude-code-my-workflow/.agents/skills/simulation-study/SKILL.md

simulation-study

Skill1.7k starsChanged 5 days agoMITView on GitHub

Scaffold and run a reproducible Monte Carlo simulation study in R — a declared assumption regime, a parameterized DGP, an estimator grid, a seeded replication loop, and a summary of bias, RMSE, empirical SE, coverage, size/power with Monte Carlo standard errors. Use when the user says "run a Monte Carlo simulation", "simulation study", "check the bias/coverage of an estimator", "compare estimators in simulation", "size and power simulation", "Monte Carlo experiment", or wants to demonstrate an estimator's finite-sample properties. Produces a numbered R script in `scripts/R/` and saves per-replication raw results + a summary table to `output/`.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Who's talking about pedrohcgs/claude-code-my-workflow

The biggest 5 of 16 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 16

Talked about on GitHub and Bluesky (16 times).

On GitHub · 14

9 more on GitHub

On Bluesky · 2

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Read that file now and follow it, with the files it points to.

    line 10
  2. Distinctive:

    Fresh context: If the step needs a context that has not seen your work, for example a claim verifier that must never see the draft, run it …

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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
<!-- Generated by scripts/sync-agent-skills.py from .claude/skills/simulation-study/SKILL.md. Do not edit: change the source and re-run the script. -->

simulation-study

This skill's instructions live in .claude/skills/simulation-study/SKILL.md. Read that file now and follow it, with the files it points to. Read AGENTS.md first if you have not already.

It was written for Claude Code. Running it from Codex, Antigravity or another agent:

  • Arguments. Where it says $ARGUMENTS, use what the user asked for.
  • Claude Code agents. Where a step hands work to an agent in .claude/agents/ (through the Agent or Task tool), do that step where it appears in the procedure: never later, and never skip it. A step that gates what follows still gates it (/commit runs its verifier before it commits). Read the agent's file for what the step checks.
  • Fresh context. If the step needs a context that has not seen your work, for example a claim verifier that must never see the draft, run it in a separate session or worker that has not seen the draft, if your tool can start one, and give it only what the step says to pass. If it cannot, do the step yourself, mark every result it produced not independently verified, and tell the user to repeat that check in Claude Code (/verify-claims for citations) before relying on it.
  • Claude Code settings. allowed-tools, model, effort, argument-hint and disable-model-invocation in the source's frontmatter configure Claude Code. Ignore them.
  • Guards. Claude Code's guard hooks do not run for you. Follow the rules in AGENTS.md yourself; the git pre-commit gate and CI still apply to your commits.

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.

Check your setup, free