release-readiness

Audit Xberg before a push or release by reconciling CI, Publish Release dry-run, Benchmarks, generated freshness, changelog, and remote branch state. Load for release-readiness work, not routine local commits.

Quality

92%

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

92%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 tight, well-structured release-gate skill that pairs a sequenced audit checklist with explicit validation checkpoints and precise per-artifact verification contracts. It is token-efficient and actionable, with only minor delegation of command-level detail to repo conventions.

Dimension	Reasoning	Score
Conciseness	Lean directive prose with no padding or explanation of concepts Claude already knows; each sentence encodes project-specific contracts that earn their tokens.	5 / 5
Actionability	Highly concrete directives and precise verification criteria (e.g., reset per-library status, GHCR image existence), but some execution detail is delegated to 'gh-workflows conventions' and sibling skills rather than spelled out.	4 / 5
Workflow Clarity	A numbered five-step audit checklist plus a sequenced push/dispatch section with explicit validation checkpoints and feedback loops ('Retry only after identifying and addressing the cause', 'Close addressed issues only after the fixing commit is reachable remotely').	5 / 5
Progressive Disclosure	Under 50 lines, single-purpose, and well-organized into Audit, Publish dry-run contracts, and Push and dispatch sections with no need for external bundle references; cross-skill pointers are clearly signaled.	5 / 5
	Total	19 / 20 Passed

Description

92%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, specific description that clearly delimits a release-readiness gate with concrete signals and an explicit use/not-use trigger. It is concise without sacrificing coverage. The only minor weakness is keyword synonym breadth.

Dimension	Reasoning	Score
Specificity	Enumerates concrete audit actions — reconciling CI, Publish Release dry-run, Benchmarks, generated freshness, changelog, and remote branch state — giving comprehensive coverage rather than generic verbs.	5 / 5
Completeness	Explicitly states both what (audit Xberg by reconciling the six signals) and when ('Load for release-readiness work, not routine local commits') with a concrete trigger phrase.	5 / 5
Trigger Term Quality	Natural trigger terms ('push or release', 'release-readiness work', 'routine local commits') are present and would be said by a user, but coverage is somewhat jargon-bound and lacks broader synonyms.	4 / 5
Distinctiveness Conflict Risk	Scoped to Xberg release gating with a distinct niche and an explicit negative trigger ('not routine local commits'), minimizing overlap with general commit or versioning skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: xberg-io/xberg
Path: .ai-rulez/skills/release-readiness/SKILL.md
Commit: 04336bd

Reviewed: 5 days 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.