My collection of Claude skills -- primarily used for the Claude.ai PaaS skill compute environment, mileage will vary if attempted used as Claude Code Agent Skills
- To install a skill in Claude.ai you first need a paid account (Claude Pro or Team)
- Download the skill ZIP from the Releases page
- Note: Each release includes a direct download link for the skill ZIP - use that, not the "Source code" archives auto-generated by GitHub
- Upload to Claude.ai Skills Settings
- See official documentation for more details
(Not actually sure about the workflow for a forked repo back to mine -- someone will have to test and report, but within your own fork:...)
- Create your skill folder with
SKILL.mdat the root - Package your skill:
# Correct structure: your-skill.zip └── your-skill/ ├── SKILL.md └── resources/ (optional) # NOTE: Do NOT include a VERSION file in your ZIP # VERSION files are workflow metadata and will be ignored
- Upload the ZIP to the
uploads/directory - The workflow will automatically create a PR with your skill content
- When ready to release, update the VERSION file separately (see "Releasing Skills" below)
- Create a new branch
- Add your skill folder at the repository root (SKILL.md and resources)
- Submit a PR with your skill content
- When ready to release, update the VERSION file separately (see "Releasing Skills" below)
Important: VERSION files are workflow metadata, separate from skill content.
- Releases are triggered explicitly by updating VERSION files on main branch
- Simply changing skill content does NOT trigger a release
- This separation allows you to iterate on skills without creating releases for every change
- Develop & Update: Upload ZIPs or edit skill files directly → PRs update skill content in repo
- Release When Ready: Update VERSION file → Automatic release created with downloadable ZIP
-
Update the
VERSIONfile in your skill folder:echo "1.1.0" > your-skill/VERSION
-
Commit and push (or merge PR):
git add your-skill/VERSION git commit -m "chore: bump your-skill to v1.1.0" git push -
The workflow will automatically:
- Create a properly structured ZIP file (VERSION excluded - it's not part of the skill)
- Generate a GitHub release with tag
your-skill-v1.1.0 - Attach the ZIP as a release asset
- Generate release notes from recent commits
- Users download this ZIP to install the skill
You can also trigger a release manually via GitHub Actions:
- Go to Actions → Release Skill → Run workflow
- Enter the skill folder name
- Optionally specify a version (otherwise uses VERSION file)
Use semantic versioning:
1.0.0- Initial release1.0.1- Patch (bug fixes)1.1.0- Minor (new features, backward compatible)2.0.0- Major (breaking changes)