Add DealWatch and CortexPilot public skills

marketplaces/default.json

@@ -485,6 +485,32 @@
                 "sample"
             ]
         },
+        {
+            "name": "dealwatch-readonly-builder",
+            "source": "./dealwatch-readonly-builder",
+            "description": "Teach the agent how to install and use the published DealWatch read-only MCP package for compare-first grocery workflows.",
+            "category": "integration",
+            "keywords": [
+                "dealwatch",
+                "builder",
+                "mcp",
+                "compare",
+                "local-first"
+            ]
+        },
+        {
+            "name": "cortexpilot-adoption-router",
+            "source": "./cortexpilot-adoption-router",
+            "description": "Teach the agent how to install and use the published CortexPilot read-only MCP package and choose the right public lane.",
+            "category": "productivity",
+            "keywords": [
+                "cortexpilot",
+                "router",
+                "mcp",
+                "proof",
+                "adoption"
+            ]
+        },
         {
             "name": "automation-creation",
             "source": "./plugins/automation-creation",

skills/cortexpilot-adoption-router/README.md

@@ -0,0 +1,42 @@
+# CortexPilot Adoption Router
+
+This bundle teaches an agent how to connect the published CortexPilot read-only
+MCP package and choose the right public adoption lane.
+
+## What the agent learns here
+
+- how to install the published `cortexpilot-orchestrator==0.1.0a4` MCP package
+- which read-only CortexPilot tools exist and which are safe-first
+- how to choose between run/workflow inspection, queue/approval reads, and
+  proof/incident reads
+- which hosted or write-capable claims stay out of bounds
+
+## Included files
+
+- `SKILL.md` — the progressive-disclosure prompt for the agent
+- `README.md` — the human-facing overview for reviewers and operators
+- `manifest.yaml` — listing metadata for host skill registries
+- `references/README.md` — the local index for every supporting file
+- `references/INSTALL.md` — exact install snippets for OpenHands/OpenClaw
+- `references/OPENHANDS_MCP_CONFIG.json` — a ready-to-edit `mcpServers` snippet
+- `references/OPENCLAW_MCP_CONFIG.json` — a ready-to-edit `mcp.servers` snippet
+- `references/CAPABILITIES.md` — the stable read-only tool inventory
+- `references/DEMO.md` — the first-success walkthrough and expected return shape
+- `references/TROUBLESHOOTING.md` — the first checks when launch or inspection fails
+
+## The shortest install path
+
+Use the published package, not a repo-local checkout:
+
+```bash
+uvx --from cortexpilot-orchestrator==0.1.0a4 cortexpilot-readonly-mcp
+```
+
+If the host needs a saved MCP config snippet, use the host-specific examples in
+`references/INSTALL.md`.
+
+## Hard boundaries
+
+- no hosted operator service
+- no write-capable public MCP
+- no first-party marketplace claim unless that host independently confirms it

skills/cortexpilot-adoption-router/SKILL.md

@@ -0,0 +1,82 @@
+---
+name: cortexpilot-adoption-router
+description: Teach the agent how to connect the published CortexPilot read-only MCP package, choose the right public lane, and use the stable read-only tools without overclaiming hosted or write-capable support.
+triggers:
+  - cortexpilot
+  - cortexpilot setup
+  - cortexpilot mcp
+  - cortexpilot proof
+  - cortexpilot workflow
+---
+
+# CortexPilot Adoption Router
+
+Use this skill when the user needs the shortest truthful path into CortexPilot.
+
+## What this skill teaches
+
+- how to install the published CortexPilot MCP package
+- how to choose the right read-only tool for the current job
+- how to start with one public lane instead of mixing every surface together
+- how to keep the answer inside the current read-only public boundary
+
+## When to use this skill
+
+Use this skill when the user asks to:
+
+- connect CortexPilot to OpenHands or OpenClaw
+- inspect runs or workflows through the public read-only MCP
+- understand which public CortexPilot lane to choose first
+- inspect approvals, queue state, proof, compare, or incident summaries without
+  mutating anything
+
+## If the MCP is not connected yet
+
+Open `README.md` in this folder and follow `references/INSTALL.md`.
+Do not invent repo-local startup paths when the published package already
+exists.
+
+## Safe-first workflow
+
+1. `list_runs` or `list_workflows`
+   Use these first when the user needs the top-level ledger.
+2. `get_run` or `get_workflow`
+   Use these after the user already has the specific run or workflow to inspect.
+3. `list_queue`, `get_pending_approvals`, or `get_diff_gate_state`
+   Use these for queue, approval, or diff-gate posture.
+4. `get_run_reports`, `get_compare_summary`, `get_proof_summary`, or
+   `get_incident_summary`
+   Use these after the user is already inside one run and needs a specific
+   proof-oriented read model.
+
+## Tool-selection rule
+
+- Choose run/workflow reads for “what is happening now?”
+- Choose queue/approval reads for “what is blocked or pending?”
+- Choose compare/proof/incident reads for “what evidence exists for this run?”
+- Do not mix multiple lanes unless the user explicitly asks for a broader audit
+
+## What to return
+
+Return a short answer with:
+
+1. the chosen lane
+2. the next 1-3 actions
+3. one boundary reminder
+4. one exact MCP tool or install snippet
+
+## Guardrails
+
+- Do not describe CortexPilot as a hosted operator product.
+- Do not describe the public MCP surface as write-capable.
+- Do not claim a first-party marketplace listing unless that host independently
+  confirms it.
+- Keep `task_contract` as the execution authority for real runs; this MCP is
+  read-only inspection only.
+
+## Read next
+
+- `references/INSTALL.md`
+- `references/CAPABILITIES.md`
+- `references/DEMO.md`
+- `references/TROUBLESHOOTING.md`

skills/cortexpilot-adoption-router/manifest.yaml

@@ -0,0 +1,42 @@
+schema_version: 1
+artifact: public-skill-listing-manifest
+
+skill:
+  name: cortexpilot-adoption-router
+  display_name: CortexPilot Adoption Router
+  version: 1.1.1
+  entrypoint: SKILL.md
+  package_shape: skill-folder
+
+registry_targets:
+  clawhub:
+    status: listed-live
+    package_shape: skill-folder
+    listing_url: https://www.clawhub.ai/skills/cortexpilot-adoption-router
+    submit_via: clawhub publish . --slug cortexpilot-adoption-router --name "CortexPilot Adoption Router" --version 1.1.1 --tags mcp,workflow,proof,read-only,cortexpilot
+  openhands-extensions:
+    status: review-pending
+    package_shape: skill-folder
+    submission_url: https://github.com/OpenHands/extensions/pull/151
+    submit_via: submit this folder as skills/cortexpilot-adoption-router/ in OpenHands/extensions
+
+boundaries:
+  product_identity: Proof-first CortexPilot adoption routing through the published read-only MCP surface.
+  canonical_repo_version: 0.1.0a4
+  official_listing_state: clawhub-live-other-hosts-pending
+  not_claimed:
+    - No hosted operator service is claimed
+    - No write-capable public MCP surface is claimed
+    - No first-party marketplace listing is claimed unless independently confirmed
+    - No live OpenHands/extensions listing is claimed until the PR lands
+
+pair_with:
+  - SKILL.md
+  - README.md
+  - references/README.md
+  - references/INSTALL.md
+  - references/OPENHANDS_MCP_CONFIG.json
+  - references/OPENCLAW_MCP_CONFIG.json
+  - references/CAPABILITIES.md
+  - references/DEMO.md
+  - references/TROUBLESHOOTING.md

skills/cortexpilot-adoption-router/references/CAPABILITIES.md

@@ -0,0 +1,33 @@
+# CortexPilot MCP Capabilities
+
+These are the stable read-only tools exposed by the published CortexPilot MCP.
+
+## Safe-first tools
+
+1. `list_runs`
+   - use first when the user needs the current run ledger
+2. `get_run`
+   - use when the user already has one run identifier and needs the run snapshot
+3. `list_workflows`
+   - use when the user needs the current workflow ledger
+4. `get_workflow`
+   - use when the user already has one workflow identifier
+
+## Queue and approval tools
+
+- `list_queue`
+- `get_pending_approvals`
+- `get_diff_gate_state`
+
+Use these when the user is inspecting queue state, pending approvals, or diff
+gate posture.
+
+## Proof and incident tools
+
+- `get_run_reports`
+- `get_compare_summary`
+- `get_proof_summary`
+- `get_incident_summary`
+
+Use these after the user is already inside a specific run and wants the proof,
+compare, or incident read model.

skills/cortexpilot-adoption-router/references/DEMO.md

@@ -0,0 +1,24 @@
+# OpenHands / OpenClaw Demo Walkthrough
+
+This is the shortest concrete demo you can run to prove the skill is doing real
+inspection work instead of only describing one.
+
+## Demo prompt
+
+Connect CortexPilot and inspect the current public run ledger. Start with
+`list_runs` or `list_workflows`, then inspect one specific run or workflow.
+If the user is really asking what is blocked, pivot into `list_queue` or
+`get_pending_approvals` and explain the safest next lane.
+
+## Expected tool sequence
+
+1. `list_runs` or `list_workflows`
+2. `get_run` or `get_workflow`
+3. optionally `list_queue` or `get_pending_approvals`
+
+## Visible success criteria
+
+- the agent names one real run or workflow instead of speaking in the abstract
+- the answer stays on the read-only lane
+- the agent points the user at the next inspection step instead of inventing a
+  write workflow

skills/cortexpilot-adoption-router/references/INSTALL.md

@@ -0,0 +1,22 @@
+# Install The Published CortexPilot MCP
+
+Use the published PyPI package, not a repo-local checkout.
+
+## Published package
+
+- package: `cortexpilot-orchestrator==0.1.0a4`
+- executable: `cortexpilot-readonly-mcp`
+- transport: `stdio`
+
+## OpenHands example
+
+Use `OPENHANDS_MCP_CONFIG.json` as the starting point for your host config.
+
+## OpenClaw example
+
+Use `OPENCLAW_MCP_CONFIG.json` as the starting point for your host config.
+
+## Smoke check
+
+Use a minimal MCP handshake and `tools/list` request after the host attaches the
+server.

skills/cortexpilot-adoption-router/references/OPENCLAW_MCP_CONFIG.json

@@ -0,0 +1,10 @@
+{
+  "mcp": {
+    "servers": {
+      "cortexpilot-readonly": {
+        "command": "uvx",
+        "args": ["--from", "cortexpilot-orchestrator==0.1.0a4", "cortexpilot-readonly-mcp"]
+      }
+    }
+  }
+}

skills/cortexpilot-adoption-router/references/OPENHANDS_MCP_CONFIG.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "cortexpilot-readonly": {
+      "command": "uvx",
+      "args": ["--from", "cortexpilot-orchestrator==0.1.0a4", "cortexpilot-readonly-mcp"]
+    }
+  }
+}

skills/cortexpilot-adoption-router/references/README.md

@@ -0,0 +1,19 @@
+# CortexPilot Skill References
+
+This directory keeps the practical material that a reviewer or agent needs
+without depending on repo-root docs.
+
+## Included references
+
+- `INSTALL.md`
+  - install the published MCP package and wire it into a host
+- `OPENHANDS_MCP_CONFIG.json`
+  - a ready-to-edit `mcpServers` snippet
+- `OPENCLAW_MCP_CONFIG.json`
+  - a ready-to-edit `mcp.servers` snippet
+- `CAPABILITIES.md`
+  - the stable read-only tool surface and recommended safe-first order
+- `DEMO.md`
+  - the first-success walkthrough and expected return shape
+- `TROUBLESHOOTING.md`
+  - the first places to check when attach or inspection fails

skills/cortexpilot-adoption-router/references/TROUBLESHOOTING.md

@@ -0,0 +1,35 @@
+# CortexPilot Troubleshooting
+
+Use this page when the packet looks correct but the first attach or read-only
+inspection still fails.
+
+## 1. The MCP server does not launch
+
+Check these first:
+
+- `uvx` is available on the machine
+- the package version from `INSTALL.md` still resolves
+- the host config matches the command and args in the JSON snippets
+
+If launch still fails, report it as a package or host-config problem instead of
+claiming the packet is attach-ready.
+
+## 2. The top-level list tools return nothing useful
+
+Confirm:
+
+- you started with `list_runs` or `list_workflows`
+- the public read-only MCP actually has access to the expected environment
+- the user is not asking for a hosted or write-capable surface this packet does
+  not expose
+
+## 3. The user wants to mutate state
+
+Stop and explain the boundary. This packet only covers the published read-only
+inspection lane.
+
+## 4. Boundary reminder
+
+This packet is for the public, read-only CortexPilot MCP surface. It does not
+claim a hosted operator service, a write-capable public MCP, or a live
+OpenHands/extensions listing until the PR lands.

skills/cortexpilot-adoption-router/references/example-tasks.md

@@ -0,0 +1,15 @@
+# Example Tasks
+
+Use this bundle for tasks like:
+
+- “Connect CortexPilot to OpenHands and inspect the run ledger.”
+- “Which CortexPilot MCP tool should I call first for workflow truth?”
+- “Show me the safest read-only lane for approvals or queue state.”
+- “Inspect proof or incident summaries without mutating anything.”
+
+Return shapes should stay short and operational:
+
+1. chosen lane
+2. next 1-3 actions
+3. one boundary reminder
+4. one exact MCP tool or install snippet