CtrlK
BlogDocsLog inGet started
Tessl Logo

qsv-performance

Performance guide covering index files, stats cache, and frequency cache accelerators for qsv

56

Quality

62%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/skills/qsv-performance/SKILL.md
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 a well-structured, mostly lean performance reference with concrete commands and a clear size-based decision tree plus timeout recovery guidance; its main gap is the absence of explicit validation checkpoints for risky batch operations, which keeps workflow clarity just short of the top anchor.

DimensionReasoningScore

Conciseness

The body is dense and tabular with almost no padding or restating of concepts Claude already knows; the only minor slack is explanatory phrasing in the Parquet paragraph ('a columnar format that speeds up...'), so it sits just above the efficient anchor rather than fully lean.

4 / 5

Actionability

It gives concrete commands and flags (e.g., 'qsv stats --cardinality --stats-jsonl', 'mcp__qsv__qsv_to_parquet', 'slice --len N') with clear usage rules, but most guidance is prescriptive invocation rather than copy-paste runnable snippets, leaving a small gap to fully executable examples.

4 / 5

Workflow Clarity

The decision tree sequences actions by file size with explicit 'Always/Must/Avoid' checkpoints, and timeout handling offers a recovery loop (try Polars alternative or split), but there is no explicit validation/verification checkpoint for batch or destructive operations like sort or split-then-cat.

4 / 5

Progressive Disclosure

No bundle files (references/scripts/assets) exist, the skill is under 50 lines is not the case (it is longer), but content is organized into well-labeled sections with a single decision tree; given the judging note that under-50-line no-external-reference skills can score 5 when well-organized, the clearly sectioned overview here is easy to navigate with no nested references.

5 / 5

Total

17

/

20

Passed

Description

46%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 identifies a clear, distinct niche and names concrete accelerators, but it omits any 'when to use' trigger guidance and leans on technical jargon rather than natural user phrasing, capping both completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause stating the user situations that trigger this skill (e.g., large CSV files, slow qsv commands, repeated SQL queries).

Include natural trigger terms users would say, such as 'large CSV files', 'slow qsv', 'stats', 'frequency', and file extensions, rather than only internal cache names.

Add one or two concrete actions it enables (e.g., 'speed up qsv counts, stats, and frequency on large CSVs') to lift specificity.

DimensionReasoningScore

Specificity

The description names the domain (qsv performance) and lists concrete cache/accelerator artifacts ('index files, stats cache, and frequency cache accelerators') but stops short of enumerating the concrete actions it enables (counting, slicing, schema generation, frequency analysis), matching the 'names domain and 1-2 concrete actions' anchor.

3 / 5

Completeness

It clearly states 'what' (a performance guide covering named accelerators) but has no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

It relies on technical jargon ('index files', 'stats cache', 'frequency cache accelerators', 'qsv') with no natural phrasing a user would say when needing the skill; it lacks common variations a user might actually voice.

2 / 5

Distinctiveness Conflict Risk

The qsv-specific niche and named caches make it clearly distinct with minimal overlap risk against other skills, though the wording is narrow enough that it would not surface for general performance questions.

4 / 5

Total

12

/

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
dathere/qsv
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.