Service Registry

For each external service, prefer MCP first, then CLI, then personal skills, then plugin skills.

Service registry principle: use the highest-ranked interface that can do the job; drop ranks only when higher ones cannot handle the task. Source: Skill Resolver, 2026-05-31

Covered services include Vercel, Stripe, Supabase, Clerk, Firebase, Figma, PostHog, Sentry, Datadog, Linear, Slack, GitHub, AWS, Cloudflare, Browser.

See per-service pages in this category for rank tables.

Routing Scope

This page owns one action-routing shard extracted from Skill Resolver. Keep interface order and trigger boundaries current; use frontmatter related: for sibling routes. Source: wiki quality pass, 2026-06-27

---

Timeline

• 2026-05-31 | Service registry overview split from SKILL-RESOLVER. Source: public wiki expansion, 2026-05-31