bootloops-ai · Agent Skills
出典を確認した実質的な文書を持つ Skill が 12 件あります。カードを開くと原文、パッケージ内容、導入方法を確認できます。
acceptance-gate
The standard a computed result must meet before it may be called done. Use whenever an agent claims an integral is solved, a fit has closed, a formula is identified, or any quantitative answer is ready — the claim is not done until it passes this gate.
- 1時間の導入数
- 4
- GitHub Stars
- 6
- 更新日
- 10月1日
bootloops-setup
Set up the BootLoops protocol skills for this user. Use when the user asks to set up BootLoops, activate or install its skills, or asks what discipline the toolkit ships with. Presents the roster, asks which skills to activate, and installs only what the user chooses.
- 1時間の導入数
- 4
- GitHub Stars
- 6
- 更新日
- 10月1日
constant-recognition
Discipline for integer-relation searches (PSLQ, LLL) that turn high-precision digits into exact constants. Use whenever recognizing a numerical value as a closed form, fitting boundary constants, or reporting that no closed form exists.
- 1時間の導入数
- 4
- GitHub Stars
- 6
- 更新日
- 10月1日
independence-bookkeeping
Provenance rules that keep checks independent. Use when setting up any comparison, oracle, or reference value — and whenever tempted to certify a result with machinery that helped produce it.
- 1時間の導入数
- 4
- GitHub Stars
- 6
- 更新日
- 10月1日
lit-review
Deep literature review behind a research project's novelty claims — a protocol whose one job is to prevent shortcuts. It demands the papers be actually read (nothing from memory), makes thoroughness falsifiable (read ledgers, search receipts, gap statements), tracks citation chains in both directions, and lists the places to look. Use before any novelty claim ships, when writing or reviewing a related-work section, and when refereeing.
- 1時間の導入数
- 4
- GitHub Stars
- 6
- 更新日
- 10月1日
planted-truth
Synthetic-truth controls for analysis pipelines. Use before running any statistical fit, solver, audit, or search on real data — the pipeline must first prove it can recover a known planted answer and catch a deliberately corrupted input.
- 1時間の導入数
- 4
- GitHub Stars
- 6
- 更新日
- 10月1日
prove-protocol
Multi-agent protocol for proving or refuting mathematical statements. Use when trying to prove a mathematical statement with agents, when a claimed lemma keeps dying under scrutiny, or when the true statement itself is still unknown (theory-finding regime).
- 1時間の導入数
- 4
- GitHub Stars
- 6
- 更新日
- 10月1日
reading-contract
Sources-only discipline for any instrument or agent that reads documents and asserts facts from them — literature audits, record replays, data extraction, citation of prior work.
- 1時間の導入数
- 4
- GitHub Stars
- 6
- 更新日
- 10月1日
ref-check
Careful bibliography verification and entry-addition for papers — verify every author, title, journal, volume, pages, year, arXiv ID, and DOI against authoritative online sources (INSPIRE, arXiv, CrossRef/DOI, zbMATH, publisher) before anything enters or stays in a .bib file. Use whenever adding bib entries, auditing a bibliography, checking citations, fixing references, or when asked to "check the references". Encodes the report-then-fix pattern for full-file audits and the folklore-error traps
- 1時間の導入数
- 4
- GitHub Stars
- 6
- 更新日
- 10月1日
referee-sim
Use before circulating any outward-facing scientific document — simulate the strongest standard objection from every audience it claims and verify the document answers each where that reader would look.
- 1時間の導入数
- 4
- GitHub Stars
- 6
- 更新日
- 10月1日
timing-discipline
Compute-planning rules. Use before launching any calculation whose runtime is not already measured — and whenever an agent proposes a long run, an overnight grind, or a bigger machine as the way forward.
- 1時間の導入数
- 4
- GitHub Stars
- 6
- 更新日
- 10月1日
tool-stewardship
How the toolkit is consulted, extended, and documented. Use before writing any new code — and after, when a genuinely new instrument has earned its place.
- 1時間の導入数
- 4
- GitHub Stars
- 6
- 更新日
- 10月1日
