submit-repo API returns Cloudflare Worker 1101 #34
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
rtlabs-llm-agents/agent-skills-cli#34
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
skills submit-repocannot reach the marketplace indexing step because the public submit endpoint returns a Cloudflare Worker exception.Reproduction
The CLI first hits the unauthenticated GitHub API and may encounter its shared rate limit. Calling the endpoint with the same payload the CLI constructs reproduces the server error directly:
Actual result
Reproduced twice on 2026-08-27.
Expected result
A success response, or a documented 4xx response for invalid/duplicate submissions. It may also help if the CLI can use an authenticated GitHub token when one is already configured, so repository discovery does not depend on the shared unauthenticated rate limit.
The reproduction repository is public, Apache-2.0 licensed, and contains one
SKILL.mdatskills/sandbase/SKILL.md.Update from 2026-08-27: the failure mode has changed, but submission still does not reach indexing.
npx -y [email protected] submit-repo sandbaseai/clinow stops at the CLI's unauthenticated GitHub lookup withGitHub API error: 403. Posting to the documented endpoint returns HTTP 404 with:An authenticated GitHub API check confirms the repository is public and currently reports:
mainskills/sandbase/SKILL.mdThe
SKILL.mdhas validnameanddescriptionfrontmatter. If the shared API rate limit cannot be fixed immediately, could this repository be queued for manual indexing from the verified fields above?