DATA block to be filled by the build script (all ready skills, full skill.md content).
Everything below will light up once the data lands.
— SOPs. Their article mappings resolve to — hubs: — catalog-ready and — in progress. A Definitive marker also requires review of the actual page.
Never treat a task as isolated. Gather (Produce) → Process in Descript → Post → Promote with ads. Digital Plumbing sits under the line as gates: a $1/day boost with no pixel is spend you cannot retarget. Click a phase to filter the library.
Use each real run to check the recipe. Record what happened, including failed or blocked work, then review any lesson before changing the shared instructions. Writing the run record is required; public release needs its own authority.
Do → Check the result → Write the run record → Link the task → Review the lesson → ↺
One maintained recipe explains a repeatable task. Each actual execution gets a meta article: a written account of its steps, evidence, result, and next handoff. Keep the same execution ID across revisions and retries. A written draft is a valid record while public release is pending.
If a run reveals a useful lesson, propose a change to the recipe and review the evidence. The next execution tests an accepted change. A failed run, an unresolved gap, or no justified recipe change can be the honest result.
Nothing in — SOPs matches that combination of search and status filter.