Automated summary
Automates the preparation and publication of a new release for the cryptobot-python package.
Strengths
- Reduces manual errors by automating version file updates
- Runs tests before release to ensure quality
- Creates a git tag and GitHub release automatically
Limitations
- Specific to the cryptobot-python project structure (pyproject.toml, HISTORY.md)
- Requires gh (GitHub CLI) to be installed and configured
- Assumes make test is available and passes
When you need to publish a new version of the cryptobot-python package, e.g., after accumulating changes.
For projects not using pyproject.toml or a HISTORY.md file, or if you prefer a manual release process.
Security analysis
CautionThe skill uses powerful tools like `make` and `gh` for release management. No destructive or exfiltration commands, but `make test` could run arbitrary code without user verification.
- •The skill instructs to run `make test` which executes potentially arbitrary commands from a Makefile. While likely legitimate for the project, it introduces execution risk if the Makefile is compromised.
Examples
Cut a release for cryptobot-python version 0.4.2Prepare and publish a new release with version 1.0.0 for cryptobot-pythonCreate a release for cryptobot-python version 0.5.0, I will provide the release notes after you start.name: release description: Prepare and publish a new cryptobot-python release. Use when the user asks to cut a release, bump the package version, update HISTORY.md, create a git tag, or create a GitHub release.
Release Skill
Create a new release for the cryptobot-python package.
Usage
/release <version>
Where <version> is the new semantic version (e.g., 0.4.2, 0.5.0, 1.0.0).
Instructions
When the user invokes this skill with a version number, perform the following steps:
-
Validate the version: Ensure the version follows semantic versioning (X.Y.Z format).
-
Update version files:
- Update
versioninpyproject.toml - Update
__version__incryptobot/__init__.py
- Update
-
Ask for release notes: Ask the user what changes should be included in the release notes.
-
Update HISTORY.md: Add a new entry at the top of the History section with:
- Version number and today's date
- The release notes provided by the user
-
Run tests: Execute
make testto ensure all tests pass before proceeding. -
Create commit: Create a commit with message
chore(release): prepare v<version> release -
Create tag: Create an annotated git tag
v<version>pointing to the release commit. -
Create GitHub release: Use
gh release createto create a GitHub release with:- Tag:
v<version> - Title:
v<version> - Release notes from the HISTORY.md entry
- Tag:
-
Report completion: Provide the user with:
- Summary of files changed
- Link to the GitHub release
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/release-cryptobot-python-package-mmio722s/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/release-cryptobot-python-package-mmio722s' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/release-cryptobot-python-package-mmio722s/download' --output '.skill-downloads/release-cryptobot-python-package-mmio722s/SKILL.md.part' && mv '.skill-downloads/release-cryptobot-python-package-mmio722s/SKILL.md.part' '.skill-downloads/release-cryptobot-python-package-mmio722s/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/release-cryptobot-python-package-mmio722s/SKILL.md' && test -s '.skill-downloads/release-cryptobot-python-package-mmio722s/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/release' && cp -R '.skill-downloads/release-cryptobot-python-package-mmio722s' '.claude/skills/release'Cursor
test -f '.skill-downloads/release-cryptobot-python-package-mmio722s/SKILL.md' && test -s '.skill-downloads/release-cryptobot-python-package-mmio722s/SKILL.md' && mkdir -p '.cursor/skills' && test ! -e '.cursor/skills/release' && cp -R '.skill-downloads/release-cryptobot-python-package-mmio722s' '.cursor/skills/release'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/release-cryptobot-python-package-mmio722s'openskills read 'release-cryptobot-python-package-mmio722s'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/release-cryptobot-python-package-mmio722s/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
Configure a Chat Channel with SecretRefs
DevOps
Set up chat channels using non-interactive commands, with secrets only as SecretRefs. Covers gather, mutate, repair, and prove steps for reliable delivery.
Investigate ClickHouse CI Failures
DevOps
Investigate a ClickHouse CI failure end-to-end from a PR or S3 report URL. Fetches failed tests, classifies flaky vs real regression, and checks for existing issues/fixes.
Ansible PR Review
DevOps
Reviews an Ansible PR following the project's standardized process, including changelog checks, test coverage validation, and feedback tracking.