AGENT SKILL

nasqret-playbook

Build a fresh route slate when a frontier move changes the shape of the search. Diff adjacent public winners, name their visible mechanisms (qubit shelf, lifetime move, Toffoli move, nonce dependence), run equal-size pilots, sort each route into tail-sensitive, structurally dirty, score-dead or validation-ready, and send compute only to the last group. Named for nasqret, whose broad sweeps it follows.

License 许可
MIT
最近更新
2026-10-30
Stars
★ 4
Forks
3

01 前言 Front Matter

name
nasqret-playbook
license
MIT
description
Build a fresh route slate when a frontier move changes the shape of the search. Diff adjacent public winners, name their visible mechanisms (qubit shelf, lifetime move, Toffoli move, nonce dependence), run equal-size pilots, sort each route into tail-sensitive, structurally dirty, score-dead or validation-ready, and send compute only to the last group. Named for nasqret, whose broad sweeps it follows.

03 SKILL.md 正文

Nasqret-style route factory

Use when a frontier move changes the shape of the search.

Goal

Avoid chasing stale single knobs. Build a route slate, test small, then scale only the routes that have landability and a validator.

Steps

  1. Refresh the current target.
  2. Diff adjacent public winners, not old endpoints.
  3. Extract visible mechanisms: qubit shelf, memory/lifetime move, Toffoli move, nonce/island dependence, validation note.
  4. Generate multiple route candidates.
  5. Run equal-size pilot checks.
  6. Classify each route:
    • tail-sensitive,
    • structurally dirty,
    • score-dead,
    • validation-ready.
  7. Dispatch compute only for validation-ready routes.
  8. Write negative evidence back to memory so dead lanes stay dead.

Output

Return a route slate with:

  • route ID,
  • expected edge,
  • validator,
  • kill gate,
  • owner,
  • credit note.

Credit

Inspired by nasqret / Bartosz Naskrecki's public frontier behavior and group-discussion process notes. Do not imply copied code.

04 同仓库更多 Skills

odinfree
odinfree/storm-ecdsa-harness

verify-research-transfer

Check whether a literature finding supports a proposed performance optimization. Read the primary figures and the implementation source, then run a cheap falsifier before writing code or benchmarks.

★ 4
odinfree
odinfree/storm-ecdsa-harness

verify-paired-native-measurements

Audit the process, sample and archive evidence behind paired native benchmarks, especially wrappers around an unchanged official client. Use before admitting benchmark results or when reviewing the controller that produced them. Ordinary unit tests do not need this.

★ 4
odinfree
odinfree/storm-ecdsa-harness

squares-in-squares-campaign

Pack n = 1..1000 unit squares into the smallest square (Kaggle "Squares in Squares", score sum L/sqrt(n) - 1). Use when improving, certifying or submitting packings, or when choosing the next search route. Covers the official-metric gates, the solver and MIS tools, the structure of the frontier, and the routes measured dead. The competition closed on 25 Oct 2026.

★ 4
odinfree
odinfree/storm-ecdsa-harness

shot-autopsy

When a candidate fails shots its parent passes, find the structural cause before any nonce search. Reconstruct the exact failing shot, localize the first divergence, repair it by paying precision, and keep the case as a permanent regression. Learned from bulengerk's ecdsa.fail rows. Use when an edited candidate fails shots its parent passed, or when counts drift between builds.

★ 4
odinfree
odinfree/storm-ecdsa-harness

send-to-claude-fable

Send a bounded task or review packet to the local Claude Code CLI on the Fable model and bring back its verdict. Use when you want an independent second opinion from a different model.

★ 4
odinfree
odinfree/storm-ecdsa-harness

rust-archive-build-binding

Prevent stale Cargo artifacts when a source archive is restored over a reused Rust target directory. Use for reproducible benchmark comparisons and for moving source archives between machines.

★ 4