@frontmcp/skills 1.0.3 → 1.1.0-beta.1

package/catalog/skills-manifest.json

@@ -364,6 +364,77 @@
           "name": "setup-sqlite",
           "description": "Cross-reference to the full SQLite configuration guide in frontmcp-setup",
           "examples": []
+        },
+        {
+          "name": "configure-deployment-targets",
+          "description": "Configure multi-target builds with frontmcp.config.ts for node, distributed, vercel, lambda, cloudflare, browser, cli, and sdk targets",
+          "examples": [
+            {
+              "name": "multi-target-with-security",
+              "description": "Configure a FrontMCP project with node + distributed targets, CSP headers, and HSTS",
+              "level": "intermediate",
+              "tags": ["config", "deployment", "csp", "security", "distributed", "hsts", "multi-target"],
+              "features": [
+                "Using defineConfig() for typed configuration with IDE autocomplete",
+                "Multi-target deployments with per-target server settings",
+                "CSP directives including value-less directives like upgrade-insecure-requests",
+                "Security headers (HSTS, X-Frame-Options, X-Content-Type-Options)",
+                "HA configuration for the distributed target"
+              ]
+            },
+            {
+              "name": "distributed-ha-config",
+              "description": "Configure a distributed deployment target with HA settings for heartbeat, session takeover, and Redis-backed session persistence",
+              "level": "advanced",
+              "tags": ["config", "deployment", "distributed", "ha", "redis", "heartbeat", "session-takeover"],
+              "features": [
+                "Configuring the distributed deployment target with HA options",
+                "Setting custom heartbeat intervals and TTL for pod liveness detection",
+                "Combining server config (CSP, cookies) with HA config in the same target",
+                "Using per-target environment variables for Redis connection"
+              ]
+            },
+            {
+              "name": "json-schema-ide-support",
+              "description": "Use frontmcp.config.json with JSON Schema for VS Code and WebStorm autocomplete",
+              "level": "basic",
+              "tags": ["config", "deployment", "json", "schema", "ide", "autocomplete"],
+              "features": [
+                "Adding $schema field for IDE autocomplete in JSON config files",
+                "Configuring multiple deployment targets in JSON format",
+                "Using the frontmcp.schema.json for property validation and hover docs"
+              ]
+            }
+          ]
+        },
+        {
+          "name": "configure-security-headers",
+          "description": "Configure CSP, HSTS, X-Frame-Options, and X-Content-Type-Options via frontmcp.config server settings",
+          "examples": [
+            {
+              "name": "csp-report-only",
+              "description": "Test CSP policies in report-only mode to identify violations before enforcement",
+              "level": "basic",
+              "tags": ["config", "csp", "security", "report-only", "headers"],
+              "features": [
+                "Enabling CSP in report-only mode with reportUri for violation monitoring",
+                "Using the object-format directives in frontmcp.config",
+                "Verifying report-only header is emitted instead of enforcement header"
+              ]
+            },
+            {
+              "name": "full-production-headers",
+              "description": "Complete security headers configuration for production with CSP enforcement, HSTS preload, and clickjacking protection",
+              "level": "intermediate",
+              "tags": ["config", "csp", "security", "hsts", "production", "headers", "frame-options"],
+              "features": [
+                "Full CSP enforcement with multiple directive types including value-less directives",
+                "HSTS with preload and includeSubDomains for HTTPS enforcement",
+                "X-Frame-Options DENY for clickjacking protection",
+                "Custom headers for additional security controls"
+              ]
+            }
+          ]
         }
       ]
     },
@@ -441,6 +512,23 @@
             }
           ]
         },
+        {
+          "name": "build-for-mcpb",
+          "description": "Package a FrontMCP server as a .mcpb archive that Claude Desktop and other MCPB-aware clients install with one click",
+          "examples": [
+            {
+              "name": "mcpb-bundle-build",
+              "description": "Produce a .mcpb archive for Claude Desktop with metadata, tools, and install-time user_config.",
+              "level": "basic",
+              "tags": ["deployment", "mcpb", "bundle", "claude-desktop", "user-config"],
+              "features": [
+                "Using `frontmcp build --target mcpb` to produce a single `.mcpb` archive",
+                "Translating `setup.steps` into MCPB `user_config` + `${user_config.KEY}` env bindings",
+                "Validating the archive round-trip with `frontmcp mcpb validate`"
+              ]
+            }
+          ]
+        },
         {
           "name": "build-for-sdk",
           "description": "Build a FrontMCP server as an embeddable library with create() and connect() APIs",
@@ -691,6 +779,48 @@
               ]
             }
           ]
+        },
+        {
+          "name": "mcp-client-integration",
+          "description": "Configure MCP clients (Claude Desktop, Claude Code, Cursor, VS Code) to connect to a FrontMCP server via stdio, HTTP, or Unix socket",
+          "examples": [
+            {
+              "name": "stdio-npx",
+              "description": "Publish a FrontMCP server to npm and configure MCP clients to use it with npx --stdio.",
+              "level": "basic",
+              "tags": ["deployment", "stdio", "npx", "npm", "mcp-client", "claude-code", "claude-desktop"],
+              "features": [
+                "Building a FrontMCP server as a distributable CLI bundle",
+                "Configuring package.json bin field for npx execution",
+                "Setting up Claude Code, Claude Desktop, and Cursor to use the server via stdio",
+                "Passing environment variables from MCP client config to the server"
+              ]
+            },
+            {
+              "name": "http-remote",
+              "description": "Connect an MCP client to a FrontMCP server running as an HTTP server, locally or remotely.",
+              "level": "basic",
+              "tags": ["deployment", "http", "mcp-client", "remote", "cloud", "production"],
+              "features": [
+                "Connecting to a local FrontMCP dev server on a custom port",
+                "Connecting to a remote production FrontMCP server with authentication",
+                "Configuring HTTP transport in Claude Code and Claude Desktop",
+                "Using a background daemon on a TCP port for persistent local access"
+              ]
+            },
+            {
+              "name": "stdio-binary-with-env",
+              "description": "Configure a local FrontMCP CLI binary with environment variables and custom arguments in MCP client configs.",
+              "level": "intermediate",
+              "tags": ["deployment", "stdio", "cli", "binary", "env", "mcp-client", "configuration"],
+              "features": [
+                "Pointing MCP clients at a locally installed FrontMCP binary",
+                "Passing database URLs, API keys, and feature flags via environment variables",
+                "Using absolute paths for reliable binary resolution",
+                "Configuring different environments (dev, staging) via env vars"
+              ]
+            }
+          ]
         }
       ]
     },
@@ -1348,8 +1478,25 @@
         },
         {
           "name": "official-adapters",
-          "description": "Convert OpenAPI specs and external definitions into MCP tools automatically",
+          "description": "Overview of all official FrontMCP adapters that convert external definitions into MCP primitives",
+          "examples": []
+        },
+        {
+          "name": "openapi-adapter",
+          "description": "Convert OpenAPI 3.x specifications into MCP tools with authentication, polling, transforms, format resolution, and $ref security",
           "examples": [
+            {
+              "name": "basic-openapi-adapter",
+              "description": "Demonstrates converting an OpenAPI specification into MCP tools automatically using `OpenapiAdapter` with minimal configuration.",
+              "level": "basic",
+              "tags": ["development", "openapi", "adapters", "adapter"],
+              "features": [
+                "Using `OpenapiAdapter.init()` with just `name` and `url` to auto-generate MCP tools",
+                "Each OpenAPI operation becomes a tool named `<adapter-name>:<operationId>`",
+                "The adapter is registered in the `adapters` array of `@App`, not in `plugins`",
+                "The `name` field serves as the namespace prefix to prevent tool name collisions"
+              ]
+            },
             {
               "name": "authenticated-adapter-with-polling",
               "description": "Demonstrates configuring authentication (API key and bearer token) and automatic spec polling for OpenAPI adapters.",
@@ -1364,15 +1511,28 @@
               ]
             },
             {
-              "name": "basic-openapi-adapter",
-              "description": "Demonstrates converting an OpenAPI specification into MCP tools automatically using `OpenapiAdapter` with minimal configuration.",
-              "level": "basic",
-              "tags": ["development", "openapi", "adapters", "adapter"],
+              "name": "format-resolution-and-custom-resolvers",
+              "description": "Demonstrates using built-in and custom format resolvers to enrich tool input schemas with concrete constraints from OpenAPI format values.",
+              "level": "intermediate",
+              "tags": ["development", "openapi", "adapters", "format", "schema", "validation"],
               "features": [
-                "Using `OpenapiAdapter.init()` with just `name` and `url` to auto-generate MCP tools",
-                "Each OpenAPI operation becomes a tool named `<adapter-name>:<operationId>`",
-                "The adapter is registered in the `adapters` array of `@App`, not in `plugins`",
-                "The `name` field serves as the namespace prefix to prevent tool name collisions"
+                "Enabling built-in format resolvers with `resolveFormats: true` for uuid, date-time, email, int32, etc.",
+                "Adding custom format resolvers for domain-specific formats (phone, currency)",
+                "Merging custom resolvers with built-ins where custom takes precedence",
+                "Using custom-only resolvers without built-ins for full control"
+              ]
+            },
+            {
+              "name": "ref-security-and-filtering",
+              "description": "Demonstrates configuring $ref resolution security to prevent SSRF attacks and filtering which API operations become MCP tools.",
+              "level": "intermediate",
+              "tags": ["development", "openapi", "adapters", "security", "ssrf", "filtering"],
+              "features": [
+                "Configuring `refResolution` to restrict which hosts and protocols are allowed for external `$ref` pointers",
+                "Using `allowedHosts` to restrict $refs to trusted schema servers",
+                "Using `allowedProtocols` to enable or disable file://, http://, https://, and other protocols",
+                "Filtering operations with `includeOperations`, `excludeOperations`, and `filterFn`",
+                "Combining security hardening with operation filtering for a production-ready setup"
               ]
             },
             {
@@ -2067,6 +2227,24 @@
               ]
             }
           ]
+        },
+        {
+          "name": "distributed-ha",
+          "description": "Deploy FrontMCP across multiple pods with heartbeat, session takeover, and notification relay for zero-downtime failover",
+          "examples": [
+            {
+              "name": "ha-kubernetes-3-replicas",
+              "description": "Deploy FrontMCP with 3 replicas, Redis, and automatic session failover on Kubernetes",
+              "level": "intermediate",
+              "tags": ["ha", "kubernetes", "redis", "distributed", "session-takeover", "heartbeat"],
+              "features": [
+                "Configuring @FrontMcp with Redis for distributed deployment",
+                "Kubernetes Deployment YAML with 3 replicas and readiness probes",
+                "Verifying heartbeat keys and session takeover via redis-cli",
+                "NGINX sticky sessions for session affinity"
+              ]
+            }
+          ]
         }
       ]
     },
@@ -2371,13 +2549,13 @@
             },
             {
               "name": "hybrid-vercel-kv-with-pubsub",
-              "description": "Use Vercel KV for session storage and a separate Redis instance for pub/sub resource subscriptions.",
+              "description": "Use Vercel KV for session storage and a separate Redis instance for pub/sub resource subscriptions in distributed multi-instance deployments.",
               "level": "advanced",
               "tags": ["setup", "vercel-kv", "redis", "vercel", "session", "hybrid"],
               "features": [
                 "Vercel KV handles sessions (`redis` config) while a real Redis handles pub/sub (`pubsub` config)",
-                "Vercel KV does not support pub/sub operations, so a separate Redis instance is required",
-                "Resources with `subscribe: true` rely on the `pubsub` config for real-time notifications",
+                "Vercel KV does not support pub/sub operations, so a separate Redis instance is required for distributed setups",
+                "Resource subscriptions across multiple server instances rely on the `pubsub` config for cross-instance notifications (single-instance servers use in-memory subscriptions automatically)",
                 "The `pubsub` field accepts `provider: 'redis'` only (no Vercel KV support)"
               ]
             },
@@ -2877,6 +3055,180 @@
           ]
         }
       ]
+    },
+    {
+      "name": "frontmcp-channels",
+      "category": "development",
+      "description": "Use when you want to push real-time notifications into Claude Code sessions. Build webhook channels, chat bridges (WhatsApp, Telegram, Slack), agent completion alerts, job status notifications, or error forwarding. The skill for CHANNELS and NOTIFICATIONS.",
+      "path": "frontmcp-channels",
+      "targets": ["all"],
+      "hasResources": true,
+      "tags": [
+        "channels",
+        "notifications",
+        "claude-code",
+        "webhooks",
+        "messaging",
+        "real-time",
+        "two-way",
+        "whatsapp",
+        "telegram",
+        "slack",
+        "chat-bridge"
+      ],
+      "bundle": ["full"],
+      "references": [
+        {
+          "name": "channel-sources",
+          "description": "Configure different channel source types - webhooks, app events, agent completion, job completion, and manual push",
+          "examples": [
+            {
+              "name": "webhook-github",
+              "description": "Forward GitHub webhook events (PRs, pushes, CI) into Claude Code",
+              "level": "basic",
+              "tags": ["webhook", "github", "ci", "notifications"],
+              "features": [
+                "Webhook source with HTTP POST endpoint",
+                "GitHub event type routing",
+                "Static meta for team context"
+              ]
+            },
+            {
+              "name": "app-errors",
+              "description": "Forward application errors to Claude Code via the in-process event bus",
+              "level": "basic",
+              "tags": ["errors", "app-event", "debugging", "monitoring"],
+              "features": [
+                "App event source with ChannelEventBus",
+                "Error severity classification",
+                "Stack trace forwarding"
+              ]
+            },
+            {
+              "name": "agent-notify",
+              "description": "Notify Claude Code when AI agents complete their tasks",
+              "level": "intermediate",
+              "tags": ["agents", "completion", "notifications", "automation"],
+              "features": [
+                "Agent completion source with ID filtering",
+                "Duration and output reporting",
+                "Integration with agent registry emitter"
+              ]
+            },
+            {
+              "name": "job-completion",
+              "description": "Notify Claude Code when background jobs and workflows complete",
+              "level": "intermediate",
+              "tags": ["jobs", "workflows", "completion", "background", "notifications"],
+              "features": [
+                "Job completion source with name filtering",
+                "Status-aware notification formatting",
+                "Duration and output reporting"
+              ]
+            },
+            {
+              "name": "service-connector",
+              "description": "Build a persistent service connector that lets Claude send and receive messages through WhatsApp, Telegram, or any messaging API",
+              "level": "advanced",
+              "tags": ["service", "connector", "whatsapp", "persistent-connection", "bidirectional"],
+              "features": [
+                "Service source type with onConnect/onDisconnect lifecycle",
+                "Channel-contributed tools for outbound messages",
+                "pushIncoming() for feeding service events into the notification pipeline",
+                "Bidirectional conversation flow"
+              ]
+            },
+            {
+              "name": "file-watcher",
+              "description": "Watch files for changes and notify Claude Code in real-time",
+              "level": "intermediate",
+              "tags": ["file-watcher", "filesystem", "logs", "monitoring", "real-time"],
+              "features": [
+                "File watcher source type with glob patterns",
+                "onConnect lifecycle for starting the watcher",
+                "pushIncoming for streaming file events",
+                "Log file monitoring example"
+              ]
+            },
+            {
+              "name": "replay-buffer",
+              "description": "Buffer channel events so Claude Code receives them when it connects, even if events occurred while offline",
+              "level": "advanced",
+              "tags": ["replay", "buffer", "persistence", "offline", "reconnect"],
+              "features": [
+                "Replay configuration with maxEvents cap",
+                "In-memory ring buffer for event storage",
+                "Replay on session connect",
+                "Persistent store pattern with onConnect"
+              ]
+            }
+          ]
+        },
+        {
+          "name": "channel-two-way",
+          "description": "Build two-way chat bridges connecting WhatsApp, Telegram, Slack, and Discord to Claude Code",
+          "examples": [
+            {
+              "name": "whatsapp-bridge",
+              "description": "Full WhatsApp Business API bridge allowing users to chat with Claude Code via WhatsApp",
+              "level": "advanced",
+              "tags": ["whatsapp", "chat", "two-way", "messaging", "bridge"],
+              "features": [
+                "Two-way channel with reply support",
+                "WhatsApp Cloud API integration",
+                "Sender verification and allowlisting",
+                "Webhook signature validation"
+              ]
+            }
+          ]
+        }
+      ]
+    },
+    {
+      "name": "frontmcp-authorities",
+      "category": "development",
+      "description": "Use when implementing authorization, access control, RBAC, ABAC, or ReBAC for tools, resources, or prompts. Covers JWT claims mapping, authority profiles, and policy enforcement.",
+      "path": "frontmcp-authorities",
+      "targets": ["all"],
+      "hasResources": true,
+      "tags": [
+        "authorization",
+        "rbac",
+        "abac",
+        "rebac",
+        "security",
+        "permissions",
+        "roles",
+        "access-control",
+        "authorities",
+        "jwt"
+      ],
+      "bundle": ["full"],
+      "priority": 9,
+      "visibility": "both",
+      "license": "Apache-2.0",
+      "references": [
+        {
+          "name": "claims-mapping",
+          "description": "JWT claims mapping per identity provider (Auth0, Keycloak, Okta, Cognito, Frontegg)",
+          "examples": []
+        },
+        {
+          "name": "authority-profiles",
+          "description": "Registering and using named authority profiles for reusable access patterns",
+          "examples": []
+        },
+        {
+          "name": "rbac-abac-rebac",
+          "description": "Comparison of RBAC, ABAC, and ReBAC authorization models with usage guidance",
+          "examples": []
+        },
+        {
+          "name": "custom-evaluators",
+          "description": "Creating custom authority evaluators for domain-specific access control",
+          "examples": []
+        }
+      ]
     }
   ]
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@frontmcp/skills",
-  "version": "1.0.3",
+  "version": "1.1.0-beta.1",
   "description": "Curated skills catalog for FrontMCP projects",
   "author": "AgentFront <info@agentfront.dev>",
   "homepage": "https://docs.agentfront.dev",