release-versioning

How xberg versions are synced and released — Cargo.toml is the single source of truth, `task version:sync` propagates it to alef-managed binding manifests AND the integrations under integrations/, which are versioned and published in lockstep with core (including -rc.N). Load before bumping a version, editing the version-sync task, or touching an integration's version/xberg dependency.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable instruction skill with concrete commands, a clear sync workflow, and explicit drift validation. Minor room to tighten illustrative version examples and to spell out an error-recovery loop after `version:check` fails.

Suggestions

Add an explicit 'If `task version:check` fails: re-run `task version:sync`, then re-check' feedback loop to lift workflow clarity to the top anchor.

Trim or generalize the illustrative version numbers (e.g., `1.0.0-rc.32` → `1.0.0-rc.N`) to reduce time-sensitive-looking detail.

Consider a one-line summary of the sync order at the top of the propagation section so the two-family ordering is scannable before the numbered list.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence throughout; the PEP 440 rationale and Do/Don't lists earn their place, with only minor instances (e.g., the illustrative version-number examples) that could be trimmed.	4 / 5
Actionability	Fully executable guidance with concrete commands (`task version:sync`, `task version:bump:*`, `task version:set`, `task version:check`), exact file paths, and named config keys (`VERSION_TARGETS`, `XBERG_DEP_MANIFESTS`, `NPM_MANIFESTS`) covering the common cases.	5 / 5
Workflow Clarity	Clear ordered sequence (numbered sync steps, chaining bump helpers) with an explicit validation checkpoint (`task version:check` dry-runs both and 'fails on drift', run in CI), though no explicit fix-and-retry feedback loop is described.	4 / 5
Progressive Disclosure	Well-organized into clearly labeled sections (Single source of truth, propagation, lockstep integrations, Do, Don't) with no need for external references for a self-contained skill of this scope.	5 / 5
	Total	18 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description that clearly states what the skill covers and when to load it, with concrete tooling references and a distinct niche. It is slightly mechanism-oriented rather than action-list-oriented, which keeps specificity just below the top anchor.

Dimension	Reasoning	Score
Specificity	Names several concrete actions — 'Cargo.toml is the single source of truth', '`task version:sync` propagates it', integrations 'versioned and published in lockstep with core' — but focuses on mechanism rather than a comprehensive list of discrete actions, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both 'what' (how versions are synced and released from Cargo.toml) and 'when' ('Load before bumping a version, editing the version-sync task, or touching an integration's version/xberg dependency') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural trigger phrases users would say ('bumping a version', 'editing the version-sync task', 'touching an integration's version/xberg dependency') with good keyword coverage, though a few common synonyms are absent.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — xberg release/versioning with named tooling (Cargo.toml, alef, task version:sync) — making it highly distinct with minimal conflict risk against other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: xberg-io/xberg
Path: .ai-rulez/skills/release-versioning/SKILL.md
Commit: 0a60357

Reviewed: about 12 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.