alef-generated-bindings

Alef-managed generated bindings in packages/* and binding crates — the regeneration workflow (task alef:generate / alef:verify), the alef.toml section layout, the core-side edits that break a regen, and the FFI bridge's JSON marshalling requirement. Load before editing anything under packages/* or a binding crate, before adding a trait method or extractor, or when regenerating or verifying Alef output.

Quality

94%

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

96%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.

An information-dense, highly actionable body with a well-sequenced workflow and explicit validation/recovery guidance. The only structural weakness is that some reference-style lists are inlined rather than split into a bundled reference file.

Suggestions

Move the enumerated [crates.<lang>] language list and the generated-output crate path list into a references/ file (e.g. ALEF_TOML.md) and link to it from the 'Key alef.toml sections' section to tighten the SKILL.md overview.

Consider promoting the 'Core-side edits that break a regen' bullets into an explicit checklist format so the regen-failure feedback loop is scannable at a glance.

Dimension	Reasoning	Score
Conciseness	Dense and project-specific throughout — concrete task names, file paths, attribute names, error codes (E0639), and counts (218 call sites, 36 of 42 modules) — with no padding or explanation of concepts Claude already knows; every token earns its place.	5 / 5
Actionability	Provides fully executable, copy-paste-ready guidance: exact commands ('task alef:generate', 'cargo check -p xberg-ffi', 'cargo install --path . --force'), specific attributes ('#[cfg_attr(alef, alef(skip))]', '#[non_exhaustive]'), and concrete trait requirements (Default + Serialize + Deserialize) covering the common cases.	5 / 5
Workflow Clarity	The 6-step workflow is clearly sequenced with explicit validation checkpoints ('task alef:verify', 'task e2e:test') and error-recovery feedback loops ('Check this first when a regen dies', 'Revert that churn rather than committing it'); validation is present for the batch regen operation so the destructive/batch cap does not apply.	5 / 5
Progressive Disclosure	Well-organized into clearly headed sections (Workflow, Freshness check, Key alef.toml sections, Core-side edits, FFI bridge, Which alef answered) with no nested references, but it slightly exceeds the ~50-line simple-skill threshold and inlines some reference-list material (15-language list, 9 crate paths) that could live in a separate file.	4 / 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 conditions tailored to an internal codebase. The only minor gap is natural-term breadth, which is inherently bounded by the niche domain.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete facets — 'the regeneration workflow (task alef:generate / alef:verify), the alef.toml section layout, the core-side edits that break a regen, and the FFI bridge's JSON marshalling requirement' — giving comprehensive, specific coverage rather than vague language.	5 / 5
Completeness	Explicitly answers both 'what' (Alef-managed generated bindings, workflow, toml layout, breaking edits, FFI requirement) and 'when' via a concrete 'Load before...' trigger clause, matching the anchor for clearly answering both with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural task-oriented phrases a user would say ('editing anything under packages/* or a binding crate', 'adding a trait method or extractor', 'regenerating or verifying Alef output') with some synonyms, but coverage of natural variations is good rather than exhaustive for this niche domain.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Alef-managed generated bindings under packages/* and binding crates) with highly specific triggers like 'alef:generate / alef:verify' and 'adding a trait method or extractor', giving minimal conflict risk with other 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/alef-generated-bindings/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.