← ClaudeAtlas

strata-scriptsmithlisted

The Strata script creation protocol — when a script is required, run vs extend vs new, scaffolding with strata new script, manifest fields and side-effect classes, runtime choice, shared lib reuse, tests and the --format json contract, gates, catalog and linking. Use when an operation is repeatable and deterministic, before improvising a command you have run before, or when writing or changing anything under scripts/.
zbmowrey/strata · ★ 0 · Code & Development · score 75
Install: claude install-skill zbmowrey/strata
# Writing Strata scripts ## Find first `strata search '<need> kind:script'` · `strata scripts list` · then `strata run <id> -- <args>`. | Situation | Action | | --------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------ | | A script fits | Run it. | | Nearly fits; change additive, backward-compatible, current behavior tested | Extend: new flag, existing output byte-identical, new tests. | | Change alters semantics, interface, output, side-effect class, or callers unknown | New script; move shared code into `scripts/lib/<runtime>/` first — never copy-paste. | | Nothing fits and it will recur | `strata new script <domain>/<name> [--runtime go\|python]` | | Genuinely one-off | Run ad hoc (repeats are detected and become garden tasks). | ## Manifest (`script.yaml`) — scaffold placeholders fail lint until filled `id, summary, description, status, runtime, entry, usage, examples, input