cc-skill:build-mcp-app
Claude Code skill · anthropic · active
Deploy this skill
no laptop requiredRun this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.
How this performs
Cloud-automation runs, real outputs, and feedback.
No cloud runs yet for this skill.
Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.
Claude Code skill at /Users/olanrewajukareem/.claude/skills/build-mcp-app/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.
This skill should be used when the user wants to build an "MCP app", add "interactive UI" or "widgets" to an MCP server, "render components in chat", build "MCP UI resources", make a tool that shows a "form", "picker", "dashboard" or "confirmation di
Local Claude Code use (optional)
Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.
Save this skill to ~/.claude/skills/build-mcp-app/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.
{
"source": "global",
"description": "This skill should be used when the user wants to build an \"MCP app\", add \"interactive UI\" or \"widgets\" to an MCP server, \"render components in chat\", build \"MCP UI resources\", make a tool that shows a \"form\", \"picker\", \"dashboard\" or \"confirmation dialog\" inline in the conversation, or mentions \"apps SDK\" in the context of MCP. Use AFTER the build-mcp-server skill has settled the deployment model, or when the user already knows they want UI widgets."
}{
"method": "embed_in_prompt",
"skill_path": "/Users/olanrewajukareem/.claude/skills/build-mcp-app/SKILL.md"
}That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.