Submit a Skill
Import from a GitHub repository, claim an existing skill route, or paste a direct SKILL.md URL, then analyze before anything is submitted.
Run analysis to inspect owner, title, duplicate matches, and warnings before creating a pending submission.
Account context
Sign in before you move drafts into dashboard, creator claims, and submission review.
We scan repositories for SKILL.md files, or match an existing @owner/skill route, before anything is submitted.
We couldn't analyze that source.
Ready to submit
PendingReview the imported draft. The next step creates a pending submission only.
Possible duplicates
- No duplicates yet
Pending submission created
PendingYour draft is saved as a pending submission. Open the success page or dashboard to continue.
Is this your skill?
Connect GitHub to claim ownership and move into the verification flow.
1
Connect GitHub to claim ownership.
2
Skills from your repos or orgs are auto-linked.
3
Verification unlocks the richer publishing and review surface.
Webhook sync
https://findskill.top/api/webhooks/githubConnect a GitHub repository to keep your dashboard in sync when webhook deliveries arrive.
Submission checklist
1
Make sure the repository has a directly discoverable SKILL.md entrypoint.
2
Include platform tags, install hints, and clear ownership metadata.
3
After import, review the generated detail, Quality, and Security routes.
What happens next
StageSystem actionWhat you verifyNext route
Analyze
Scan repo and infer platform/tags
Entrypoint and ownership
/submit/
Ready
Review preview and duplicate matches
Pending submission only
/submit/
Submitted
Create a pending submission record
Success page and dashboard links
/submit/success/
Verification FAQ
Who can claim a submitted skill?
By default the matching GitHub repo or org owner can claim it; everyone else needs extra verification.
Why does the imported copy differ from the repo readme?
The marketplace prioritizes SKILL.md and install metadata rather than a generic project readme.