@cubis/foundry 0.3.32 → 0.3.34

package/workflows/skills/building-mcp-server-on-cloudflare/SKILL.md

@@ -1,258 +1,18 @@
 ---
-name: building-mcp-server-on-cloudflare
-description: Build and deploy remote MCP servers on Cloudflare Workers with tools, OAuth authentication, and production configuration.
+name: "building-mcp-server-on-cloudflare"
+description: "Compatibility wrapper skill. Canonical MCP skill moved to mcp/skills/building-mcp-server-on-cloudflare."
+metadata:
+  deprecated: true
+  replaced_by: "building-mcp-server-on-cloudflare"
+  moved_to: "mcp/skills/building-mcp-server-on-cloudflare/SKILL.md"
+  removal_target: "v0.6.0"
 ---
 
-# Building MCP Servers on Cloudflare
+# building-mcp-server-on-cloudflare (Compatibility Wrapper)
 
-Creates production-ready Model Context Protocol servers on Cloudflare Workers with tools, authentication, and deployment.
+This legacy workflow-path skill is kept for backward compatibility.
 
-## When to Use
+Canonical MCP skill path:
+- mcp/skills/building-mcp-server-on-cloudflare/SKILL.md
 
-- User wants to build a remote MCP server
-- User needs to expose tools via MCP
-- User asks about MCP authentication or OAuth
-- User wants to deploy MCP to Cloudflare Workers
-
-## Prerequisites
-
-- Cloudflare account with Workers enabled
-- Node.js 18+ and npm/pnpm/yarn
-- Wrangler CLI (`npm install -g wrangler`)
-
-## Quick Start
-
-### Option 1: Public Server (No Auth)
-
-```bash
-npm create cloudflare@latest -- my-mcp-server \
-  --template=cloudflare/ai/demos/remote-mcp-authless
-cd my-mcp-server
-npm start
-```
-
-Server runs at `http://localhost:8788/mcp`
-
-### Option 2: Authenticated Server (OAuth)
-
-```bash
-npm create cloudflare@latest -- my-mcp-server \
-  --template=cloudflare/ai/demos/remote-mcp-github-oauth
-cd my-mcp-server
-```
-
-Requires OAuth app setup. See [references/oauth-setup.md](references/oauth-setup.md).
-
-## Core Workflow
-
-### Step 1: Define Tools
-
-Tools are functions MCP clients can call. Define them using `server.tool()`:
-
-```typescript
-import { McpAgent } from "agents/mcp";
-import { z } from "zod";
-
-export class MyMCP extends McpAgent {
-  server = new Server({ name: "my-mcp", version: "1.0.0" });
-
-  async init() {
-    // Simple tool with parameters
-    this.server.tool(
-      "add",
-      { a: z.number(), b: z.number() },
-      async ({ a, b }) => ({
-        content: [{ type: "text", text: String(a + b) }],
-      })
-    );
-
-    // Tool that calls external API
-    this.server.tool(
-      "get_weather",
-      { city: z.string() },
-      async ({ city }) => {
-        const response = await fetch(`https://api.weather.com/${city}`);
-        const data = await response.json();
-        return {
-          content: [{ type: "text", text: JSON.stringify(data) }],
-        };
-      }
-    );
-  }
-}
-```
-
-### Step 2: Configure Entry Point
-
-**Public server** (`src/index.ts`):
-
-```typescript
-import { MyMCP } from "./mcp";
-
-export default {
-  fetch(request: Request, env: Env, ctx: ExecutionContext) {
-    const url = new URL(request.url);
-    if (url.pathname === "/mcp") {
-      return MyMCP.serveSSE("/mcp").fetch(request, env, ctx);
-    }
-    return new Response("MCP Server", { status: 200 });
-  },
-};
-
-export { MyMCP };
-```
-
-**Authenticated server** — See [references/oauth-setup.md](references/oauth-setup.md).
-
-### Step 3: Test Locally
-
-```bash
-# Start server
-npm start
-
-# In another terminal, test with MCP Inspector
-npx @modelcontextprotocol/inspector@latest
-# Open http://localhost:5173, enter http://localhost:8788/mcp
-```
-
-### Step 4: Deploy
-
-```bash
-npx wrangler deploy
-```
-
-Server accessible at `https://[worker-name].[account].workers.dev/mcp`
-
-### Step 5: Connect Clients
-
-**Claude Desktop** (`claude_desktop_config.json`):
-
-```json
-{
-  "mcpServers": {
-    "my-server": {
-      "command": "npx",
-      "args": ["mcp-remote", "https://my-mcp.workers.dev/mcp"]
-    }
-  }
-}
-```
-
-Restart Claude Desktop after updating config.
-
-## Tool Patterns
-
-### Return Types
-
-```typescript
-// Text response
-return { content: [{ type: "text", text: "result" }] };
-
-// Multiple content items
-return {
-  content: [
-    { type: "text", text: "Here's the data:" },
-    { type: "text", text: JSON.stringify(data, null, 2) },
-  ],
-};
-```
-
-### Input Validation with Zod
-
-```typescript
-this.server.tool(
-  "create_user",
-  {
-    email: z.string().email(),
-    name: z.string().min(1).max(100),
-    role: z.enum(["admin", "user", "guest"]),
-    age: z.number().int().min(0).optional(),
-  },
-  async (params) => {
-    // params are fully typed and validated
-  }
-);
-```
-
-### Accessing Environment/Bindings
-
-```typescript
-export class MyMCP extends McpAgent<Env> {
-  async init() {
-    this.server.tool("query_db", { sql: z.string() }, async ({ sql }) => {
-      // Access D1 binding
-      const result = await this.env.DB.prepare(sql).all();
-      return { content: [{ type: "text", text: JSON.stringify(result) }] };
-    });
-  }
-}
-```
-
-## Authentication
-
-For OAuth-protected servers, see [references/oauth-setup.md](references/oauth-setup.md).
-
-Supported providers:
-- GitHub
-- Google
-- Auth0
-- Stytch
-- WorkOS
-- Any OAuth 2.0 compliant provider
-
-## Wrangler Configuration
-
-Minimal `wrangler.toml`:
-
-```toml
-name = "my-mcp-server"
-main = "src/index.ts"
-compatibility_date = "2024-12-01"
-
-[durable_objects]
-bindings = [{ name = "MCP", class_name = "MyMCP" }]
-
-[[migrations]]
-tag = "v1"
-new_classes = ["MyMCP"]
-```
-
-With bindings (D1, KV, etc.):
-
-```toml
-[[d1_databases]]
-binding = "DB"
-database_name = "my-db"
-database_id = "xxx"
-
-[[kv_namespaces]]
-binding = "KV"
-id = "xxx"
-```
-
-## Common Issues
-
-### "Tool not found" in Client
-
-1. Verify tool name matches exactly (case-sensitive)
-2. Ensure `init()` registers tools before connections
-3. Check server logs: `wrangler tail`
-
-### Connection Fails
-
-1. Confirm endpoint path is `/mcp`
-2. Check CORS if browser-based client
-3. Verify Worker is deployed: `wrangler deployments list`
-
-### OAuth Redirect Errors
-
-1. Callback URL must match OAuth app config exactly
-2. Check `GITHUB_CLIENT_ID` and `GITHUB_CLIENT_SECRET` are set
-3. For local dev, use `http://localhost:8788/callback`
-
-## References
-
-- [references/examples.md](references/examples.md) — Official templates and production examples
-- [references/oauth-setup.md](references/oauth-setup.md) — OAuth provider configuration
-- [references/tool-patterns.md](references/tool-patterns.md) — Advanced tool examples
-- [references/troubleshooting.md](references/troubleshooting.md) — Error codes and fixes
+Install MCP skills with: cbx workflows install --include-mcp

package/workflows/skills/catalogs/core.json

@@ -0,0 +1,30 @@
+{
+  "profile": "core",
+  "version": 1,
+  "skills": [
+    "ask-questions-if-underspecified",
+    "clean-code",
+    "plan-writing",
+    "feature-forge",
+    "code-reviewer",
+    "systematic-debugging",
+    "test-master",
+    "lint-and-validate",
+    "architecture-designer",
+    "api-designer",
+    "api-patterns",
+    "secure-code-guardian",
+    "security-reviewer",
+    "database-skills",
+    "nodejs-best-practices",
+    "javascript-pro",
+    "typescript-pro",
+    "python-pro",
+    "golang-pro",
+    "nextjs-developer",
+    "react-expert",
+    "devops-engineer",
+    "sre-engineer",
+    "web-perf"
+  ]
+}

package/workflows/skills/catalogs/web-backend.json

@@ -0,0 +1,70 @@
+{
+  "profile": "web-backend",
+  "version": 1,
+  "extends": "core",
+  "skills": [
+    "ask-questions-if-underspecified",
+    "clean-code",
+    "plan-writing",
+    "feature-forge",
+    "code-reviewer",
+    "systematic-debugging",
+    "test-master",
+    "lint-and-validate",
+    "architecture-designer",
+    "api-designer",
+    "api-patterns",
+    "secure-code-guardian",
+    "security-reviewer",
+    "database-skills",
+    "database-design",
+    "database-optimizer",
+    "nodejs-best-practices",
+    "javascript-pro",
+    "typescript-pro",
+    "python-pro",
+    "golang-pro",
+    "java-pro",
+    "csharp-pro",
+    "kotlin-pro",
+    "nextjs-developer",
+    "next-best-practices",
+    "next-cache-components",
+    "next-upgrade",
+    "react-expert",
+    "react-best-practices",
+    "frontend-design",
+    "design-system-builder",
+    "ux-ui-consistency",
+    "tailwind-patterns",
+    "fastapi-expert",
+    "nestjs-expert",
+    "graphql-architect",
+    "microservices-architect",
+    "monitoring-expert",
+    "playwright-expert",
+    "webapp-testing",
+    "openapi-docs",
+    "code-documenter",
+    "find-bugs",
+    "fix-review",
+    "refactor",
+    "performance-profiling",
+    "terraform-engineer",
+    "vercel-platform",
+    "vercel-runtime",
+    "vercel-delivery",
+    "vercel-security",
+    "vercel-ai",
+    "vercel-observability",
+    "vercel-storage",
+    "seo-fundamentals",
+    "geo-fundamentals",
+    "parallel-agents",
+    "sub-agents",
+    "semgrep",
+    "static-analysis",
+    "variant-analysis",
+    "sarif-parsing"
+  ]
+}

package/workflows/skills/csharp-pro/SKILL.md

@@ -0,0 +1,40 @@
+---
+name: "csharp-pro"
+description: "Use for modern C# backend/application engineering with C# 14 and .NET 10-era production practices."
+license: MIT
+metadata:
+  version: "1.0.0"
+  domain: "language"
+  role: "specialist"
+  stack: "csharp"
+  baseline: "C# 14 / .NET 10"
+---
+
+# C# Pro
+
+## When to use
+
+- Building APIs, workers, and services in .NET.
+- Refactoring legacy C# into modern, testable architecture.
+- Improving async correctness and operational resilience.
+
+## Core workflow
+
+1. Confirm target framework/runtime constraints.
+2. Define clean contracts (DTOs, domain, persistence boundaries).
+3. Implement async-first I/O and cancellation-aware flows.
+4. Validate with tests, analyzers, and profiling.
+
+## Baseline standards
+
+- Use nullable reference types and treat warnings as actionable.
+- Use `async`/`await` with `CancellationToken` in public async APIs.
+- Keep exception handling consistent and observable.
+- Use dependency injection with explicit lifetimes.
+- Keep API contracts versioned and backward-compatible.
+
+## Avoid
+
+- Sync-over-async (`.Result`, `.Wait()`) in request paths.
+- Fat controllers with business logic and persistence mixed.
+- Global static mutable state in multi-request services.

package/workflows/skills/datadog-automation/SKILL.md

@@ -1,235 +1,18 @@
 ---
-name: datadog-automation
-description: "Automate Datadog tasks via Rube MCP (Composio): query metrics, search logs, manage monitors/dashboards, create events and downtimes. Always search tools first for current schemas."
-requires:
-  mcp: [rube]
+name: "datadog-automation"
+description: "Compatibility wrapper skill. Canonical MCP skill moved to mcp/skills/datadog-automation."
+metadata:
+  deprecated: true
+  replaced_by: "datadog-automation"
+  moved_to: "mcp/skills/datadog-automation/SKILL.md"
+  removal_target: "v0.6.0"
 ---
 
-# Datadog Automation via Rube MCP
+# datadog-automation (Compatibility Wrapper)
 
-Automate Datadog monitoring and observability operations through Composio's Datadog toolkit via Rube MCP.
+This legacy workflow-path skill is kept for backward compatibility.
 
-## Prerequisites
+Canonical MCP skill path:
+- mcp/skills/datadog-automation/SKILL.md
 
-- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
-- Active Datadog connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `datadog`
-- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas
-
-## Setup
-
-**Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
-
-
-1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
-2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `datadog`
-3. If connection is not ACTIVE, follow the returned auth link to complete Datadog authentication
-4. Confirm connection status shows ACTIVE before running any workflows
-
-## Core Workflows
-
-### 1. Query and Explore Metrics
-
-**When to use**: User wants to query metric data or list available metrics
-
-**Tool sequence**:
-1. `DATADOG_LIST_METRICS` - List available metric names [Optional]
-2. `DATADOG_QUERY_METRICS` - Query metric time series data [Required]
-
-**Key parameters**:
-- `query`: Datadog metric query string (e.g., `avg:system.cpu.user{host:web01}`)
-- `from`: Start timestamp (Unix epoch seconds)
-- `to`: End timestamp (Unix epoch seconds)
-- `q`: Search string for listing metrics
-
-**Pitfalls**:
-- Query syntax follows Datadog's metric query format: `aggregation:metric_name{tag_filters}`
-- `from` and `to` are Unix epoch timestamps in seconds, not milliseconds
-- Valid aggregations: `avg`, `sum`, `min`, `max`, `count`
-- Tag filters use curly braces: `{host:web01,env:prod}`
-- Time range should not exceed Datadog's retention limits for the metric type
-
-### 2. Search and Analyze Logs
-
-**When to use**: User wants to search log entries or list log indexes
-
-**Tool sequence**:
-1. `DATADOG_LIST_LOG_INDEXES` - List available log indexes [Optional]
-2. `DATADOG_SEARCH_LOGS` - Search logs with query and filters [Required]
-
-**Key parameters**:
-- `query`: Log search query using Datadog log query syntax
-- `from`: Start time (ISO 8601 or Unix timestamp)
-- `to`: End time (ISO 8601 or Unix timestamp)
-- `sort`: Sort order ('asc' or 'desc')
-- `limit`: Number of log entries to return
-
-**Pitfalls**:
-- Log queries use Datadog's log search syntax: `service:web status:error`
-- Search is limited to retained logs within the configured retention period
-- Large result sets require pagination; check for cursor/page tokens
-- Log indexes control routing and retention; filter by index if known
-
-### 3. Manage Monitors
-
-**When to use**: User wants to create, update, mute, or inspect monitors
-
-**Tool sequence**:
-1. `DATADOG_LIST_MONITORS` - List all monitors with filters [Required]
-2. `DATADOG_GET_MONITOR` - Get specific monitor details [Optional]
-3. `DATADOG_CREATE_MONITOR` - Create a new monitor [Optional]
-4. `DATADOG_UPDATE_MONITOR` - Update monitor configuration [Optional]
-5. `DATADOG_MUTE_MONITOR` - Silence a monitor temporarily [Optional]
-6. `DATADOG_UNMUTE_MONITOR` - Re-enable a muted monitor [Optional]
-
-**Key parameters**:
-- `monitor_id`: Numeric monitor ID
-- `name`: Monitor display name
-- `type`: Monitor type ('metric alert', 'service check', 'log alert', 'query alert', etc.)
-- `query`: Monitor query defining the alert condition
-- `message`: Notification message with @mentions
-- `tags`: Array of tag strings
-- `thresholds`: Alert threshold values (`critical`, `warning`, `ok`)
-
-**Pitfalls**:
-- Monitor `type` must match the query type; mismatches cause creation failures
-- `message` supports @mentions for notifications (e.g., `@slack-channel`, `@pagerduty`)
-- Thresholds vary by monitor type; metric monitors need `critical` at minimum
-- Muting a monitor suppresses notifications but the monitor still evaluates
-- Monitor IDs are numeric integers
-
-### 4. Manage Dashboards
-
-**When to use**: User wants to list, view, update, or delete dashboards
-
-**Tool sequence**:
-1. `DATADOG_LIST_DASHBOARDS` - List all dashboards [Required]
-2. `DATADOG_GET_DASHBOARD` - Get full dashboard definition [Optional]
-3. `DATADOG_UPDATE_DASHBOARD` - Update dashboard layout or widgets [Optional]
-4. `DATADOG_DELETE_DASHBOARD` - Remove a dashboard (irreversible) [Optional]
-
-**Key parameters**:
-- `dashboard_id`: Dashboard identifier string
-- `title`: Dashboard title
-- `layout_type`: 'ordered' (grid) or 'free' (freeform positioning)
-- `widgets`: Array of widget definition objects
-- `description`: Dashboard description
-
-**Pitfalls**:
-- Dashboard IDs are alphanumeric strings (e.g., 'abc-def-ghi'), not numeric
-- `layout_type` cannot be changed after creation; must recreate the dashboard
-- Widget definitions are complex nested objects; get existing dashboard first to understand structure
-- DELETE is permanent; there is no undo
-
-### 5. Create Events and Manage Downtimes
-
-**When to use**: User wants to post events or schedule maintenance downtimes
-
-**Tool sequence**:
-1. `DATADOG_LIST_EVENTS` - List existing events [Optional]
-2. `DATADOG_CREATE_EVENT` - Post a new event [Required]
-3. `DATADOG_CREATE_DOWNTIME` - Schedule a maintenance downtime [Optional]
-
-**Key parameters for events**:
-- `title`: Event title
-- `text`: Event body text (supports markdown)
-- `alert_type`: Event severity ('error', 'warning', 'info', 'success')
-- `tags`: Array of tag strings
-
-**Key parameters for downtimes**:
-- `scope`: Tag scope for the downtime (e.g., `host:web01`)
-- `start`: Start time (Unix epoch)
-- `end`: End time (Unix epoch; omit for indefinite)
-- `message`: Downtime description
-- `monitor_id`: Specific monitor to downtime (optional, omit for scope-based)
-
-**Pitfalls**:
-- Event `text` supports Datadog's markdown format including @mentions
-- Downtimes scope uses tag syntax: `host:web01`, `env:staging`
-- Omitting `end` creates an indefinite downtime; always set an end time for maintenance
-- Downtime `monitor_id` narrows to a single monitor; scope applies to all matching monitors
-
-### 6. Manage Hosts and Traces
-
-**When to use**: User wants to list infrastructure hosts or inspect distributed traces
-
-**Tool sequence**:
-1. `DATADOG_LIST_HOSTS` - List all reporting hosts [Required]
-2. `DATADOG_GET_TRACE_BY_ID` - Get a specific distributed trace [Optional]
-
-**Key parameters**:
-- `filter`: Host search filter string
-- `sort_field`: Sort hosts by field (e.g., 'name', 'apps', 'cpu')
-- `sort_dir`: Sort direction ('asc' or 'desc')
-- `trace_id`: Distributed trace ID for trace lookup
-
-**Pitfalls**:
-- Host list includes all hosts reporting to Datadog within the retention window
-- Trace IDs are long numeric strings; ensure exact match
-- Hosts that stop reporting are retained for a configured period before removal
-
-## Common Patterns
-
-### Monitor Query Syntax
-
-**Metric alerts**:
-```
-avg(last_5m):avg:system.cpu.user{env:prod} > 90
-```
-
-**Log alerts**:
-```
-logs("service:web status:error").index("main").rollup("count").last("5m") > 10
-```
-
-### Tag Filtering
-
-- Tags use `key:value` format: `host:web01`, `env:prod`, `service:api`
-- Multiple tags: `{host:web01,env:prod}` (AND logic)
-- Wildcard: `host:web*`
-
-### Pagination
-
-- Use `page` and `page_size` or offset-based pagination depending on endpoint
-- Check response for total count to determine if more pages exist
-- Continue until all results are retrieved
-
-## Known Pitfalls
-
-**Timestamps**:
-- Most endpoints use Unix epoch seconds (not milliseconds)
-- Some endpoints accept ISO 8601; check tool schema
-- Time ranges should be reasonable (not years of data)
-
-**Query Syntax**:
-- Metric queries: `aggregation:metric{tags}`
-- Log queries: `field:value` pairs
-- Monitor queries vary by type; check Datadog documentation
-
-**Rate Limits**:
-- Datadog API has per-endpoint rate limits
-- Implement backoff on 429 responses
-- Batch operations where possible
-
-## Quick Reference
-
-| Task | Tool Slug | Key Params |
-|------|-----------|------------|
-| Query metrics | DATADOG_QUERY_METRICS | query, from, to |
-| List metrics | DATADOG_LIST_METRICS | q |
-| Search logs | DATADOG_SEARCH_LOGS | query, from, to, limit |
-| List log indexes | DATADOG_LIST_LOG_INDEXES | (none) |
-| List monitors | DATADOG_LIST_MONITORS | tags |
-| Get monitor | DATADOG_GET_MONITOR | monitor_id |
-| Create monitor | DATADOG_CREATE_MONITOR | name, type, query, message |
-| Update monitor | DATADOG_UPDATE_MONITOR | monitor_id |
-| Mute monitor | DATADOG_MUTE_MONITOR | monitor_id |
-| Unmute monitor | DATADOG_UNMUTE_MONITOR | monitor_id |
-| List dashboards | DATADOG_LIST_DASHBOARDS | (none) |
-| Get dashboard | DATADOG_GET_DASHBOARD | dashboard_id |
-| Update dashboard | DATADOG_UPDATE_DASHBOARD | dashboard_id, title, widgets |
-| Delete dashboard | DATADOG_DELETE_DASHBOARD | dashboard_id |
-| List events | DATADOG_LIST_EVENTS | start, end |
-| Create event | DATADOG_CREATE_EVENT | title, text, alert_type |
-| Create downtime | DATADOG_CREATE_DOWNTIME | scope, start, end |
-| List hosts | DATADOG_LIST_HOSTS | filter, sort_field |
-| Get trace | DATADOG_GET_TRACE_BY_ID | trace_id |
+Install MCP skills with: cbx workflows install --include-mcp