Menu

Individual skill

principle-build-the-lever

Use for any edit, migration, analysis, or verification beyond the trivial. Produce a codemod, script, generator, or repeatable check that performs or demonstrates the result, so a reviewer can rerun it in place of taking your word.

plugins/requie/endostack/skills/principle-build-the-lever/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,531
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Build the lever

Once a task is more than trivial, create the tool that carries it out or checks it: a codemod, a script, a generator, a check you can run again, or a skill file that delegates read. Manual work can only be confirmed by repeating it, while a deterministic tool lets the reviewer confirm it with one command.

## When it applies

Edits, migrations, analyses, and verification of any size above trivial. What triggers it is that the work is non-trivial, whether or not it repeats. Even a task you will do once deserves a tool if the tool is what lets someone check the result.

Skip it for a couple of obvious edits that anyone can verify at a glance.

## What to do

1. Default to building the tool.
2. Handle the first unit manually so you understand the steps. Next, write the tool, point it at that same unit, and compare its output with your manual version. Identical output shows the tool is correct.