saucekit

Check

One-screen verdict block: Before / After / Better because, classification, pattern, then the verdict with a concrete route.

Get /check See example

"The default is no. This makes the yes earn it."

Luke Toledo

You ask, skill returns

Your request

@example

Should I add dark mode to my SaaS before launch? Feels unprofessional without it.

Skill output

Before: you ship without dark mode. After: launch slips a week for a toggle nobody asked for. Better because: it is not - no user requested it and zero revenue depends on it. Classification: nice-to-have. Pattern: one-off. Verdict: Defer - park it with a revisit condition: first paying user who asks. Route: write it down with that condition and ship without it.

Who this is for

Idea triage

Mid-session idea pops up. Check it before it becomes a detour.

Agent proposal filter

Claude or Codex suggests something plausible. Find out if it serves the business or just sounds good.

Backlog cleanup

Run stale roadmap entries through the filter. Most die. The survivors get sharper.

How It Works

  1. 1

    Get skill

    Open access from the creator page.

  2. 2

    Paste one command

    Install the Saucekit skill locally.

  3. 3

    Run the slash command

    Use /check inside Claude Code.

FAQ

Do I see the private rules?

No. Saucekit runs them server-side and returns the verdict.

Can it browse or run tools?

No. One-shot judgment: idea in, verdict out.

What if I disagree with the verdict?

Good - it forced you to articulate why. Overriding with a reason is the filter working.

Do I see the creator's private rules?

No. Saucekit runs the method server-side. You only receive the final answer.

What does it install?

A Claude Code slash command for Check.

What should I ask it?

Start with this: Paste your last shiny idea and let it fight for its life.

Try /check on a real request.

Start with the image you already need. The skill gives you a stronger direction before you spend the next hour tweaking.

Get /check