smithery-ai

Build and edit the Smithery homepage app -- a TanStack Start + shadcn/ui web app at ~/.smithery/homepage that connects to MCP servers through the Smithery Connect API. Use this skill whenever the user wants to create, modify, or add features to the Smithery homepage, build pages that display data from MCP tools (Linear issues, Gmail, Notion, etc.), or asks about editing anything in ~/.smithery/homepage. Also triggers for requests like 'add a page to the homepage', 'show my Linear issues on the homepage', 'update the homepage UI', or any task involving the ~/.smithery/homepage project.

Find, connect, and use MCP tools and skills via the Smithery CLI. Use when the user searches for new tools or skills, wants to discover integrations, connect to an MCP, install a skill, or wants to interact with an external service (email, Slack, Discord, GitHub, Jira, Notion, databases, cloud APIs, monitoring, etc.).

Authoring and diagnosing code in the agentjsx codebase (npm package `@flamecast/agentjsx`, locally at `/Users/arjun/Documents/github/effectctx`). The library lets you define an agent as a JSX tree — capability components install tools, block components emit prompt content, shaper components transform via `renderChildren`. Use whenever the user is writing new components (capability, content, or shaper), adding a new extension, debugging the render walk or tool reconciler, asking how a piece of agentjsx works internally, or referencing JSX patterns like `useRenderContext`, `runEffect`, `emitTool`, `emitFragment`, `renderChildren`. Also trigger on filenames in `src/jsx/`, `src/core/`, `src/platforms/`, `src/extensions/`, or any task touching `@flamecast/agentjsx` imports. Use proactively when you see `createAgentRuntime`, `<Workspace>`, `<Compact>`, `<McpServer>`, `<Skills>`, `<Todo>`, or any other agentjsx component in code — that's the strong signal you should consult this skill before authoring more.

Diagnose and improve Effect-TS code against canonical patterns. Use whenever the user is writing, reviewing, refactoring, or debugging code that imports from `effect`, `@effect/*`, or a project built on Effect (like effectctx). Covers Layer composition, Service/Context.Tag, error channels with Data.TaggedError, Scope and resource management, Stream/Queue/PubSub, Schema decoding at boundaries, fiber management, tracing with withSpan, and the anti-patterns that experienced Effect users keep flagging (missing `yield*`, unbounded concurrency, providing Layers twice, accessor R-leakage, etc.). Trigger on phrases like "review my Effect code", "is this idiomatic Effect", "audit the Layer composition", "why is this fiber not interrupting", "what's the right error type here", "convert this Promise code to Effect", or any task that involves writing non-trivial Effect-TS code where idiom matters.

Authenticate with any OAuth 2.1 MCP server. Handles discovery, PKCE, dynamic client registration, local callback server, token exchange, and authenticated requests. Use when connecting to OAuth-protected MCP servers, testing MCP tools, or debugging auth flows. Accepts an MCP server URL as argument.

Start the Unicorn or Bust game. Use this skill when a user wants to play the Unicorn or Bust game - a choose your own adventure game where you play as a startup founder navigating challenges to build a unicorn. The game is powered by the unicorn-or-bust MCP server with dynamic challenges, resource management (runway, morale, product, investor hype), and stat progression.

Set up agent.pw credential management in agent applications. Use when adding credential storage, OAuth flows, API key management, or auth header resolution to an agent platform. Triggers on "set up agent.pw", "add agent.pw", "integrate agent.pw", "credential management", "store credentials", "OAuth for agents", "connect external APIs", or when building agent apps that need to call authenticated external APIs on behalf of users.

How to use the mcp-to-cli command-line tool to connect to remote MCP servers and interact with their tools, resources, and prompts. Use this skill whenever the user wants to connect to an MCP server from the terminal, call MCP tools via CLI, manage MCP connections, list or invoke tools/resources/prompts on a remote server, or debug MCP server interactions. Also use this when the user mentions "mcp-to-cli", asks about CLI-based MCP workflows, or wants to script MCP tool calls.

MCP OAuth compliance simulator — walks the exact path a real client would (unauthenticated probe → 401 challenge → discovery → registration → authorization → token exchange → MCP calls) and reports spec compliance at each step. Use when investigating auth failures, testing server compliance, or onboarding new OAuth MCP servers. Triggers on "debug oauth", "test oauth flow", "oauth compliance", "oauth-debug", "why is auth failing".

Get an independent opinion from OpenAI Codex CLI (GPT 5.4 model) on a design decision, code review, or debugging hypothesis. Use when you want a second opinion from a different model, need to challenge your own approach, or want to validate a fix before committing. Triggers: "ask codex", "get codex opinion", "what does codex think", "second opinion", or when /ask-council invokes it.