chore: bump version to 2.2.1 (#42)

Author: leonardovida

.claude-plugin/marketplace.json

@@ -5,14 +5,14 @@
   },
   "metadata": {
     "description": "MotherDuck skills for connecting, exploring live schemas, writing DuckDB SQL, using the REST API, and shipping Dives, dashboards, pipelines, and analytics apps.",
-    "version": "2.2.0"
+    "version": "2.2.1"
   },
   "plugins": [
     {
       "name": "motherduck-skills",
       "source": "./plugins/motherduck-skills-claude",
       "description": "MotherDuck skills for connecting, exploring live schemas, writing DuckDB SQL, using the REST API, and building dashboards, Dives, pipelines, and analytics apps.",
-      "version": "2.2.0",
+      "version": "2.2.1",
       "author": {
         "name": "MotherDuck"
       },

.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "motherduck-skills",
-  "version": "2.2.0",
+  "version": "2.2.1",
   "description": "MotherDuck skills for agents and developers: connect, explore schemas, write DuckDB SQL, use the REST API, build Dives, and ship dashboards, pipelines, and customer-facing analytics.",
   "author": {
     "name": "MotherDuck",

.cursor-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "motherduck-skills",
   "displayName": "MotherDuck Skills",
-  "version": "2.2.0",
+  "version": "2.2.1",
   "description": "MotherDuck skills for agents and developers: connect, explore schemas, write DuckDB SQL, use the REST API, build Dives, and ship dashboards, pipelines, and customer-facing analytics.",
   "author": {
     "name": "MotherDuck"

docs/skill-authoring.md

@@ -18,7 +18,7 @@ For use-case skills, always say what to do when a remote or local MotherDuck ser
 - ask which database or workspace is in scope if unclear
 - explore databases, schemas, tables, columns, and key joins
 - let the real data model shape the downstream implementation
-- when the skill emits a native DuckDB (`md:`) connection, watermark it with `custom_user_agent=agent-skills/2.2.0(harness-<harness>;llm-<llm>)`; if metadata is missing, fall back to `harness-unknown` and `llm-unknown`
+- when the skill emits a native DuckDB (`md:`) connection, watermark it with `custom_user_agent=agent-skills/2.2.1(harness-<harness>;llm-<llm>)`; if metadata is missing, fall back to `harness-unknown` and `llm-unknown`
   - this watermark is for high-level product analytics only: which harness and LLM used the skill, so we can improve the skill and test it against that LLM later
   - do not present it as user tracking; it is not for personal data or end-user attribution
 

gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "motherduck-skills",
-  "version": "2.2.0",
+  "version": "2.2.1",
   "description": "MotherDuck skills for Gemini CLI: connect, explore live schemas, write DuckDB SQL, use the REST API, and build Dives, dashboards, pipelines, migrations, and analytics apps.",
   "contextFileName": "GEMINI.md",
   "plan": {

package.json

@@ -1,6 +1,6 @@
 {
   "name": "motherduck-skills",
-  "version": "2.2.0",
+  "version": "2.2.1",
   "description": "Opinionated MotherDuck skills for AI coding agents.",
   "devDependencies": {
     "typescript": "^6.0.2"

plugins/motherduck-skills-claude/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "motherduck-skills",
-  "version": "2.2.0",
+  "version": "2.2.1",
   "description": "MotherDuck skills for connecting, exploring live schemas, writing DuckDB SQL, using the REST API, and building dashboards, Dives, pipelines, and analytics apps.",
   "author": {
     "name": "MotherDuck",

plugins/motherduck-skills-claude/skills/motherduck-build-cfa-app/SKILL.md

@@ -66,7 +66,7 @@ If no server is active, ask for a representative schema excerpt or table list an
 6. Choose the connection path and read-scaling posture.
 7. Produce the implementation plan, API contract, and rollout sequence.
 
-When this skill produces a native DuckDB (`md:`) connection, watermark it with `custom_user_agent=agent-skills/2.2.0(harness-<harness>;llm-<llm>)`. If metadata is missing, fall back to `harness-unknown` and `llm-unknown`.
+When this skill produces a native DuckDB (`md:`) connection, watermark it with `custom_user_agent=agent-skills/2.2.1(harness-<harness>;llm-<llm>)`. If metadata is missing, fall back to `harness-unknown` and `llm-unknown`.
 
 ## Output
 

plugins/motherduck-skills-claude/skills/motherduck-build-cfa-app/artifacts/customer_routing_example.ts

@@ -13,7 +13,7 @@ function normalizeMetadataValue(value: string | undefined, fallback: string): st
 function buildUseCaseUserAgent(): string {
   const harness = normalizeMetadataValue(process.env.MOTHERDUCK_AGENT_HARNESS, "unknown");
   const llm = normalizeMetadataValue(process.env.MOTHERDUCK_AGENT_LLM, "unknown");
-  return `agent-skills/2.2.0(harness-${harness};llm-${llm})`;
+  return `agent-skills/2.2.1(harness-${harness};llm-${llm})`;
 }
 
 function summarizeCustomer(rows: EventRow[]): Array<{ event_type: string; total_revenue: number }> {

plugins/motherduck-skills-claude/skills/motherduck-build-cfa-app/references/CFA_IMPLEMENTATION_GUIDE.md

@@ -203,7 +203,7 @@ Native DuckDB gives full SQL support, cross-database queries, and no driver tran
 # Python backend example (FastAPI + duckdb)
 import duckdb
 
-CFA_USER_AGENT = "agent-skills/2.2.0(harness-<harness>;llm-<llm>)"
+CFA_USER_AGENT = "agent-skills/2.2.1(harness-<harness>;llm-<llm>)"
 
 def get_customer_connection(customer_db: str, customer_token: str):
     """Create a native DuckDB connection to a customer's MotherDuck database."""