diff --git a/marketplaces/default.json b/marketplaces/default.json
index 5ee1dd6a..94283117 100644
--- a/marketplaces/default.json
+++ b/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",
diff --git a/skills/cortexpilot-adoption-router/README.md b/skills/cortexpilot-adoption-router/README.md
new file mode 100644
index 00000000..05537ceb
--- /dev/null
+++ b/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
diff --git a/skills/cortexpilot-adoption-router/SKILL.md b/skills/cortexpilot-adoption-router/SKILL.md
new file mode 100644
index 00000000..072909ce
--- /dev/null
+++ b/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`
diff --git a/skills/cortexpilot-adoption-router/manifest.yaml b/skills/cortexpilot-adoption-router/manifest.yaml
new file mode 100644
index 00000000..8df48135
--- /dev/null
+++ b/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
diff --git a/skills/cortexpilot-adoption-router/references/CAPABILITIES.md b/skills/cortexpilot-adoption-router/references/CAPABILITIES.md
new file mode 100644
index 00000000..58a9eeab
--- /dev/null
+++ b/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.
diff --git a/skills/cortexpilot-adoption-router/references/DEMO.md b/skills/cortexpilot-adoption-router/references/DEMO.md
new file mode 100644
index 00000000..beb094fe
--- /dev/null
+++ b/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
diff --git a/skills/cortexpilot-adoption-router/references/INSTALL.md b/skills/cortexpilot-adoption-router/references/INSTALL.md
new file mode 100644
index 00000000..328d2ff2
--- /dev/null
+++ b/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.
diff --git a/skills/cortexpilot-adoption-router/references/OPENCLAW_MCP_CONFIG.json b/skills/cortexpilot-adoption-router/references/OPENCLAW_MCP_CONFIG.json
new file mode 100644
index 00000000..d287b044
--- /dev/null
+++ b/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"]
+      }
+    }
+  }
+}
diff --git a/skills/cortexpilot-adoption-router/references/OPENHANDS_MCP_CONFIG.json b/skills/cortexpilot-adoption-router/references/OPENHANDS_MCP_CONFIG.json
new file mode 100644
index 00000000..ea2a1827
--- /dev/null
+++ b/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"]
+    }
+  }
+}
diff --git a/skills/cortexpilot-adoption-router/references/README.md b/skills/cortexpilot-adoption-router/references/README.md
new file mode 100644
index 00000000..fb4ddc77
--- /dev/null
+++ b/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
diff --git a/skills/cortexpilot-adoption-router/references/TROUBLESHOOTING.md b/skills/cortexpilot-adoption-router/references/TROUBLESHOOTING.md
new file mode 100644
index 00000000..83e476d2
--- /dev/null
+++ b/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.
diff --git a/skills/cortexpilot-adoption-router/references/example-tasks.md b/skills/cortexpilot-adoption-router/references/example-tasks.md
new file mode 100644
index 00000000..ce4efb82
--- /dev/null
+++ b/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
diff --git a/skills/cortexpilot-adoption-router/references/mcp-install.md b/skills/cortexpilot-adoption-router/references/mcp-install.md
new file mode 100644
index 00000000..589823e1
--- /dev/null
+++ b/skills/cortexpilot-adoption-router/references/mcp-install.md
@@ -0,0 +1,42 @@
+# 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
+
+Add the server to `~/.openhands/config.toml`:
+
+```toml
+[mcp]
+stdio_servers = [
+  { name = "cortexpilot-readonly", command = "uvx", args = ["--from", "cortexpilot-orchestrator==0.1.0a4", "cortexpilot-readonly-mcp"] }
+]
+```
+
+## OpenClaw example
+
+Add the server to your saved MCP server config:
+
+```json
+{
+  "mcp": {
+    "servers": {
+      "cortexpilot-readonly": {
+        "command": "uvx",
+        "args": ["--from", "cortexpilot-orchestrator==0.1.0a4", "cortexpilot-readonly-mcp"]
+      }
+    }
+  }
+}
+```
+
+## Smoke check
+
+Use a minimal MCP handshake and `tools/list` request after the host attaches the
+server.
diff --git a/skills/cortexpilot-adoption-router/references/tool-map.md b/skills/cortexpilot-adoption-router/references/tool-map.md
new file mode 100644
index 00000000..83201a23
--- /dev/null
+++ b/skills/cortexpilot-adoption-router/references/tool-map.md
@@ -0,0 +1,33 @@
+# CortexPilot MCP Tool Map
+
+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 Case 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.
diff --git a/skills/dealwatch-readonly-builder/README.md b/skills/dealwatch-readonly-builder/README.md
new file mode 100644
index 00000000..5c7f66e5
--- /dev/null
+++ b/skills/dealwatch-readonly-builder/README.md
@@ -0,0 +1,43 @@
+# DealWatch Read-only Builder
+
+This bundle teaches an agent how to connect the published DealWatch MCP package
+and use its read-only tools safely.
+
+## What the agent learns here
+
+- how to install the published `dealwatch==1.0.1` MCP package
+- which DealWatch MCP tools exist and which three are safe-first
+- how to choose between runtime-readiness, builder-starter, compare, watch, and
+  recovery reads
+- which 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` — read-only tool inventory and first-use order
+- `references/DEMO.md` — the first-success walkthrough and expected output shape
+- `references/TROUBLESHOOTING.md` — the first checks when attach or compare fails
+
+## The shortest install path
+
+Use the published package, not a repo-local checkout:
+
+```bash
+uvx --from dealwatch==1.0.1 dealwatch-mcp serve
+```
+
+If the host needs a saved MCP config snippet, use the host-specific examples in
+`references/INSTALL.md`.
+
+## Hard boundaries
+
+- no hosted DealWatch control plane
+- no write-side MCP surface
+- no autonomous recommendation claim
+- no first-party marketplace claim unless that host independently confirms it
diff --git a/skills/dealwatch-readonly-builder/SKILL.md b/skills/dealwatch-readonly-builder/SKILL.md
new file mode 100644
index 00000000..28cc8937
--- /dev/null
+++ b/skills/dealwatch-readonly-builder/SKILL.md
@@ -0,0 +1,85 @@
+---
+name: dealwatch-readonly-builder
+description: Teach the agent how to connect the published DealWatch MCP package, choose the right read-only tool, and guide the user through the compare-first safe path without claiming hosted or write-capable features.
+triggers:
+  - dealwatch
+  - dealwatch setup
+  - dealwatch mcp
+  - compare preview
+  - watch group
+---
+
+# DealWatch Read-only Builder
+
+Use this skill when the user wants the shortest truthful path into DealWatch.
+
+## What this skill teaches
+
+- how to install the published DealWatch MCP package
+- how to choose the right read-only tool for the current job
+- how to start with runtime readiness and compare preview before deeper reads
+- how to keep the answer inside the current local-first boundary
+
+## When to use this skill
+
+Use this skill when the user asks to:
+
+- connect DealWatch to OpenHands or OpenClaw
+- check whether DealWatch is ready for a local read-only session
+- compare grocery product URLs before creating durable state
+- inspect watch tasks, watch groups, or recovery state 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 launch commands when the published package already
+exists.
+
+## Safe-first workflow
+
+1. `get_runtime_readiness`
+   Use this first when setup, environment, or startup truth is unclear.
+2. `compare_preview`
+   Use this first when the user wants to compare candidate grocery URLs without
+   creating tasks.
+3. `get_builder_starter_pack`
+   Use this when the user needs the integration contract or host setup path.
+4. `list_watch_tasks` or `list_watch_groups`
+   Use these after the first-safe path is already clear.
+5. `get_watch_task_detail` or `get_watch_group_detail`
+   Use these for one deeper read-only follow-up.
+6. `get_recovery_inbox`, `get_notification_settings`, or
+   `get_store_onboarding_cockpit`
+   Use these only after the user is already inside a recovery or operator
+   diagnostic workflow.
+
+## Tool-selection rule
+
+- Choose `compare_preview` for “Which URL is the right target?”
+- Choose `get_runtime_readiness` for “Is the local runtime healthy?”
+- Choose `get_builder_starter_pack` for “How do I connect an agent or host?”
+- Choose watch-task/group reads only after the user already has durable state to
+  inspect
+
+## 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
+
+- write-side MCP
+- hosted control plane
+- official marketplace or registry listing
+- autonomous recommendation support
+
+## Read next
+
+- `references/INSTALL.md`
+- `references/CAPABILITIES.md`
+- `references/DEMO.md`
+- `references/TROUBLESHOOTING.md`
diff --git a/skills/dealwatch-readonly-builder/manifest.yaml b/skills/dealwatch-readonly-builder/manifest.yaml
new file mode 100644
index 00000000..e5206da8
--- /dev/null
+++ b/skills/dealwatch-readonly-builder/manifest.yaml
@@ -0,0 +1,42 @@
+schema_version: 1
+artifact: public-skill-listing-manifest
+
+skill:
+  name: dealwatch-readonly-builder
+  display_name: DealWatch Read-only Builder
+  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/dealwatch-readonly-builder
+    submit_via: clawhub publish . --slug dealwatch-readonly-builder --name "DealWatch Read-only Builder" --version 1.1.1 --tags groceries,compare-first,mcp,read-only,dealwatch
+  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/dealwatch-readonly-builder/ in OpenHands/extensions
+
+boundaries:
+  product_identity: Local-first grocery comparison and watch-state inspection through the DealWatch read-only MCP.
+  canonical_repo_version: 1.0.1
+  official_listing_state: clawhub-live-other-hosts-pending
+  not_claimed:
+    - No hosted DealWatch control plane is claimed
+    - No write-capable MCP surface is claimed
+    - No autonomous recommendation support is claimed
+    - No first-party marketplace listing is claimed unless independently confirmed
+
+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
diff --git a/skills/dealwatch-readonly-builder/references/CAPABILITIES.md b/skills/dealwatch-readonly-builder/references/CAPABILITIES.md
new file mode 100644
index 00000000..263b04ac
--- /dev/null
+++ b/skills/dealwatch-readonly-builder/references/CAPABILITIES.md
@@ -0,0 +1,38 @@
+# DealWatch MCP Capabilities
+
+These are the stable read-only tools exposed by the published DealWatch MCP.
+
+## Safe-first tools
+
+1. `get_runtime_readiness`
+   - use first when setup, environment, or startup truth is unclear
+2. `compare_preview`
+   - use first when the user wants to compare candidate grocery URLs without
+     creating durable state
+3. `get_builder_starter_pack`
+   - use when the user needs the integration contract, launch commands, and
+     host setup path
+
+## Watch-task tools
+
+- `list_watch_tasks`
+- `get_watch_task_detail`
+
+Use these after the safe-first path is already clear.
+
+## Watch-group tools
+
+- `list_watch_groups`
+- `get_watch_group_detail`
+
+Use these after the user is already inside an existing watch-group flow.
+
+## Recovery and runtime follow-up
+
+- `get_recovery_inbox`
+- `list_notifications`
+- `get_notification_settings`
+- `list_store_bindings`
+- `get_store_onboarding_cockpit`
+
+Use these only after the safe-first path is grounded in a real runtime state.
diff --git a/skills/dealwatch-readonly-builder/references/DEMO.md b/skills/dealwatch-readonly-builder/references/DEMO.md
new file mode 100644
index 00000000..5387b07d
--- /dev/null
+++ b/skills/dealwatch-readonly-builder/references/DEMO.md
@@ -0,0 +1,34 @@
+# OpenHands / OpenClaw Demo Walkthrough
+
+This is the shortest concrete demo you can run to prove the skill is doing real
+work instead of only describing one.
+
+## Demo prompt
+
+Connect DealWatch, confirm whether the runtime is ready, and compare two
+candidate grocery URLs without creating any durable state.
+
+Start with `get_runtime_readiness`. If the runtime is healthy, run
+`compare_preview` on the submitted product URLs. Then explain which lane the
+user should choose next and why.
+
+## Expected tool sequence
+
+1. `get_runtime_readiness`
+2. `compare_preview`
+3. optionally `get_builder_starter_pack`
+
+## Visible success criteria
+
+- the agent reports whether the local runtime is ready
+- the compare step returns a real preview instead of creating durable state
+- the agent names the safest next lane instead of widening into write flows
+
+## What the output should look like
+
+Return a compact answer with:
+
+1. the chosen lane
+2. the next 1-3 actions
+3. one boundary reminder
+4. one exact MCP tool or install snippet
diff --git a/skills/dealwatch-readonly-builder/references/INSTALL.md b/skills/dealwatch-readonly-builder/references/INSTALL.md
new file mode 100644
index 00000000..fc1b4a6c
--- /dev/null
+++ b/skills/dealwatch-readonly-builder/references/INSTALL.md
@@ -0,0 +1,26 @@
+# Install The Published DealWatch MCP
+
+Use the published PyPI package, not a repo-local `PYTHONPATH=src` shortcut.
+
+## Published package
+
+- package: `dealwatch==1.0.1`
+- executable: `dealwatch-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
+
+```bash
+uvx --from dealwatch==1.0.1 dealwatch-mcp list-tools --json
+```
+
+If that command returns the tool inventory, the published MCP package is wired
+correctly.
diff --git a/skills/dealwatch-readonly-builder/references/OPENCLAW_MCP_CONFIG.json b/skills/dealwatch-readonly-builder/references/OPENCLAW_MCP_CONFIG.json
new file mode 100644
index 00000000..223e4807
--- /dev/null
+++ b/skills/dealwatch-readonly-builder/references/OPENCLAW_MCP_CONFIG.json
@@ -0,0 +1,10 @@
+{
+  "mcp": {
+    "servers": {
+      "dealwatch": {
+        "command": "uvx",
+        "args": ["--from", "dealwatch==1.0.1", "dealwatch-mcp", "serve"]
+      }
+    }
+  }
+}
diff --git a/skills/dealwatch-readonly-builder/references/OPENHANDS_MCP_CONFIG.json b/skills/dealwatch-readonly-builder/references/OPENHANDS_MCP_CONFIG.json
new file mode 100644
index 00000000..691e6705
--- /dev/null
+++ b/skills/dealwatch-readonly-builder/references/OPENHANDS_MCP_CONFIG.json
@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "dealwatch": {
+      "command": "uvx",
+      "args": ["--from", "dealwatch==1.0.1", "dealwatch-mcp", "serve"]
+    }
+  }
+}
diff --git a/skills/dealwatch-readonly-builder/references/README.md b/skills/dealwatch-readonly-builder/references/README.md
new file mode 100644
index 00000000..a58c0333
--- /dev/null
+++ b/skills/dealwatch-readonly-builder/references/README.md
@@ -0,0 +1,19 @@
+# DealWatch 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 output shape
+- `TROUBLESHOOTING.md`
+  - the first places to check when launch or compare fails
diff --git a/skills/dealwatch-readonly-builder/references/TROUBLESHOOTING.md b/skills/dealwatch-readonly-builder/references/TROUBLESHOOTING.md
new file mode 100644
index 00000000..027a1d9b
--- /dev/null
+++ b/skills/dealwatch-readonly-builder/references/TROUBLESHOOTING.md
@@ -0,0 +1,34 @@
+# DealWatch Troubleshooting
+
+Use this page when the packet looks right on paper but the first real attach or
+compare attempt still fails.
+
+## 1. The MCP server does not launch
+
+Check these first:
+
+- `uvx` is available on the machine
+- the package version in `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 skill is attach-ready.
+
+## 2. `get_runtime_readiness` fails
+
+That usually means the local DealWatch runtime is not healthy yet. Stop there
+and report the runtime problem before trying `compare_preview`.
+
+## 3. `compare_preview` fails
+
+Re-check:
+
+- the submitted URLs are valid and reachable
+- the runtime readiness step already passed
+- the user really wants a read-only compare, not a durable task or watch write
+
+## 4. Boundary reminder
+
+This packet is for the local-first, read-only DealWatch MCP surface. It does
+not claim a hosted control plane, a write-capable MCP lane, or autonomous
+recommendation support.
diff --git a/skills/dealwatch-readonly-builder/references/example-tasks.md b/skills/dealwatch-readonly-builder/references/example-tasks.md
new file mode 100644
index 00000000..c0cace02
--- /dev/null
+++ b/skills/dealwatch-readonly-builder/references/example-tasks.md
@@ -0,0 +1,15 @@
+# Example Tasks
+
+Use this skill bundle for tasks like:
+
+- “Connect DealWatch to OpenHands and check whether the runtime is ready.”
+- “Compare these grocery product URLs before creating any watch task.”
+- “Show me which DealWatch read-only tool I should call first.”
+- “Inspect one watch task or watch group without mutating state.”
+
+Return shapes should stay short and operational:
+
+1. chosen lane
+2. next 1-3 actions
+3. one boundary reminder
+4. one MCP tool or one install snippet
diff --git a/skills/dealwatch-readonly-builder/references/mcp-install.md b/skills/dealwatch-readonly-builder/references/mcp-install.md
new file mode 100644
index 00000000..0736131e
--- /dev/null
+++ b/skills/dealwatch-readonly-builder/references/mcp-install.md
@@ -0,0 +1,46 @@
+# Install The Published DealWatch MCP
+
+Use the published PyPI package, not a repo-local `PYTHONPATH=src` shortcut.
+
+## Published package
+
+- package: `dealwatch==1.0.1`
+- executable: `dealwatch-mcp`
+- transport: `stdio`
+
+## OpenHands example
+
+Add the server to `~/.openhands/config.toml`:
+
+```toml
+[mcp]
+stdio_servers = [
+  { name = "dealwatch", command = "uvx", args = ["--from", "dealwatch==1.0.1", "dealwatch-mcp", "serve"] }
+]
+```
+
+## OpenClaw example
+
+Add the server to your saved MCP server config:
+
+```json
+{
+  "mcp": {
+    "servers": {
+      "dealwatch": {
+        "command": "uvx",
+        "args": ["--from", "dealwatch==1.0.1", "dealwatch-mcp", "serve"]
+      }
+    }
+  }
+}
+```
+
+## Smoke check
+
+```bash
+uvx --from dealwatch==1.0.1 dealwatch-mcp list-tools --json
+```
+
+If that command returns the tool inventory, the published MCP package is wired
+correctly.
diff --git a/skills/dealwatch-readonly-builder/references/tool-map.md b/skills/dealwatch-readonly-builder/references/tool-map.md
new file mode 100644
index 00000000..61aa998f
--- /dev/null
+++ b/skills/dealwatch-readonly-builder/references/tool-map.md
@@ -0,0 +1,39 @@
+# DealWatch MCP Tool Map
+
+These are the stable read-only tools exposed by the published DealWatch MCP.
+
+## Safe-first tools
+
+1. `get_runtime_readiness`
+   Use first when the user needs to know whether the local runtime is ready.
+2. `compare_preview`
+   Use first when the user wants to compare submitted product URLs without
+   creating durable state.
+3. `get_builder_starter_pack`
+   Use when the user needs the integration contract, launch commands, and host
+   config guidance.
+
+## Watch-task tools
+
+- `list_watch_tasks`
+- `get_watch_task_detail`
+
+Use these after the user is already inside an existing watch-task flow.
+
+## Watch-group tools
+
+- `list_watch_groups`
+- `get_watch_group_detail`
+
+Use these after the user is already inside an existing watch-group flow.
+
+## Recovery and runtime follow-up
+
+- `get_recovery_inbox`
+- `list_notifications`
+- `get_notification_settings`
+- `list_store_bindings`
+- `get_store_onboarding_cockpit`
+
+Use these only after the safe-first path is clear and the user needs a deeper
+read-only diagnostic.