Skip to content

Pricing
Blog

Sign in Get started

Site footer

Spend less on every AI request. Safe before it leaves, explained after.

curl -LsSf https://opensmartroute.ai/install.sh | sh

Apache-2.0v1.8.0enterprise edition

The daily newsletter

Models, LLMs and agents, one email a day. Confirm by email; leave with one click.

Email address

Product

Solutions
Services
Models
Marketplace
Playground
Browser extension
Desktop app
Security
Observability
Enterprise
Pricing

Developers

SDKs and API
Documentation
REST API
Python SDK
TypeScript SDK
MCP server
Self-hosting
Downloads

Company

Blog
Newsletter
Changelog
Support
Talk to sales
Status
PyPI
npm

OpenSmartRouteCopyright 2026 the OpenSmartRoute contributors. Open source under Apache-2.0.

Terms Privacy Report a vulnerability

Support assistant

Connecting...

Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.

Grounded in the docs - follow a source before acting on it.

Marketplace/Skills

Skills that teach a model one job well

Step-by-step SKILL.md packages an AI follows for a single kind of task.

A skill is a focused playbook - instructions, examples and constraints - that makes any model reliable at one job, from SQL reporting to changelog writing. The router fills a plan's skill slot with the best match for the request.

164.4K SkillsPublish yours

One job, done consistently
Model-agnostic instructions
Composable into plans

Agents6.8K Personas6.8K Prompts19.5K Templates32 Tools33.7K Models

164419 results

455

create-verification-skill

Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", "

by michael-denyerskills.sh

Not rated yet

Free

deslop

Remove AI-generated code slop and clean up code style

by michael-denyerskills.sh

figure-it-out

Design an auditable playbook when no narrower one fits: a large migration, an ambitious multi-part change, or work a human reviews after stepping away. Scales rigor to the task, runs a hypothesis loop

by michael-denyerskills.sh

fix-ci

Find failing PR checks, inspect logs or external check links, and apply focused fixes

by michael-denyerskills.sh

fix-merge-conflicts

Resolve merge conflicts non-interactively, validate build and tests, and finalize conflict resolution

by michael-denyerskills.sh

get-pr-comments

Fetch and summarize review comments from the active pull request

by michael-denyerskills.sh

how

Use for "how does X work", code walkthroughs before changing something, and placement / ownership / layering questions ("where should this live", "which package owns this", "is this the right layer").

by michael-denyerskills.sh

interrogate

Use for "interrogate", "adversarial review", "multi-model review", "challenge this", "stress test this code", "find blind spots", or "tear this apart". Multiple LLM reviewers challenge changes from in

by michael-denyerskills.sh

maintain-verification-skill

Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use f

by michael-denyerskills.sh

make-pr-easy-to-review

Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up

by michael-denyerskills.sh

no-comments

Spawn the comment-sicko subagent, fix accepted findings, and offer encodings for claimed constraints.

by michael-denyerskills.sh

poteto-mode

poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

by michael-denyerskills.sh

principle-attack-the-premise

Apply when repeated fixes sharing an assumption fail. State the assumption and choose an observation that can challenge it before trying another fix that depends on it.

by michael-denyerskills.sh

principle-boundary-discipline

Apply when wiring validation, error handling, or framework adapters. Concentrate guards at system boundaries (CLI, config, network, external APIs); trust internal types and keep business logic in pure

by michael-denyerskills.sh

principle-build-the-lever

Apply to any non-trivial work, not just bulk work: edits, migrations, analyses, checks. Build the tool that does it or proves it (codemod, script, generator, or a skill your subagents follow) instead

by michael-denyerskills.sh

principle-encode-lessons-in-structure

Apply when you catch yourself writing the same instruction a second time, or notice a recurring correction. Encode the rule as a lint, metadata flag, runtime check, or script instead of more text.

by michael-denyerskills.sh

principle-exhaust-the-design-space

Apply when facing a novel UI interaction or architectural decision with no precedent in the codebase. Build 2-3 competing prototypes and compare side by side before committing.

by michael-denyerskills.sh

principle-experience-first

Apply when product, UX, or feature-scope tradeoffs come up. Choose user delight over implementation convenience; ship fewer polished features over more rough ones.

by michael-denyerskills.sh

principle-fix-root-causes

Apply when debugging. Trace each symptom to its root cause and fix it there; reproduce first, ask why until you reach it, resist nil-check guards that silence crashes.

by michael-denyerskills.sh

principle-foundational-thinking

Apply before writing logic: choosing core types and data structures, sequencing scaffold-vs-feature work, asking what concurrent actors share. Get the data structures right so downstream code becomes

by michael-denyerskills.sh

principle-guard-the-context-window

Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.

by michael-denyerskills.sh

principle-laziness-protocol

Apply when refactoring, evaluating diff size, or tempted to add abstractions, layers, or signal threading. Bias toward deletion and the smallest change that solves the problem.

by michael-denyerskills.sh

principle-make-operations-idempotent

Apply when designing commands, lifecycle steps, or processing loops that run amid crashes, restarts, and retries. Converge to the same end state regardless of partial prior runs.

by michael-denyerskills.sh

principle-migrate-callers-then-delete-legacy-apis

Apply when introducing a new internal API while old callers still exist. Migrate callers and delete the old API in the same wave instead of preserving compatibility layers.

by michael-denyerskills.sh

1
225
226
227
228
229
6851