From 66edaf830d04b5f05195408cc79605f2f905593e Mon Sep 17 00:00:00 2001 From: Chip Lay Date: Thu, 10 Sep 2026 01:49:49 +0000 Subject: [PATCH 1/2] skills(sightkick-debug): end with a "get listed" step for the Sightmap Atlas Once `sightmap browser mcp list` confirms the tools on the deployed URL, the last step is to submit the site: POST to sightmap.org/api/atlas/submit, or call the Atlas page's own submit_site tool. A maintainer reviews every listing before it appears. The embedded copy is regenerated. Co-Authored-By: Claude Fable 5.1 Claude-Session: https://claude.ai/code/session_01NpEUDK1MADpEDitJ3Px7D4 Signed-off-by: Chip Lay --- generator/skills/sightkick-debug/SKILL.md | 13 +++++++++++++ skills/sightkick-debug/SKILL.md | 13 +++++++++++++ 2 files changed, 26 insertions(+) diff --git a/generator/skills/sightkick-debug/SKILL.md b/generator/skills/sightkick-debug/SKILL.md index df857d0..5dee4f0 100644 --- a/generator/skills/sightkick-debug/SKILL.md +++ b/generator/skills/sightkick-debug/SKILL.md @@ -239,3 +239,16 @@ rm -rf /tmp/sk-dbg - **A stale daemon collides** — `sightmap browser stop` before `start`, and give `--detach` a beat for the content tab to open before page commands (poll `status` / `wait-for`). + +## Get listed + +Once the tools register on your **deployed** URL, submit the site to the +Sightmap Atlas so other agents can find it: + +```sh +curl -X POST https://sightmap.org/api/atlas/submit -H 'content-type: application/json' \ + -d '{"url": "", "email": "", "owner": true, "sightkick": true}' +``` + +Or open in a WebMCP-capable session and call its +`submit_site` tool. A maintainer reviews every listing before it appears. diff --git a/skills/sightkick-debug/SKILL.md b/skills/sightkick-debug/SKILL.md index df857d0..5dee4f0 100644 --- a/skills/sightkick-debug/SKILL.md +++ b/skills/sightkick-debug/SKILL.md @@ -239,3 +239,16 @@ rm -rf /tmp/sk-dbg - **A stale daemon collides** — `sightmap browser stop` before `start`, and give `--detach` a beat for the content tab to open before page commands (poll `status` / `wait-for`). + +## Get listed + +Once the tools register on your **deployed** URL, submit the site to the +Sightmap Atlas so other agents can find it: + +```sh +curl -X POST https://sightmap.org/api/atlas/submit -H 'content-type: application/json' \ + -d '{"url": "", "email": "", "owner": true, "sightkick": true}' +``` + +Or open in a WebMCP-capable session and call its +`submit_site` tool. A maintainer reviews every listing before it appears. From f6aa6ed748a7f6f6d5c0eabd19306463d772d4dc Mon Sep 17 00:00:00 2001 From: Chip Lay Date: Thu, 10 Sep 2026 21:34:56 +0000 Subject: [PATCH 2/2] skills(sightkick-debug): make the Atlas listing optional and claimed The last step now reads as what it is: optional, for an owner who wants the site shown in the Sightmap Atlas. Before the deploy that ships the tools the agent generates a token and writes it into webmcp.txt as a `# sightmap-claim:` comment line, then submits with the same token as `claim` and reports the card URL that comes back. The card is shareable at once; the Atlas listing still waits on a maintainer's review. Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01NpEUDK1MADpEDitJ3Px7D4 Signed-off-by: Chip Lay --- generator/skills/sightkick-debug/SKILL.md | 37 ++++++++++++++++++++--- skills/sightkick-debug/SKILL.md | 37 ++++++++++++++++++++--- 2 files changed, 64 insertions(+), 10 deletions(-) diff --git a/generator/skills/sightkick-debug/SKILL.md b/generator/skills/sightkick-debug/SKILL.md index 5dee4f0..482f30c 100644 --- a/generator/skills/sightkick-debug/SKILL.md +++ b/generator/skills/sightkick-debug/SKILL.md @@ -240,15 +240,42 @@ rm -rf /tmp/sk-dbg `--detach` a beat for the content tab to open before page commands (poll `status` / `wait-for`). -## Get listed +## Optional: show your work in the Sightmap Atlas -Once the tools register on your **deployed** URL, submit the site to the -Sightmap Atlas so other agents can find it: +Nothing below is required: any agent that opens the site can use the tools as +soon as they are live. Do it if the owner wants the site shown in the Sightmap +Atlas. + +**Before the deploy that ships the tools**, generate a claim token and put it in +`webmcp.txt`, the plain-text tool list served from the site root: + +```sh +openssl rand -hex 16 # 32 hex characters; keep it, the submission reuses it +``` + +```text +https://yourdomain.com +# sightmap-claim: 8f3c1d90a4b27e6510fd2c83b9a4e7d1 +search_flights — find fares between two airports on a date +select_fare — pick one of the fares a search returned +``` + +Lines starting with `#` are comments and readers ignore them. The token shows +the domain is the owner's; it is only ever compared against that file. + +Deploy, confirm the tools register on the deployed URL, then submit with the +same token: ```sh curl -X POST https://sightmap.org/api/atlas/submit -H 'content-type: application/json' \ - -d '{"url": "", "email": "", "owner": true, "sightkick": true}' + -d '{"url": "", "email": "", "owner": true, "sightkick": true, "claim": ""}' ``` Or open in a WebMCP-capable session and call its -`submit_site` tool. A maintainer reviews every listing before it appears. +`submit_site` tool. A `422` naming `claim-unreachable` or `claim-mismatch` means +the deployed `webmcp.txt` does not carry that line — fix the file and resubmit. + +A submission that carries the claim answers with a card URL, +`https://sightmap.org/try/`, which the owner can share immediately; report +it. The Atlas listing itself appears only after a maintainer reviews the +submission. diff --git a/skills/sightkick-debug/SKILL.md b/skills/sightkick-debug/SKILL.md index 5dee4f0..482f30c 100644 --- a/skills/sightkick-debug/SKILL.md +++ b/skills/sightkick-debug/SKILL.md @@ -240,15 +240,42 @@ rm -rf /tmp/sk-dbg `--detach` a beat for the content tab to open before page commands (poll `status` / `wait-for`). -## Get listed +## Optional: show your work in the Sightmap Atlas -Once the tools register on your **deployed** URL, submit the site to the -Sightmap Atlas so other agents can find it: +Nothing below is required: any agent that opens the site can use the tools as +soon as they are live. Do it if the owner wants the site shown in the Sightmap +Atlas. + +**Before the deploy that ships the tools**, generate a claim token and put it in +`webmcp.txt`, the plain-text tool list served from the site root: + +```sh +openssl rand -hex 16 # 32 hex characters; keep it, the submission reuses it +``` + +```text +https://yourdomain.com +# sightmap-claim: 8f3c1d90a4b27e6510fd2c83b9a4e7d1 +search_flights — find fares between two airports on a date +select_fare — pick one of the fares a search returned +``` + +Lines starting with `#` are comments and readers ignore them. The token shows +the domain is the owner's; it is only ever compared against that file. + +Deploy, confirm the tools register on the deployed URL, then submit with the +same token: ```sh curl -X POST https://sightmap.org/api/atlas/submit -H 'content-type: application/json' \ - -d '{"url": "", "email": "", "owner": true, "sightkick": true}' + -d '{"url": "", "email": "", "owner": true, "sightkick": true, "claim": ""}' ``` Or open in a WebMCP-capable session and call its -`submit_site` tool. A maintainer reviews every listing before it appears. +`submit_site` tool. A `422` naming `claim-unreachable` or `claim-mismatch` means +the deployed `webmcp.txt` does not carry that line — fix the file and resubmit. + +A submission that carries the claim answers with a card URL, +`https://sightmap.org/try/`, which the owner can share immediately; report +it. The Atlas listing itself appears only after a maintainer reviews the +submission.