Example Skill
npx machina-cli add skill cathy-kim/skill-semver/example-skill --openclawExample Skill
A simple example skill demonstrating version control structure
Version: 1.0.0 Last Updated: 2026-01-30
Purpose
This skill demonstrates the proper versioning structure:
- Version header in SKILL.md
- CHANGELOG.md for tracking changes
- releases/ folder for version snapshots
Usage
Just an example - customize for your needs.
Workflow
- Read input
- Process
- Output result
Source
git clone https://github.com/cathy-kim/skill-semver/blob/main/examples/example-skill/SKILL.mdView on GitHub Overview
The Example Skill showcases how to organize a skill for proper version control. It highlights using a Version header in SKILL.md, maintaining a CHANGELOG.md for changes, and storing version snapshots in a releases/ folder. This structure helps teams track releases consistently and simplifies rollback and auditing.
How This Skill Works
The skill content presents a minimal template that includes the Version header and Last Updated date in SKILL.md, plus a CHANGELOG.md and a releases/ folder for snapshots. Practically, teams update Version and Last Updated on each release, log changes in CHANGELOG.md, and commit a new snapshot under releases/.
When to Use It
- Documenting a new skill version for onboarding
- Teaching basic version control and release processes
- Auditing repository structure for consistency
- Preparing a sample project to illustrate releases
- Creating a reference implementation for training
Quick Start
- Step 1: Create SKILL.md with a Version: 1.0.0 header and Last Updated date
- Step 2: Add a CHANGELOG.md that records changes for the release
- Step 3: Create a releases/ folder and add a version snapshot for the release
Best Practices
- Always include a Version header in SKILL.md and keep it in sync with Last Updated
- Maintain a concise and chronological CHANGELOG.md
- Store stable version snapshots in releases/ to enable rollbacks
- Update both SKILL.md and CHANGELOG.md before publishing a release
- Document assumptions and scope in the Usage/Workflow sections
Example Use Cases
- A library that uses SKILL.md Version headers, a CHANGELOG.md, and a releases/ folder to manage npm package versions
- A training repository showing versioning structure for a sampleSkill with snapshots in releases/
- A component repository that demonstrates semantic versioning alongside an always-updated Last Updated date
- An onboarding project that teaches new developers how to release skill updates using the described files
- A demo app that snapshots each release under releases/ with a corresponding CHANGELOG entry
