Content
86%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
An exemplary API-overview skill: fully executable multi-language examples, a high-value pitfalls section, and clean progressive disclosure to real, one-level-deep reference files. The only friction points are stale-prone pinned versions and the absence of an explicit batch error-recovery loop.
Suggestions
Drop hard-pinned CLI versions (use @xberg-io/xberg-cli and xberg-cli unpinned, or move version pins to a changelog/reference) so the quick-install commands do not go stale.
Add a short retry/skip pattern for batch failures (e.g. collect result.errors indices, re-extract failed inputs with adjusted config) to close the feedback loop in the Batch Processing section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Nearly all content is executable code, tables, and pitfalls with zero explanation of concepts Claude already knows, but pinned version numbers ("npx @xberg-io/xberg-cli@1.3.10", "uvx --from xberg-cli==1.3.8", Cargo "version = \"1.1.0\"") are time-sensitive and the 100+ row extension table duplicates the supported-formats reference, keeping it below the lean 5 anchor. | 4 / 5 |
Actionability | Copy-paste-ready, complete examples in Python, Node, Rust, and CLI spanning install, extraction, configuration (including TOML config files and --config-json), batch, and typed error handling, plus pitfalls with exact field names and signatures ("extract(input, &config) — the config is a reference"); specific examples cover the common cases. | 5 / 5 |
Workflow Clarity | Sections are logically sequenced (Install → Quick Start → Configuration → Batch → OCR → Result fields → Error Handling → Pitfalls) and batch verification is explicitly shown (inspecting result.errors in Python and Node), but there is no validate→fix→retry feedback loop for failed batch inputs (recovery is deferred to a sibling skill), matching 4's "minor validation gaps" rather than 5's feedback loops. | 4 / 5 |
Progressive Disclosure | The overview keeps key examples inline while eight well-labeled, one-level-deep references (e.g. "All functions, config classes, plugin protocols, exact signatures") hold the bulk detail; every referenced file exists in the bundle and no reference file chains onward to another, so navigation is easy and content is appropriately split. | 5 / 5 |
Total | 18 / 20 Passed |