/mcp-oauth-doctor:mcp-oauth-doctor runs the doctor against an MCP server URL and explains the first broken sign-in step (401 challenge, protected-resource metadata, authorization-server discovery, client registration), whose it is — the server, its identity provider or a known client bug — and the fix, per client.
Create new skills, modify and improve existing skills, and measure skill performance. Runs a guided interview to scope new skills and helps choose an orchestration architecture (inline, forked subagent, dynamic workflow, or agent team). Use when users want to create a skill from scratch, update or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Host adapters for CodeRifts: Claude Code PreToolUse asks before Write/Edit of OpenAPI, AsyncAPI, GraphQL, protobuf, or MCP manifest files. Not the GitHub Action (coderifts/contract-gate) and not the guard library (@coderifts/agent-guard).
Architects Swift server backends as gRPC microservices behind a Hummingbird gateway, one Swift package per service, with Postgres row-level security, Valkey and Temporal workflows. Use when planning a Swift backend or splitting it into services, adding a service, endpoint, use case, repository, migration, webhook, multi-tenant table, background job or durable Temporal workflow, drawing a Swift server's module boundaries or writing its Package.swift, wiring configuration, graceful shutdown, mTLS or JWT auth, naming server types and targets, setting up a server package's tests, CI/CD or deployment, or reviewing a Swift server's architecture or code style. Not for iOS, macOS or SwiftUI apps. Applies even when the user doesn't name the architecture.
IoT and embedded work done safely: identify the board and its voltages before wiring, back up flash before flashing, MQTT and OTA with authentication and a way back, and proof on the real device before 'done'.
PLC, industrial automation and robotics with safety first: safety functions stay with qualified engineers, programs are backed up from the PLC before editing, simulation before site, Modbus/OPC UA done right, commissioning evidence.
Research with integrity: every reference verified to exist (DOI, Crossref, OpenAlex, PubMed, arXiv), accurate quotes and numbers, reproducible analysis, sound statistics, ethics and AI-use disclosure.
Coding practices that apply on any host: design and clarity over expediency, security first, comment discipline, logging, and verifying what you don't know. No hooks, no forge.
Cross-provider development loop: independent plan review, delegated build, and independent final inspection across Claude Code, Codex, Kimi Code, DeepSeek Harness and qwen-code.
Lavish extension: /lavish-ext:code-walkthrough turns a PR, branch, or diff into a plain-words, step-by-step walkthrough page (Overview, then Step 1..N with the code and why). Requires the lavish skill.