alef-generated-bindings

Alef-managed generated bindings in packages/* and binding crates — the regeneration workflow (task alef:generate / alef:format), Go DocumentExtractor→Extractor rename mapping, the git-diff freshness check, and the key alef.toml sections. Load before editing anything under packages/* or a binding crate, or when regenerating, formatting, or verifying Alef output.

Quality

93%

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

93%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, highly actionable skill body with concrete commands, a sequenced workflow including verification, and well-organized sections appropriate for a sub-50-line single-purpose skill. The only gap is the absence of an explicit failure-recovery loop in the workflow.

Suggestions

Add an explicit feedback loop after the verify step, e.g. 'If e2e tests fail, fix the Rust source/alef.toml and re-run from step 3 before committing.'

Spell out what to do when the freshness check exits non-zero (regenerate and re-diff) so the recovery path is unambiguous.

Clarify in the freshness-check line that a non-zero exit means stale bindings, making the validation outcome interpretable.

Dimension	Reasoning	Score
Conciseness	Lean and efficient — no padding or explanation of what Alef is; every line (the DO-NOT-edit warning, the numbered workflow, the freshness command, the toml section list) earns its place and assumes Claude's competence.	5 / 5
Actionability	Fully executable, copy-paste-ready commands throughout — 'task alef:generate', 'alef all --clean --format=false', 'task alef:format', 'task e2e:test', and 'git diff --exit-code packages/ crates/xberg-node/...' — covering the common cases concretely.	5 / 5
Workflow Clarity	A clear 6-step sequence with an explicit verify step (step 5: 'Run task e2e:test or task e2e:all to verify') plus a freshness check, so validation is present and the destructive/batch cap does not apply; however, no explicit error-recovery feedback loop ('if tests fail, fix and re-run') is stated, keeping it just below the top anchor.	4 / 5
Progressive Disclosure	A single-purpose skill well under 50 lines with no need for external references; content is organized into clearly labeled sections (Workflow, Rename Mappings, Freshness Check, Key alef.toml Sections), satisfying the simple-skill exception for a top score.	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 states what the skill covers and when to load it, with concrete trigger phrases tied to a distinct internal-tool niche. Trigger-term variety is the only minor weakness, constrained by the domain.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'the regeneration workflow (task alef:generate / alef:format), Go DocumentExtractor→Extractor rename mapping, the git-diff freshness check, and the key alef.toml sections' — giving comprehensive, specific coverage rather than vague abstraction.	5 / 5
Completeness	Explicitly answers both 'what' (Alef-managed generated bindings and the regeneration/rename/freshness/toml concerns) and 'when' via the concrete 'Load before editing anything under packages/* or a binding crate, or when regenerating, formatting, or verifying Alef output' trigger clause.	5 / 5
Trigger Term Quality	Natural triggers are present ('editing anything under packages/* or a binding crate, or when regenerating, formatting, or verifying Alef output'), offering good keyword coverage, though synonym/extension variants are limited by the niche domain.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Alef-managed generated bindings) with distinct, tool-specific triggers that are unlikely to fire for unrelated skills, minimizing conflict risk.	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/alef-generated-bindings/SKILL.md
Commit: 0a60357

Reviewed: about 13 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.