clawskills-mcp 0.7.1 → 0.7.2

package/README.md

@@ -32,8 +32,9 @@ No install needed. Add this to your MCP client config:
 ### Via Docker
 
 ```bash
-# From repo root
-docker build -t clawskills-mcp -f mcp-server/Dockerfile .
+# From repo root — the build context must be the root, since the image
+# copies skills/ and playbooks/ from there.
+docker build -t clawskills-mcp .
 docker run --rm -i clawskills-mcp
 ```
 

package/dist/index.js

@@ -308,19 +308,27 @@ server.setRequestHandler(ListToolsRequestSchema, async () => ({
     tools: [
         {
             name: "list_skills",
-            description: "List all available ClawSkills API integration skill docs.",
+            description: "List the slugs of every available API integration skill doc, with a one-line summary of each. " +
+                "Read-only; takes no arguments; returns a short list (currently 14 entries), not the doc bodies. " +
+                "Call this first when you do not yet know which platform slug to pass to get_skill, or to check whether a platform is covered at all before falling back to general knowledge.",
             inputSchema: { type: "object", properties: {}, required: [] },
         },
         {
             name: "get_skill",
-            description: "Retrieve a ClawSkills skill doc by name (slug). Optionally specify a section (e.g. 'auth', 'rate-limits', 'recipes') to get just that part.",
+            description: "Fetch the integration guide for one SaaS platform: authentication, rate limits, pagination, error handling, and tested request recipes. " +
+                "Read-only. Returns Markdown. A whole doc is large (roughly 20-40 KB), so pass `section` to retrieve just the part you need unless you genuinely want everything. " +
+                "Use this when you already know the platform; use search_skills instead when you know the problem but not the platform. " +
+                "Each doc carries a `Last validated` date in its header indicating when it was last checked against the vendor's live documentation.",
             inputSchema: {
                 type: "object",
                 properties: {
-                    name: { type: "string", description: "Skill slug, e.g. 'salesforce', 'github', 'figma'" },
+                    name: {
+                        type: "string",
+                        description: "Skill slug, lowercase, exactly as returned by list_skills. One of: asana, dynamics365, figma, github, hubspot, jira, linear, monday, notion, salesforce, servicenow, slack, stripe, zendesk.",
+                    },
                     section: {
                         type: "string",
-                        description: "Optional section name. Aliases: auth, rate-limits, errors, pagination, recipes, gotchas, webhooks, overview, fields",
+                        description: "Optional. Return only this section instead of the whole document. One of: auth, rate-limits, errors, pagination, recipes, gotchas, webhooks, overview, fields. Omit to return the full doc.",
                     },
                 },
                 required: ["name"],
@@ -328,49 +336,70 @@ server.setRequestHandler(ListToolsRequestSchema, async () => ({
         },
         {
             name: "search_skills",
-            description: "Search across all skill docs for a query string. Returns matching excerpts with context. Useful when you don't know which skill to fetch.",
+            description: "Full-text search across all 14 platform skill docs, returning matching excerpts with surrounding context rather than whole documents. " +
+                "Read-only. Use when you know the problem but not which platform doc answers it — for example a specific error code, header, or auth mechanism. " +
+                "Searches single-platform docs only; use search_clawskills if the task spans two systems.",
             inputSchema: {
                 type: "object",
                 properties: {
-                    query: { type: "string", description: "Search query, e.g. '429 retry', 'OAuth scopes', 'webhook signature'" },
+                    query: {
+                        type: "string",
+                        description: "Free-text query matched against document contents. Works best with concrete API terms, e.g. '429 retry', 'OAuth scopes', 'webhook signature'.",
+                    },
                 },
                 required: ["query"],
             },
         },
         {
             name: "list_playbooks",
-            description: "List all available ClawSkills workflow playbooks.",
+            description: "List the slugs of every available cross-tool workflow playbook, with a one-line summary of each. " +
+                "Read-only; takes no arguments; returns a short list (currently 4 entries), not the playbook bodies. " +
+                "Playbooks describe how to wire two systems together end to end; single-platform API questions are covered by list_skills instead.",
             inputSchema: { type: "object", properties: {}, required: [] },
         },
         {
             name: "get_playbook",
-            description: "Retrieve a ClawSkills workflow playbook by name (slug).",
+            description: "Fetch one cross-tool workflow playbook: the trigger, source of truth, field mapping, idempotency and dedup keys, retry and partial-failure policy, and reconciliation steps for syncing two systems. " +
+                "Read-only. Returns Markdown, typically a few KB. " +
+                "Use this when the task spans two platforms (for example 'create a Jira issue from a Zendesk ticket'); use get_skill when the task involves only one.",
             inputSchema: {
                 type: "object",
                 properties: {
-                    name: { type: "string", description: "Playbook slug, e.g. 'zendesk-jira-bug-escalation'" },
+                    name: {
+                        type: "string",
+                        description: "Playbook slug, lowercase, exactly as returned by list_playbooks. One of: hubspot-asana-onboarding, salesforce-hubspot-lead-sync, slack-jira-incident, zendesk-jira-bug-escalation.",
+                    },
                 },
                 required: ["name"],
             },
         },
         {
             name: "search_playbooks",
-            description: "Search across workflow playbooks for a query string and return matching excerpts with context.",
+            description: "Full-text search across the cross-tool workflow playbooks, returning matching excerpts with surrounding context. " +
+                "Read-only. Use for orchestration concerns that recur across integrations — idempotency, dedup keys, rollback, partial failure — when you do not know which playbook covers them.",
             inputSchema: {
                 type: "object",
                 properties: {
-                    query: { type: "string", description: "Search query, e.g. 'idempotency', 'rollback', 'customer impact'" },
+                    query: {
+                        type: "string",
+                        description: "Free-text query matched against playbook contents, e.g. 'idempotency', 'rollback', 'customer impact'.",
+                    },
                 },
                 required: ["query"],
             },
         },
         {
             name: "search_clawskills",
-            description: "Search across both skills and playbooks. For workflow-shaped queries, playbooks are ranked ahead of generic skill matches.",
+            description: "Full-text search across both the platform skill docs and the workflow playbooks in one call, returning matching excerpts with context. " +
+                "Read-only. Playbooks are ranked ahead of skill matches for workflow-shaped queries. " +
+                "Prefer this as the default entry point when you are unsure whether the answer is a single-platform API detail or a two-system workflow; reach for search_skills or search_playbooks only when you want to restrict results to one of the two.",
             inputSchema: {
                 type: "object",
                 properties: {
-                    query: { type: "string", description: "Search query, e.g. 'closed won onboarding', 'zendesk jira escalation', 'lead sync'" },
+                    query: {
+                        type: "string",
+                        description: "Free-text query matched against both corpora, e.g. 'closed won onboarding', 'zendesk jira escalation', 'lead sync'.",
+                    },
                 },
                 required: ["query"],
             },

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "clawskills-mcp",
-  "version": "0.7.1",
+  "version": "0.7.2",
   "description": "MCP server exposing ClawSkills API integration skill docs to AI agents",
   "license": "MIT",
   "author": "ClawSkills Contributors",

package/skills/ROADMAP.md

@@ -19,7 +19,7 @@ This skill set enables end-to-end automation and integration across the most com
 | Layer | Status |
 |-------|--------|
 | **14 skill docs** — Monday.com, Salesforce, Jira, Dynamics 365, HubSpot, ServiceNow, Zendesk, Asana, GitHub, Figma, Slack, Stripe, Notion, Linear | ✅ Live |
-| **MCP server** — `clawskills-mcp` v0.7.1 on npm; `list_skills`, `get_skill`, `search_skills` | ✅ Live |
+| **MCP server** — `clawskills-mcp` v0.7.2 on npm; `list_skills`, `get_skill`, `search_skills` | ✅ Live |
 | **CI pipeline** — build + test on every push/PR via `ci.yml` | ✅ Live |
 | **Release automation** — `prepare-release.yml` workflow_dispatch → release PR; `release.yml` on merge → npm publish via OIDC + tag | ✅ Live |
 | **Test suite** — Vitest unit tests + real-skills validation (required sections, ≥5 KB, all 14 tools) | ✅ Live |
@@ -83,7 +83,7 @@ The repo now needs tighter alignment between the canonical `skills/` directory,
 | Channel | Status | Next action |
 |---------|--------|-------------|
 | GitHub (public) | Ready to flip | Make repo public |
-| npm (`clawskills-mcp`) | ✅ Live — v0.7.1 | Maintain via `release.yml` |
+| npm (`clawskills-mcp`) | ✅ Live — v0.7.2 | Maintain via `release.yml` |
 | MCP registry listings | Not submitted | Submit to glama.ai, mcp.so, smithery.ai after public launch |
 | Docs website | Planned | Mintlify — fastest path to SEO-friendly browsable docs |
 | Lane A vs B | TBD | Revisit after first traction signals from public launch |