CtrlK
BlogDocsLog inGet started
Tessl Logo

picking-a-format

Use when choosing an output format for extracted documents — plain text, markdown, djot, HTML, JSON, or DocTags. Maps consumer (LLM, parser, archive) to the right `--format` / `--content-format` pair.

66

Quality

80%

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

76%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 actionable, well-structured decision skill with copy-paste examples and a clear decision tree. Its main weaknesses are the missing validation step for the batch path and two referenced files that do not exist in the bundle.

Suggestions

Add an explicit validation/checkpoint step to the batch example (e.g., verify .results[] is non-empty or spot-check one document before bulk indexing) to lift workflow clarity above the batch-operation cap of 3.

Create references/cli-reference.md and references/configuration.md (or remove the dangling pointer lines) so the signaled navigation actually resolves.

Trim editorial justifications like 'the downstream code stays simple' and 'best compromise across LLMs, RAG, and human review' to tighten conciseness toward 5.

DimensionReasoningScore

Conciseness

The body is lean and does not explain concepts Claude already knows, but a few editorial justifications ('downstream code stays simple', 'best compromise across LLMs, RAG, and human review') are minor over-explanation that could be trimmed.

4 / 5

Actionability

A decision tree maps each consumer to an exact flag pair, and four copy-paste-ready bash examples (extract, batch|jq, token-reduction, metadata-only) cover the common cases with fully executable commands.

5 / 5

Workflow Clarity

The decision tree is a clear sequence, but the batch example is a batch operation with no validation/verification step, and the only validation cue ('maximum is lossy — verify before relying on it') is implicit, capping this at 3 per the batch-operation rule.

3 / 5

Progressive Disclosure

Sections are well-organized and the two end references are clearly signaled and one level deep, but neither referenced path (references/cli-reference.md, references/configuration.md) exists in the bundle, a minor navigation gap that keeps it below 5.

4 / 5

Total

16

/

20

Passed

Description

85%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 description with an explicit trigger phrase, concrete enumerated scope, and a narrow, low-conflict niche. The only gap is missing synonyms/file extensions in the trigger terms, which keeps trigger quality just below full marks.

DimensionReasoningScore

Specificity

Names the concrete task ('choosing an output format'), enumerates six formats and the two flags, and describes a mapping action; several specific elements with minor coverage gaps rather than comprehensive, fitting the anchor-4 example.

4 / 5

Completeness

Explicitly answers both what (choose an output format and map consumer to the right flag pair) and when (an explicit 'Use when choosing an output format for extracted documents' trigger), matching the anchor-5 example.

5 / 5

Trigger Term Quality

Leads with a natural 'Use when choosing an output format' trigger and lists format names (plain text, markdown, djot, HTML, JSON, DocTags) plus consumer terms (LLM, parser, archive), but misses common synonyms and file extensions.

4 / 5

Distinctiveness Conflict Risk

Targets a narrow, tool-specific niche (Xberg's --format / --content-format selection) with distinct triggers, giving it a clear niche and minimal conflict risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

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.