CtrlK
BlogDocsLog inGet started
Tessl Logo

crate-structure

The Xberg workspace layout — the version source of truth (root Cargo.toml [workspace.package] version), the crates/ workspace members (core lib, CLI, FFI, per-language binding crates, OCR crates), the out-of-workspace binding packages under packages/ (PyPI, RubyGems, Composer, Go, Maven, NuGet, Hex), and the tools/ directory. Load when navigating the repo, deciding where code belongs, or wiring a new crate or binding package.

75

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 reference that lists every workspace member and package with its role and key tooling, assuming Claude's competence throughout. As a structural map it is appropriately concise and well-organized, though it is descriptive rather than executable by nature.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — each bullet maps a crate or package to its role in one line, with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

It provides concrete pointers (paths like packages/elixir/native/xberg_rustler, feature sets like wasm-target, tooling like maturin + PyO3) but stops at description rather than executable commands, leaving minor gaps for copy-paste use.

4 / 5

Workflow Clarity

This is a simple, single-purpose reference skill whose one job — mapping the workspace layout — is unambiguous and well-organized, so the simple-skill exception applies; there are no destructive or batch operations that would warrant validation checkpoints.

5 / 5

Progressive Disclosure

Content is organized into clearly labeled sections (Workspace crates, Out-of-workspace bindings, Tools) with no bundle files present and well under 50 lines, satisfying the simple-skill exception for a self-contained overview.

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, concrete description that names the workspace's actual components and registries and pairs them with an explicit load-trigger clause. The only mild gap is trigger-term naturalness, which leans on architectural terms over everyday user phrasing.

DimensionReasoningScore

Specificity

The description enumerates concrete, specific elements — 'core lib, CLI, FFI, per-language binding crates, OCR crates' plus named package registries (PyPI, RubyGems, Composer, Go, Maven, NuGet, Hex) and a tools/ directory — giving comprehensive coverage rather than vague language.

5 / 5

Completeness

It explicitly answers both 'what' (the workspace layout and its members) and 'when' ('Load when navigating the repo, deciding where code belongs, or wiring a new crate or binding package') with concrete trigger phrases.

5 / 5

Trigger Term Quality

'Load when navigating the repo, deciding where code belongs, or wiring a new crate or binding package' are natural phrasings a user might say, but the surrounding vocabulary is architectural jargon and lacks common synonyms/variations a user would voice.

4 / 5

Distinctiveness Conflict Risk

It carves a clear niche — the Xberg crate/binding-package structure — with triggers tied to repo navigation and crate wiring, making overlap with unrelated skills minimal.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
xberg-io/xberg
Reviewed

Table of Contents

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.