skillshare-release
Prepare and review skillshare releases using the Release Please PR, verify the proposed version and changelog, inspect draft assets, and publish through the manual Publish Release workflow when explicitly authorized
Install / Use
npx skills add runkids/skillshare --skill skillshare-releaseInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of skillshare-release
skillshare-release scores 90/100 on our quality scale, 1207th of 2,790 Automation skills we index (top 44%).
Its SKILL.md is 4.4 KB long, well organised into 12 sections with 5 code examples: a solid amount of guidance for an agent.
With 2,689 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so skillshare-release is actively maintained.
- Our last check on 2026-10-30 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-30. Automated pattern scan on 2026-09-29. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
skillshare-release compared with similar skills
All 4 of these similar skills score higher than skillshare-release; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| skillshare-release (this skill)by runkids | 90 | 2.7k | 54d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| Claude-Code-Game-Studiosby Donchitos | 100 | 39.7k | 7d ago | CLAUDE.md |
| Scraplingby D4Vinci | 100 | 103.6k | 2d ago | MCP Server |
Frequently asked questions
- How do I install skillshare-release?
- Run
npx skills add runkids/skillshare --skill skillshare-release. The install tabs above show the steps for each supported agent. - Which AI agents does skillshare-release work with?
- It is written for Claude Code and Zed, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is skillshare-release safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is skillshare-release still maintained?
- The repository was last updated about 2 months ago, so skillshare-release is actively maintained.
Skill content
View source on GitHubname: skillshare-release description: >- End-to-end release workflow for skillshare. Runs tests, generates changelog (via /changelog), optionally writes local RELEASE_NOTES, updates version numbers, commits, and drafts announcements. Use when the user says "release", "prepare release", "cut a release", "release v0.19", or any request to publish a new version. For changelog-only tasks, use /changelog instead. argument-hint: "<version>" metadata: targets: [claude, universal]
End-to-end release workflow for skillshare. $ARGUMENTS specifies the version (e.g., v0.19.0).
Before acting, run python3 scripts/ai-context.py release testing. Those topics are the source of truth for authorization, release artifacts and verification; this skill retains the release orchestration and draft formats.
Prerequisites
- All feature work merged to current branch
- Working directory clean (
git statusshows no uncommitted changes)
Workflow
Phase 1: Validate
Run full test suite and code quality checks. Fix any failures before proceeding.
make check # fmt-check + lint + test (builds binary first)
If tests fail: fix them, don't skip. Do not ask the user — fix and re-run.
Phase 2: Changelog
Invoke /changelog $VERSION to generate the changelog entry.
This handles:
- Collecting commits since last tag
- Categorizing by conventional commit type
- Writing user-facing CHANGELOG.md entry
- Syncing website changelog (
website/src/pages/changelog.md)
Review the output before proceeding.
Phase 3: Release Notes Draft (Maintainer Only, Local by Default)
Check if running as maintainer:
git config user.name # Should match "Willie" or maintainer identity
If maintainer:
Read the most recent specs/RELEASE_NOTES_*.md as a style reference, then generate specs/RELEASE_NOTES_<version>.md (no v prefix, e.g., RELEASE_NOTES_0.19.0.md).
Release notes are a local maintainer artifact by default. The specs/ directory is gitignored; do not force-add or commit specs/RELEASE_NOTES_<version>.md unless the user explicitly asks for release notes to be committed.
Structure:
- Title:
# skillshare vX.Y.Z Release Notes - TL;DR section with numbered highlights
- One
##section per feature/fix — describe what changed in plain language, with a CLI example or code block if relevant - Include migration guide if breaking changes exist
Wording rules (same user-facing standard as CHANGELOG):
- Describe what changed from the user's perspective, not how the code changed
- Never mention: function names, variable names, struct fields, file paths, Go syntax, internal APIs
- ✅ Good: "Sync now auto-creates missing target directories and shows what it did"
- ❌ Bad: "upgraded
Server.mufromsync.Mutextosync.RWMutexand applied a snapshot pattern across 30 handlers" - Keep it concise — a short paragraph per feature is enough
If not maintainer: Skip this phase.
Phase 4: Version Bump
Update the version in skills/skillshare/SKILL.md frontmatter:
metadata:
version: vX.Y.Z
This ensures skillshare upgrade --skill detects the new version correctly.
Phase 5: Commit & Tag
Commit and tag only when the release request includes it or the user confirms; the tag is what publishes.
git add CHANGELOG.md website/src/pages/changelog.md skills/skillshare/SKILL.md
# Only if the user explicitly asked to commit release notes:
# git add -f specs/RELEASE_NOTES_<version>.md
git commit -m "chore: release vX.Y.Z"
git tag vX.Y.Z
Do NOT push yet — wait for user confirmation.
Phase 6: Draft Announcements
Prepare two drafts for user review:
-
GitHub Release Notes — concise, user-facing summary suitable for the GitHub release page. Shorter than RELEASE_NOTES, highlight top 3-5 changes with one-liners.
-
Social media post — 2-3 sentences max, casual tone, mention the version and 1-2 headline features. No hashtag spam.
Tone: short, direct. Don't oversell. The user will edit before posting.
Phase 7: Present & Confirm
Show the user:
- [ ] Test results (pass/fail)
- [ ] CHANGELOG.md diff
- [ ] RELEASE_NOTES file (if generated, and whether it was left local or committed)
- [ ] Version bump diff
- [ ] GitHub release draft
- [ ] Social media draft
Wait for user approval before pushing:
git push origin HEAD --tags
Rules
Apply release and testing. Never infer permission to push or publish from preparation work.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Claude-Code-Game-Studios
39.7kTurn Claude Code into a full game dev studio — 49 AI agents, 72 workflow skills, and a complete coordination system mirroring real studio hierarchy.
Scrapling
103.6k🕷️ The BEST Web Scraping framework that handles everything from a single request to a full-scale crawl! Don't be shy, join here: https://discord.gg/EMgGbDceNQ and follow here for daily tips and tricks: https://x.com/Scrapling_dev
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
