Add TTS Engine to Voicebox
jamiepine/voicebox
Walks through adding a new text-to-speech engine to Voicebox end to end: dependency audit, backend, frontend wiring, PyInstaller bundling and frozen-build testing.
Extracts and validates semantic version strings from mixed text, parsing major, minor, patch, prerelease and build components with a fixed regular expression.
Install Semantic Version Parser
$ npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill extract-version -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install maslennikov-ig/claude-code-orchestrator-kit extract-version --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/extract-version .claude/skills/extract-version && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "extract-version" agent skill from https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/extract-version into .claude/skills/extract-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "extract-version", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/extract-versionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill extract-version -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install maslennikov-ig/claude-code-orchestrator-kit extract-version --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/extract-version .agents/skills/extract-version && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "extract-version" agent skill from https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/extract-version into .agents/skills/extract-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "extract-version", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill extract-version -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install maslennikov-ig/claude-code-orchestrator-kit extract-version --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/extract-version .cursor/skills/extract-version && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "extract-version" agent skill from https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/extract-version into .cursor/skills/extract-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "extract-version", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/maslennikov-ig/claude-code-orchestrator-kit.git --path .claude/skills/extract-version--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill extract-version -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install maslennikov-ig/claude-code-orchestrator-kit extract-version --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/extract-version .gemini/skills/extract-version && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "extract-version" agent skill from https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/extract-version into .gemini/skills/extract-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "extract-version", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install maslennikov-ig/claude-code-orchestrator-kit extract-versionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill extract-version -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/extract-version .github/skills/extract-version && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "extract-version" agent skill from https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/extract-version into .github/skills/extract-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "extract-version", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill extract-version -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install maslennikov-ig/claude-code-orchestrator-kit extract-version --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/maslennikov-ig/claude-code-orchestrator-kit.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/extract-version .opencode/skills/extract-version && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "extract-version" agent skill from https://github.com/maslennikov-ig/claude-code-orchestrator-kit/tree/main/.claude/skills/extract-version into .opencode/skills/extract-version/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "extract-version", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
extract-version- GitHub stars
- 260
- Token cost
- ~1k tokens
- SKILL.md length
- 268 words
- Files
- 1
- Skills in repo
- 29
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Extracts and validates semantic version strings from mixed text, parsing major, minor, patch, prerelease and build components with a fixed regular expression.
- Works in 5 steps: Receive Version Input → Extract Version Pattern → Parse Components → …
- Pulling a version number out of a changelog line or release note
- SKILL.md covers When to Use, Instructions, Error Handling and Examples, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
This skill parses version strings in formats such as a bare X.Y.Z, a v-prefixed version, one with a prerelease tag, one with build metadata, or the full combination of both, using a single regular expression to extract the major, minor, patch, prerelease and build components. It validates the result against the semantic versioning 2.0.0 specification, requiring major, minor and patch to be non-negative integers, restricting prerelease and build to allowed characters, and rejecting leading zeros in numeric identifiers other than zero itself.
Error handling covers three cases: no version pattern found in the input text, an invalid overall format, and a specific invalid component, each returned as a distinct error describing what went wrong. Worked examples cover a bare version, a v-prefixed version, a prerelease version, a full version with build metadata, and extracting a version embedded in a longer sentence such as a changelog line.
When your agent uses it
- Pulling a version number out of a changelog line or release note
- Validating that a version string follows semantic versioning
- Comparing two version numbers for ordering
- Normalizing version strings that use different prefixes or formats
Example prompts
- “Extract the semantic version from this changelog entry: Version: 0.8.0 released on 2025-10-17.”
- “Validate whether v1.2.3-beta.1 is a compliant semver string.”
- “Parse the major, minor and patch out of 2.0.0-beta.1+001.”
- “Compare these two version strings and tell me which is newer.”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
- Receive Version Input
- Extract Version Pattern
- Parse Components
- Validate Semver
- Return Parsed Data
What it can do on your machine
Read from SKILL.md and the folder at commit 8c3b576. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Semantic Version Parser loads about 1k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 268 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 268 words (~1,026 tokens).
“Parse semantic version strings and validate semver compliance.”
- name
- extract-version
Files
Just SKILL.md in .claude/skills/extract-version of maslennikov-ig/claude-code-orchestrator-kit.
Open the folder on GitHubat commit 8c3b576
Compare with similar skills
Semantic Version Parser next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Semantic Version Parser this skillmaslennikov-ig/claude-code-orchestrator-kit | 260 | — | ~1k | Automated safety check: Pass | Custom licence | |
| Add TTS Engine to Voiceboxjamiepine/voicebox | 57k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Dep Updatestrufflesecurity/trufflehog | 28k | — | ~1.3k | Automated safety check: Pass | AGPL-3.0 | |
| Merge Dependabot PRsonyx-dot-app/onyx | 32k | 1 repos | ~2.2k | Automated safety check: Pass | MIT | |
| Update .NET OS Packagesdotnet/core | 22k | — | ~2.3k | Automated safety check: Pass | MIT | |
| Pnpm Engineteambit/bit | 18k | — | ~1.9k | Automated safety check: Pass | Custom licence |
Similar skills
Dep Updates
trufflesecurity/trufflehog
Plan and apply Go dependency updates, including advisory-driven bumps, Trivy/govulncheck validation, and supply-chain review.
Merge Dependabot PRs
onyx-dot-app/onyx
Triages and lands a batch of open Dependabot PRs in the Onyx repo, where main is gated exclusively by GitHub's merge queue: approves and enqueues green PRs, closes superseded duplicates, fixes…
- Official
Update .NET OS Packages
dotnet/core
Audits and updates os-packages.json files listing the Linux packages each .NET release needs per distro, then regenerates the Markdown from the JSON.
Pnpm Engine
teambit/bit
Work on the pnpm Rust engine (@pnpm/napi, the pacquet crates) that bit install runs through.
- Official
Megatron-LM Container and Dependency Setup
NVIDIA/Megatron-LM
Walks an agent through working inside the Megatron-LM CI container and changing dependencies with uv, so lock files resolve the same locally and in CI.
More from maslennikov-ig/claude-code-orchestrator-kit
All 29 skills in this repoSenior Architect Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive software architecture skill for designing scalable, maintainable systems using ReactJS, NextJS, NodeJS, Express, React Native, Swift, Kotlin…
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
Senior Prompt Engineer
maslennikov-ig/claude-code-orchestrator-kit
Provides reference guides and Python scripts for prompt optimization, RAG evaluation, and agent orchestration when building or tuning LLM systems.
Priority Score Calculator
maslennikov-ig/claude-code-orchestrator-kit
Scores a bug, issue or task from severity, impact and likelihood on a 0-30 scale and maps the total to a P0 to P4 priority category with a suggested action.
Code Review with Beads Tasks
maslennikov-ig/claude-code-orchestrator-kit
Reviews staged changes, a branch, a PR or a path for bugs, security gaps and performance issues, then writes an evidence-based report and creates Beads tasks.
Conventional Commit Formatter
maslennikov-ig/claude-code-orchestrator-kit
Builds conventional commit messages from a type, optional scope, description and body, validates them and appends a Claude Code attribution footer.
Related
Categories
Questions about Semantic Version Parser
What does Semantic Version Parser do?
Extracts and validates semantic version strings from mixed text, parsing major, minor, patch, prerelease and build components with a fixed regular expression. Z, a v-prefixed version, one with a prerelease tag, one with build metadata, or the full combination of both, using a single regular expression to extract the major, minor, patch, prerelease and build components.0 specification, requiring major, minor and patch to be non-negative integers, restricting prerelease and build to allowed characters, and rejecting leading zeros in numeric identifiers other than zero itself.
When should I use Semantic Version Parser?
Semantic Version Parser fits situations like: pulling a version number out of a changelog line or release note; validating that a version string follows semantic versioning; comparing two version numbers for ordering; normalizing version strings that use different prefixes or formats.
How do I install Semantic Version Parser in Claude Code?
Run `npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill extract-version -a claude-code`. Or copy the skill folder (.claude/skills/extract-version in maslennikov-ig/claude-code-orchestrator-kit) into .claude/skills/extract-version in your project. Claude Code loads it when a task matches its description.
How do I install Semantic Version Parser in Codex?
Run `npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill extract-version -a codex`. Or copy the skill folder (.claude/skills/extract-version in maslennikov-ig/claude-code-orchestrator-kit) into .agents/skills/extract-version in your project. Codex loads it when a task matches its description.
Can I use Semantic Version Parser in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add maslennikov-ig/claude-code-orchestrator-kit --skill extract-version -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/extract-version, .gemini/skills/extract-version, .github/skills/extract-version and .opencode/skills/extract-version in your project.
What does Semantic Version Parser need to run?
SKILL.md names no scripts, command-line tools or credentials: Semantic Version Parser is instructions for the agent only.
Does Semantic Version Parser access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Semantic Version Parser safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Semantic Version Parser use?
Semantic Version Parser has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Semantic Version Parser use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Semantic Version Parser?
Skills that share tags, products or a category with Semantic Version Parser: Add TTS Engine to Voicebox (jamiepine/voicebox, 57k stars), Dep Updates (trufflesecurity/trufflehog, 28k stars), Merge Dependabot PRs (onyx-dot-app/onyx, 32k stars) and Update .NET OS Packages (dotnet/core, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Semantic Version Parser?
maslennikov-ig (a GitHub user) maintains it in maslennikov-ig/claude-code-orchestrator-kit, which has 260 GitHub stars. The repository holds 29 skills in this directory. The repository was last updated on March 5, 2026.
Source: maslennikov-ig/claude-code-orchestrator-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.