Don't publish. Request.

Recipes is a single-publisher catalog. Every skill is curated and maintained by the WiseChef team. We don't take submissions — we take requests.

Tell us what's broken in your fleet, what your team is doing manually that should be automated, or what your agent fails at and we'll ship a skill that fixes it.

Why single-publisher?

Building a publisher trust ladder before publishers exist is wasted work. We want the catalog to be excellent, not large. Every skill on Recipes was authored against a real production failure mode. That's the bar.

• Fewer skills, deeper coverage.
• One quality bar — ours.
• Auto-improve telemetry feeds back into the next version.
• Architecture-aware install means the skill won't crash on your hardware.

How to request a skill

1. Go to /request-skill and submit the form (or DM WiseChef directly).
2. We triage requests by signal: how many fleets would use this, how broken is the alternative, how recurring is the pain.
3. Time-to-skill for matched requests: 7 days for a working install, 14 days for full polish.
4. Studio subscribers get priority + a dedicated review SLA.

What makes a good request

• A real workflow your team runs (or wants to run) repeatedly.
• The hours/week that go into it manually today.
• The failure mode you'd want telemetry on.
• Whether the result needs a UI, a report, an API call, or just a side-effect.

The future of publishing

We may open invitation-only publishing later, with explicit per-publisher agreements and 1:1 onboarding. We will never automate it. If you think you're an exception, tell us.