agentleFS
odinfreeodinfree/storm-ecdsa-harness/skills/nasqret-playbook/SKILL.md

nasqret-playbook

Skill4 starsChanged 21 days agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

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

    line 11
  2. Distinctive:

    Avoid chasing stale single knobs.

    line 15
  3. Distinctive:

    Run equal-size pilot checks.

    line 25
  4. Distinctive:

    Write negative evidence back to memory so dead lanes stay dead.

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

Rundumschlag (nasqret-playbook)

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.

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.