crate-structure

The Xberg workspace layout — the version source of truth (root Cargo.toml [workspace.package] version), the 19 workspace members and 3 excluded crates, the distribution packages under packages/, the tools/ directory, and the ignore-file allowlists a new workspace member must be added to. Load when navigating the repo, deciding where code belongs, or wiring a new crate or binding package.

Quality

96%

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

100%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 excellent reference-plus-workflow skill body: concise, actionable, with a validated multi-step procedure and clean organization. It assumes competence and rewards it with concrete, copy-ready guidance.

Dimension	Reasoning	Score
Conciseness	A dense, fact-forward inventory that assumes Claude's competence; the only prose details are non-obvious gotchas (extern-crate aliasing, FFI routing) that each earn their tokens.	5 / 5
Actionability	Gives exact paths, feature flags, alias syntax, allowlist patterns (`!crates/<name>/`), literal failure messages, and a concrete verify command — directly executable guidance for wiring crates.	5 / 5
Workflow Clarity	The 'Adding a workspace member' section is a clearly sequenced numbered list with an explicit validation checkpoint (`task verify:docker-crates`) and an honest note on what it does not check, satisfying the validation requirement for a batch/destructive-adjacent operation.	5 / 5
Progressive Disclosure	No bundle files exist and the body is self-contained with clear section headers and one well-signaled one-level cross-skill reference (`alef-generated-bindings`), so the simple/well-organized-skill exception applies.	5 / 5
	Total	20 / 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 precise, well-scoped description that states concrete facts and an explicit load condition. Trigger phrasing is task-oriented and slightly jargon-heavy rather than user-natural, the only minor gap.

Dimension	Reasoning	Score
Specificity	Names concrete entities — the version source of truth, 19 workspace members, 3 excluded crates, packages/, tools/, and ignore-file allowlists — giving comprehensive coverage of the workspace layout rather than vague domain language.	5 / 5
Completeness	Explicitly answers both 'what' (the workspace layout facts) and 'when' via the 'Load when ...' clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural task-oriented triggers ('navigating the repo', 'deciding where code belongs', 'wiring a new crate or binding package'), though it leans on jargon and misses some common synonyms like 'cargo workspace' or 'adding a crate'.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to the Xberg crate/workspace structure with distinct triggers, so it is unlikely to fire for an unrelated skill.	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/crate-structure/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.