new-block
Skill4 starsChanged 41 days agoApache-2.0View on GitHub
Scaffold a new Aevum block (block.yaml plus its paired narrative plan), fill it in with the user, and validate it with preflight.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- robotostudio/turbo-start-sanitytheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- robotostudio/turbo-start-sanity★ 187same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Create block $ARGUMENTS and take it to a clean preflight.
- Very specific: line 16
Read .claude/templates/block.yaml for the schema and list the agents under .claude/agents/: each task's agent: must be one of them.
- Very specific: line 26
Write docs/blocks/<BLOCK_ID>/block.yaml and the narrative plan under docs/plans/.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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.
Files
Create block $ARGUMENTS and take it to a clean preflight.
Scaffold both artefacts:
bash scripts/new-block.sh $ARGUMENTS- Read
.claude/templates/block.yamlfor the schema and list the agents under.claude/agents/: each task'sagent:must be one of them. - Interview the user with AskUserQuestion until you can fill the block:
the goal, the clusters and their order, each task's surface
(
files_touched_globs) and acceptance criteria, and kill criteria if the block has a deadline. Push for acceptance criteria a script can check (a command and its expected result, a regex over a file), since Gate 3a verifies them mechanically. Skip what the code already answers. - Write
docs/blocks/<BLOCK_ID>/block.yamland the narrative plan underdocs/plans/. Setbase_shato the current tip ofbase_branch. Leavestatus: draft. Validate and fix until the only blocker left is
status is 'draft'(activation happens at dispatch):python3 scripts/block-preflight.py <BLOCK_ID>Capture the Gate-1 baseline:
bash scripts/capture-baseline.sh <BLOCK_ID>
Finish by telling the user the block is ready for review and that
/dispatch <BLOCK_ID> (/aevum:dispatch with the plugin) activates and launches it. Do not commit.
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.

