CtrlK
BlogDocsLog inGet started
Tessl Logo

extracting-keywords

Use when extracting keywords (YAKE/RAKE) from documents — and, secondarily, when detecting document language or generating embeddings for RAG and search. Covers the keyword config (and its feature gating), `--detect-language`, and the standalone `embed` command with real flags.

68

Quality

83%

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

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

The body is highly actionable with copy-paste commands and code, and is reasonably concise and clearly sequenced. Its main weakness is progressive disclosure: several referenced reference files are absent from the bundle, so signaled pointers lead nowhere locally.

Suggestions

Add the referenced `references/` files (python-api.md, configuration.md, advanced-features.md, cli-reference.md) to the bundle, or remove the dangling pointers and inline the essential details.

Tighten the 'Field notes' section by removing fields already documented in the TOML config comments to reduce redundancy.

If references must live in a sibling skill, state that explicitly at each pointer (e.g. 'in the sibling xberg skill') so navigation expectations are clear — currently only some pointers note this.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands and no over-explanation of basic concepts, but the 'Field notes' section re-explains fields already commented inline in the TOML block, a minor trimmable redundancy.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands (extract, embed, cache warm), a complete TOML config block, a provider flag table, and a working Python example covering the common cases.

5 / 5

Workflow Clarity

Sequences are clear (e.g. `xberg extract | xberg embed` for document embeddings) and the 'Common pitfalls' section gives recovery guidance such as pre-warming cold models, though there are no explicit validation checkpoints since the operations are non-destructive.

4 / 5

Progressive Disclosure

Sections are well-organized and references are explicitly signaled, but the referenced `references/*.md` files do not exist in the bundle (some are deferred to a sibling `xberg` skill), leaving navigation gaps for the reader.

3 / 5

Total

16

/

20

Passed

Description

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

The description is specific, complete, and trigger-rich, clearly stating both capabilities and when to invoke the skill. It is mostly distinct from sibling skills, with only minor overlap risk against general extraction/RAG tooling.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — extracting keywords (YAKE/RAKE), detecting document language, generating embeddings, plus the keyword config, `--detect-language`, and the `embed` command — giving comprehensive coverage of the skill's surface.

5 / 5

Completeness

Explicitly states both what it does and when to use it — 'Use when extracting keywords... and, secondarily, when detecting document language or generating embeddings for RAG and search' — with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms users would say (extracting keywords, document language, embeddings for RAG and search) with synonyms (YAKE/RAKE), but a few common variations are absent, keeping it just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (the xberg keyword/language/embedding surface with tool-specific flags), with only minor overlap risk against generic extraction or RAG-embedding skills.

4 / 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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 4 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.