sip
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.
- Installs
- 1.3K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/lilmgenius/paperthin --skill sip- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads sip automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
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
showeron 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, runmandela. Skip when it has neither. - Check consistency — run
ssotizein audit mode across the repo for anything the change duplicated or contradicted; execute its consolidation plan only after approval. - Detool portability claims — run
detoolonly 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 —
re0the 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 —
showerfor clarity,factchk/mandelafor truth,ssotizefor SSOT,detoolfor portability claims,re0for cleanup.siporchestrates 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/mandelafire only when there is a claim or an eval;detoolfires 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 —
sipnever 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, sosipmust 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.
FAQ
What does the sip skill do?
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.
How do I install sip?
Run npx skills add https://github.com/lilmgenius/paperthin --skill sip in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/sip/ (personal) or .claude/skills/sip/ (project).
Which AI agents can use sip?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is sip safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains sip?
It is published by lilmgenius in lilmgenius/paperthin. It has 1,300 recorded installs.
More from lilmgenius/paperthin
dedash
lilmgenius/paperthin
Remove em-dashes and the dashes standing in for them from a user-owned scope, reading each occurrence in context and choosing the punctuation or wording that fits.
ssotize
lilmgenius/paperthin
Audit and consolidate a fact that's scattered across places into one canonical source, after approval, and replace the rest with references. Use when asked to find duplication, check consistency, locate the source of truth, deduplicate, consolidate, unify, or establish SSOT across artifacts or platforms. Starts read-only, reports the map and plan, then mutates only after explicit approval.
shower
lilmgenius/paperthin
Cold-read the artifact you're focused on from a fresh, zero-context sub-session to confirm it stands on its own — a shower-thought reset for accumulated session bias. Use when a long session has worn away your fresh eyes and you can no longer tell whether the artifact in focus is clear to someone with no prior context; before a handoff, publish, or merge; or when you want a clean-room comprehension smoke test. Spawns a separate context-free reviewer; it diagnoses, it does not fix.
hate
lilmgenius/paperthin
Attack a plan, design, or argument like you want it to fail before you commit real effort — return the single load-bearing objection and the cheapest experiment that would prove it matters, not a checklist. User-invoked on purpose: a hate-it reflex always in the agent's reach would bias it toward demolition. Weighs many failure axes but owns the synthesis to one root.
factchk
lilmgenius/paperthin
Verify reality-grounded claims against external sources in both directions before they ship — could the 'absurd' be real, could the 'obvious' be false or long-established? Use whenever an artifact, or the sentence you are about to write, asserts something as plausible, realistic, absurd, novel, or impossible from intuition rather than a checked source; before relying on a factual claim in prose, a design rationale, a research claim, or a plan. Fires on metacognitive doubt — when you can't actually know, verify instead of trusting the feeling. Scans read-only, then fixes the clear errors or flags the judgment calls; leaves deliberate fiction alone.
re0
lilmgenius/paperthin
Refresh an existing artifact into the current best v0. Use when the user asks to clean up, sync up, dedupe, de-noise, smooth, rewrite, or update an artifact after iteration; when nearby artifacts may have drifted; or when changes in one place should be reflected across related artifacts while keeping the result minimal.
Popular testing & qa skills
tdd
mattpocock/skills
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
grilling
mattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
migrate-to-shoehorn
mattpocock/skills
Migrate test files from as type assertions to @total-typescript/shoehorn. Use when user mentions shoehorn, wants to replace as in tests, or needs partial test data.
run-train
lllllllama/rigorpilot-skills
Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized trainoutputs/. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.
test-driven-development
obra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
finishing-a-development-branch
obra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work