All authors
Claude Skills by whenpoem
github.com/whenpoem14 skills0 installs15 views
- Bt TournamentRank competing hypotheses with online Bradley-Terry updates and LUCB intervals. Replaces elo-select. Use whenever there are 3 or more candidate hypotheses competing for the next experiment, or when the user wants to understand which branch is currently leading.Votes: 0GitHub stars: 8
- Debug SopSystematic debugging. Use when a script errors or produces unexpected results.Votes: 0GitHub stars: 8
- PreregisterLock the falsification target for a confirmatory hypothesis before promoting results to main claims. Records metric, direction, threshold, multiple-comparison correction, and seed budget into ver_preregistrations.Votes: 0GitHub stars: 8
- Prove SopEnd-to-end statistical proof loop. Use when the user asks to prove a statistical proposition, when a hypothesis is promoted to a theorem, or when the empirical trunk's reviewer demands a theorem-side gate. This SOP is suggestion-only (per ADR 0007); skip, loop, or interleave with empirical work as the situation calls for.Votes: 0GitHub stars: 8
- ReplayRun a counterfactual ("what if we had approved hyp_07 instead of pruning it") against a saved snapshot without mutating the live graph. Use when the user wants to second-guess a paused branch or audit a past pruning decision.Votes: 0GitHub stars: 8
- Research SopEnd-to-end research loop. Use at the start of any new research task; triggers literature review, hypothesis generation, Elo selection, experimentation, and verification.Votes: 0GitHub stars: 8
- Writeup SopWriting reports or papers. Use when producing any .md file that makes claims about experimental results.Votes: 0GitHub stars: 8
- Bt TournamentRank competing hypotheses or proof skeletons from the complete comparison ledger using a joint batch MAP Bradley-Terry fit and approximate posterior intervals. Use whenever 3 or more candidates compete for the next experiment, or when the user asks which branch currently leads. Do not present the intervals as calibrated confidence bounds.Votes: 0GitHub stars: 8
- Debug SopDiagnose errors, failed tests, crashes, hangs, regressions, suspicious outputs, and unexpected experimental results through reproducible hypothesis-driven debugging. Use whenever a script or system behaves incorrectly, even if the user only says it is broken or pastes an error. Respect diagnosis-only requests; implement a fix only when authorized.Votes: 0GitHub stars: 8
- PreregisterLock a confirmatory falsification target and its fixed multiple-comparison family before observing the confirmatory result. Use before promoting an exploratory finding to a main claim or whenever several related hypotheses need Bonferroni control. Records metric, threshold, family id/size, correction, and seed budget.Votes: 0GitHub stars: 8
- Prove SopBuild and audit a statistical or mathematical proof from proposition capture through skeleton selection, diagnosis, correction, optional empirical checking, and optional Lean reinsurance. Use when the user asks to prove or rigorously derive a proposition, a graph proposition lacks a verified proof, or a reviewer requires a theorem-side gate.Votes: 0GitHub stars: 8
- ReplayAudit a past pruning or approval decision by creating a counterfactual branch from a saved snapshot without mutating the live graph. Use when the user asks what would have happened under another decision, disputes a paused branch, or wants to inspect an earlier checkpoint.Votes: 0GitHub stars: 8
- Research SopRun an end-to-end, auditable research workflow from question framing through literature, competing hypotheses, experiment selection, implementation, verification, and claim handoff. Use whenever the user asks to investigate, compare, test, validate, or establish an empirical research claim, including when they do not explicitly call it research. Do not use for a simple factual lookup or a narrowly scoped code change with no research claim.Votes: 0GitHub stars: 8
- Writeup SopProduce or revise research reports, result-bearing Markdown, paper sections, and manuscripts without overstating evidence. Use whenever writing text that reports experimental metrics, statistical conclusions, hypothesis rankings, theorem claims, or research findings. Do not trigger for ordinary README edits, changelogs, or prose with no research-result claim.Votes: 0GitHub stars: 8