Repository navigation
fix: make Claude web skill ZIPs installable and verify the live workflow - #15
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Claude's real web uploader rejected the merged distribution: dependency trees exceeded its 200-file limit. A nested runtime ZIP was also rejected, and scoped license paths contained unsupported characters.
This change uses pinned esbuild to ship two plain JavaScript bundles per skill, with locked dependency metadata and individual licenses under portable paths. Each ZIP has 29 files, no nested archive and no consumer node_modules. Producer and distribution checks enforce upload constraints. Existing CLI, Claude Code plugin and optional API adapters retain their behavior.
Actual authenticated Claude web testing now passed on Free / Sonnet 5.5 Medium, Node 22.22.0 and Python 3.13.17:
The initial fixture used a .js specifier for a .ts file; that expected dependent regeneration did not occur because v0.1 deliberately leaves this edge unresolved. A separate extensionless-import control passed. This limitation and discarded installer candidates are recorded honestly in docs/claude-web-acceptance.md and the versioned account-test JSON. Semantic claim review is sampled, not proof of every explanation.
Validation: unlazy G0–G3 passed (archive safety, offline distribution, formatting, typecheck and full regression suite). Fresh independent instruction test passed 20/20 routing cases and current packaged build/reuse checks. All 9 remote CI jobs passed in run 39933500786: Linux Node22/24 each 504 passed/0 failed/0 skipped; Windows Node22/24 each 499 passed/0 failed/5 documented platform skips. Both offline web jobs passed 11 tests (Node22.14.0 and24), and existing plugin, quality evaluation and alpha packaging passed. The exact tested candidate hashes and stable packaged-file hashes are retained for comparison with clean CI artifacts.
This follows merged PR #14. No npm release or merge is performed here.
The clean CI artifact has valid checksums and all 112 non-provenance resources are byte-identical to the packages installed and exercised in Claude. Its synthetic merge tree matches this PR exactly. Download shcontext-web-skills from the linked run, extract the outer artifact, then upload the four individual ZIPs through Customize → Skills → Add skill → Upload skill. Unlazy: 8 met, 0 unmet, 0 abandoned. No remaining failed or blocked acceptance check. The declared .js→.ts resolution limitation remains documented.