repro-logger
Skill4 starsChanged 4 months agoLicence not identifiedView on GitHub
Use this skill to turn a data-analysis run into reproducible records. Given the scripts you ran, the data you used and the outputs you got, it drafts a reproduction log (input data → processing script → output), a variable-construction note, a sample-selection log (row counts at each filter), a results explanation and an open-questions checklist; it also abstracts one analysis run into a reusable project template. Records only what the user provides; marks steps that could not run for missing data or license; never fabricates numbers, file names or results. The human checks the draft for errors and omissions.
In this repository7 other files it gives its agents.
- paper-contextSkill
- paper-strategySkill
- replication-navigatorSkill
- data-cleaning-plannerSkill
- regression-interpreterSkill
- stata-runnerSkill
- data-auditSkill
The file
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
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.