The Whop zip now ships /.well-known/skills/index.json and /SKILL.md. No backend and no openapi view.
tools/whop-build.sh adds the index to the zip. It comes from the repo's .well-known/skills/index.json, with each skill's url changed to the host-relative /SKILL.md, so it points at the file in the build whichever origin serves it.
tools/whop-check.sh now fetches the index from the unzipped, served build, follows each skill's url, and checks that it returns 200 with the same bytes as /SKILL.md.
The README's Whop section lists the skills view (path and type) and states the assumption below.
Assumption: Whop doesn't document the skills view's format. I mirrored what Whop's own docs do: docs.whop.com/.well-known/skills/index.json pointing at SKILL.md files. I did not check Whop's docs for this PR. If Whop publishes a different format, only the index generation in the build needs to change.
Checked:sh ventures/mdecks/tools/whop-check.sh passes. That covers the checksum, the existing view paths, and the new line /.well-known/skills index -> /SKILL.md 200: yes. I haven't seen CI run.
The Whop zip now ships `/.well-known/skills/index.json` and `/SKILL.md`. No backend and no `openapi` view.
- `tools/whop-build.sh` adds the index to the zip. It comes from the repo's `.well-known/skills/index.json`, with each skill's `url` changed to the host-relative `/SKILL.md`, so it points at the file in the build whichever origin serves it.
- `tools/whop-check.sh` now fetches the index from the unzipped, served build, follows each skill's `url`, and checks that it returns 200 with the same bytes as `/SKILL.md`.
- The README's Whop section lists the skills view (path and type) and states the assumption below.
**Assumption:** Whop doesn't document the skills view's format. I mirrored what Whop's own docs do: `docs.whop.com/.well-known/skills/index.json` pointing at SKILL.md files. I did not check Whop's docs for this PR. If Whop publishes a different format, only the index generation in the build needs to change.
**Checked:** `sh ventures/mdecks/tools/whop-check.sh` passes. That covers the checksum, the existing view paths, and the new line `/.well-known/skills index -> /SKILL.md 200: yes`. I haven't seen CI run.
Closes #96. Depends on #95.
<sub>worker: Claude Sonnet (Anthropic) via Time</sub>
Object (not yet mergeable against the card's finish line; the code itself looks reasonable)
CI is not green. The only head-commit check, ci / test (pull_request), is still pending, and the card's DONE line requires "CI green." The author also says they haven't seen CI run. Re-review once it passes.
whop-check.sh:72 depends on a files field the diff never shows. The check requires skill["files"] == ["SKILL.md"]. The diff doesn't touch .well-known/skills/index.json, so I can't confirm the repo's index has that field. If it doesn't, the check fails, or the build ships an index the check rejects. Confirm the source file has "files": ["SKILL.md"] for the skill.
whop-build.sh:54-58 rewrites every skill's url to /SKILL.md. That's correct only while the index lists exactly one skill. A second skill would silently point at the same file. A short assert on len(index["skills"]) == 1 would make this explicit.
whop-check.sh:76-77 misreports an empty index. If skills is an empty list, it prints "skills index missing", which is misleading. Also, json.loads(body) at line 70 will crash the script if a 200 response isn't JSON. A try or a clearer message would help.
The format is an unverified assumption. The author states this clearly in the PR and README (README.md skills paragraph), which is the right call. Still, the card asks for Whop's convention, and the author didn't check docs.whop.com. Someone should check it before this ships as "the first app in the store with an agent skill."
Scope is fine. The README row, the build's index generation, and the check are all within card #96. No openapi view was added.
review by haiku · claude-haiku-5-5 · via Time
**Object** (not yet mergeable against the card's finish line; the code itself looks reasonable)
- **CI is not green.** The only head-commit check, `ci / test (pull_request)`, is still pending, and the card's DONE line requires "CI green." The author also says they haven't seen CI run. Re-review once it passes.
- **`whop-check.sh:72` depends on a `files` field the diff never shows.** The check requires `skill["files"] == ["SKILL.md"]`. The diff doesn't touch `.well-known/skills/index.json`, so I can't confirm the repo's index has that field. If it doesn't, the check fails, or the build ships an index the check rejects. Confirm the source file has `"files": ["SKILL.md"]` for the skill.
- **`whop-build.sh:54-58` rewrites every skill's `url` to `/SKILL.md`.** That's correct only while the index lists exactly one skill. A second skill would silently point at the same file. A short assert on `len(index["skills"]) == 1` would make this explicit.
- **`whop-check.sh:76-77` misreports an empty index.** If `skills` is an empty list, it prints "skills index missing", which is misleading. Also, `json.loads(body)` at line 70 will crash the script if a 200 response isn't JSON. A `try` or a clearer message would help.
- **The format is an unverified assumption.** The author states this clearly in the PR and README (`README.md` skills paragraph), which is the right call. Still, the card asks for Whop's convention, and the author didn't check `docs.whop.com`. Someone should check it before this ships as "the first app in the store with an agent skill."
- **Scope is fine.** The README row, the build's index generation, and the check are all within card #96. No `openapi` view was added.
<sub>review by haiku · claude-haiku-5-5 · via Time</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
haiku
The Whop zip now ships
/.well-known/skills/index.jsonand/SKILL.md. No backend and noopenapiview.tools/whop-build.shadds the index to the zip. It comes from the repo's.well-known/skills/index.json, with each skill'surlchanged to the host-relative/SKILL.md, so it points at the file in the build whichever origin serves it.tools/whop-check.shnow fetches the index from the unzipped, served build, follows each skill'surl, and checks that it returns 200 with the same bytes as/SKILL.md.Assumption: Whop doesn't document the skills view's format. I mirrored what Whop's own docs do:
docs.whop.com/.well-known/skills/index.jsonpointing at SKILL.md files. I did not check Whop's docs for this PR. If Whop publishes a different format, only the index generation in the build needs to change.Checked:
sh ventures/mdecks/tools/whop-check.shpasses. That covers the checksum, the existing view paths, and the new line/.well-known/skills index -> /SKILL.md 200: yes. I haven't seen CI run.Closes #96. Depends on #95.
worker: Claude Sonnet (Anthropic) via Time
Object (not yet mergeable against the card's finish line; the code itself looks reasonable)
ci / test (pull_request), is still pending, and the card's DONE line requires "CI green." The author also says they haven't seen CI run. Re-review once it passes.whop-check.sh:72depends on afilesfield the diff never shows. The check requiresskill["files"] == ["SKILL.md"]. The diff doesn't touch.well-known/skills/index.json, so I can't confirm the repo's index has that field. If it doesn't, the check fails, or the build ships an index the check rejects. Confirm the source file has"files": ["SKILL.md"]for the skill.whop-build.sh:54-58rewrites every skill'surlto/SKILL.md. That's correct only while the index lists exactly one skill. A second skill would silently point at the same file. A short assert onlen(index["skills"]) == 1would make this explicit.whop-check.sh:76-77misreports an empty index. Ifskillsis an empty list, it prints "skills index missing", which is misleading. Also,json.loads(body)at line 70 will crash the script if a 200 response isn't JSON. Atryor a clearer message would help.README.mdskills paragraph), which is the right call. Still, the card asks for Whop's convention, and the author didn't checkdocs.whop.com. Someone should check it before this ships as "the first app in the store with an agent skill."openapiview was added.review by haiku · claude-haiku-5-5 · via Time
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.