Taste your own cooking: the moment you finish making something, check it with the very skills this repo ships before you serve it.
Goal
A reminder buried in docs ("remember to verify") won't reliably fire in a fresh session. sip makes the recursive self-improvement loop a triggered habit: right after any create or change, run our own skills on the result — the clean checks and the true ones — so quality doesn't ride on the author's biased in-session judgment.
Workflow
- Spot the trigger: you just created or changed an artifact or skill and are about to call it done, commit, or hand it off.
- Cold-read it — run
shower on the artifact (fresh-eyes comprehension / handoff check).
- Verify it's true — if the artifact asserts a reality-grounded claim, run
factchk; if it defines an eval, metric, or experiment, run mandela. Skip when it has neither.
- Check consistency — run
ssotize in audit mode across the repo for anything the change duplicated or contradicted; execute its consolidation plan only after approval.
- Detool portability claims — run
detool only when the artifact claims portability, tool-neutrality, stack-agnostic durability, or cross-agent reuse. Skip when it is provenance, operational notes, a tool-targeted runbook, or does not claim portability.
- Tidy —
re0 the changed docs so the result reads as a clean v0, not a patch over a draft.
- Apply the findings here, then serve it.
Rules
- Trigger on your OWN output, right after making it — that's when bias is highest and a check is cheapest.
- Use the skills; don't re-implement them —
shower for clarity, factchk/mandela for truth, ssotize for SSOT, detool for portability claims, re0 for cleanup. sip orchestrates and routes findings back to the author session to fix; the skills do the work.
- Skip what plainly doesn't apply, or any check whose skill isn't installed — run only what's present.
factchk/mandela fire only when there is a claim or an eval; detool fires only when the artifact claims portability, tool-neutrality, stack-agnostic durability, or cross-agent reuse; a one-line prose tweak may need only a consistency check. Say what you skipped and why.
- Stop at the artifact —
sip never touches git or makes commits.
- Chain only model-invoked skills; a user-invoked skill (marked
disable-model-invocation) is a human's to fire deliberately, so sip must not call one.
Verification
Before finishing:
- The change was actually run through the relevant skills, not eyeballed.
- Findings were applied (or consciously deferred with a stated reason).
- The artifact actually changed as a result (a diff exists), or every skipped skill has a stated reason.
1---2name: sip3description: After you create or change an artifact or skill, taste-test it with our own skills instead of trusting your in-session judgment — recursive self-improvement, made automatic. Use right after writing or editing anything, before calling it done, committing, or handing it off.4---5
6Taste your own cooking: the moment you finish making something, check it with the very skills this repo ships before you serve it.
7
8## Goal
9
10A reminder buried in docs ("remember to verify") won't reliably fire in a fresh session. `sip` makes the recursive self-improvement loop a triggered habit: right after any create or change, run our own skills on the result — the clean checks and the true ones — so quality doesn't ride on the author's biased in-session judgment.
11
12## Workflow
13
141. Spot the trigger: you just created or changed an artifact or skill and are about to call it done, commit, or hand it off.
152. **Cold-read it** — run `shower` on the artifact (fresh-eyes comprehension / handoff check).
163. **Verify it's true** — if the artifact asserts a reality-grounded claim, run `factchk`; if it defines an eval, metric, or experiment, run `mandela`. Skip when it has neither.
174. **Check consistency** — run `ssotize` in audit mode across the repo for anything the change duplicated or contradicted; execute its consolidation plan only after approval.
185. **Detool portability claims** — run `detool` only when the artifact claims portability, tool-neutrality, stack-agnostic durability, or cross-agent reuse. Skip when it is provenance, operational notes, a tool-targeted runbook, or does not claim portability.
196. **Tidy** — `re0` the changed docs so the result reads as a clean v0, not a patch over a draft.
207. Apply the findings here, then serve it.
21
22## Rules
23
24- Trigger on your OWN output, right after making it — that's when bias is highest and a check is cheapest.
25- Use the skills; don't re-implement them — `shower` for clarity, `factchk`/`mandela` for truth, `ssotize` for SSOT, `detool` for portability claims, `re0` for cleanup. `sip` orchestrates and routes findings back to the author session to fix; the skills do the work.
26- Skip what plainly doesn't apply, or any check whose skill isn't installed — run only what's present. `factchk`/`mandela` fire only when there is a claim or an eval; `detool` fires only when the artifact claims portability, tool-neutrality, stack-agnostic durability, or cross-agent reuse; a one-line prose tweak may need only a consistency check. Say what you skipped and why.
27- Stop at the artifact — `sip` never touches git or makes commits.
28- Chain only model-invoked skills; a user-invoked skill (marked `disable-model-invocation`) is a human's to fire deliberately, so `sip` must not call one.
29
30## Verification
31
32Before finishing:
33
341. The change was actually run through the relevant skills, not eyeballed.
352. Findings were applied (or consciously deferred with a stated reason).
363. The artifact actually changed as a result (a diff exists), or every skipped skill has a stated reason.
lilmgenius