agentleFS
JiamingShi-JsPhysJiamingShi-JsPhys/chelate-shell/skills/longitudinal-analysis/SKILL.md

longitudinal-analysis

Skill10 starsChanged 6 days agoMITView on GitHub

Runs a repeated-measures / panel analysis: descriptive statistics, a manipulation check, linear mixed models, mediation and sensitivity analysis. Python steps run anywhere; the mixed-model, mediation and sensitivity steps go through R and are skipped, not replaced, when Rscript is absent.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run this exact form — do not read the source tree:

    line 27
  2. Very specific:

    Run everything, or one named step with --step lmm.

    line 35

≈ “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

longitudinal-analysis

Orchestrates a fixed pipeline of statistical steps over panel data and reports each step's status. It never substitutes hand-written Python for a missing R step.

  • Stage: gates · Sandbox: no · Dependencies: pandas (numpy, R with lme4/lavaan, python-docx optional)

Quick Execution

Run this exact form — do not read the source tree:

python run.py --root <WS> --action list-steps -- --config config/examples/behavior_2x2x2.yaml
  • validate then list-steps shows which steps the config enables and which need R.
  • Run everything, or one named step with --step lmm.
  • The gate lands in <WS>/process/gates/longitudinal-analysis_<ts>.json.

When to use

  • The data has repeated measures (one or more sessions per subject).
  • The request names LMM, mixed model, mediation or sensitivity analysis.
  • Descriptive statistics or a manipulation check are needed over panel data.

When NOT to use

  • The data is a single cross-section — a plain test is enough.
  • You intend to imitate a skipped R step in Python — never do that.

Actions

--actionDoesExtra arguments
validateCheck the config--config <cfg>
list-stepsShow the enabled steps and their R needs--config <cfg>
runRun the whole pipeline, or one step--config <cfg> [--step lmm]
exportExport the generated tables--config <cfg> --format csv|docx

Hard constraints

  • Never hand-write Python to replace a skipped R step. Report the skip.
  • Never install R. List the missing packages and stop.
  • Report each step's own status; do not merge them into one verdict.

Outputs

  • <WS>/process/gates/longitudinal-analysis_<ts>.json — the gate result.
  • Per-step tables (CSV, or DOCX with --format docx) under process/.

Failure handling

  • A step reporting skipped means R or an R package is missing — list it and stop.
  • An invalid config exits non-zero naming the field.
  • A mid-pipeline error keeps earlier outputs and reports the failing step.

Limitations

  • R packages (lme4, lavaan, emmeans, jsonlite) must already be installed.
  • The mediation bootstrap count is the user's choice (default 5000) and dominates wall-clock time.

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.