CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

fuzzy-ranking

Rank fuzzy matches with rankItem, filter with RankingInfo.passed, compare saved ranking metadata with compareItems, and configure rankings, thresholds, accessors, min/max bounds, or diacritics. Load for @tanstack/match-sorter-utils itself or fuzzy Table filterMeta wiring.

Quality

90%

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

86%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 lean, well-structured reference for the library with executable code for its main patterns and high-value common-mistakes guidance. The main gap is the prose-only Table filterMeta integration pattern, which would benefit from a short code snippet.

Suggestions

Add a short executable snippet for the Table filterMeta integration (a filterFn calling addMeta?.({ itemRank }) registered under filterFns with globalFilterFn: 'fuzzy'), since that pattern is currently prose-only.

Show the sortFn fallback comparator shape in code rather than describing it in prose, so the sorting workflow's tie-breaking step is directly executable.

Add a brief verification cue for the ranking pipeline (e.g., confirm entry.info.passed is used, not .rank) to checkpoint the highest-frequency mistake.

DimensionReasoningScore

Conciseness

Lean throughout: no explanation of concepts Claude already knows, mistake rationales are single lines of non-obvious information ('The function already returns -1 when a.rank is greater than b.rank'), and every section earns its place.

5 / 5

Actionability

Two copy-paste-ready executable snippets cover the core pipeline and accessors, but the Table filter-meta pattern ('addMeta?.({ itemRank })', 'filterMeta: metaHelper<...>()', 'filterFns' registration) is described only in prose without a code example — a minor gap, not pseudocode.

4 / 5

Workflow Clarity

The core rank-once/filter-on-passed/sort-with-stored-info sequence is unambiguous and demonstrated end-to-end, and the mistake section guards the common failure modes; the Table integration path is sequenced only in prose and lacks checkpoints.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed; the body delegates cleanly to one-level-deep, well-signaled targets (node_modules type declarations, the @tanstack/table-core#table-features skill) and is organized into scannable Setup / Core Patterns / Common Mistakes / API Discovery sections.

5 / 5

Total

18

/

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 highly specific, distinctive description that names concrete API actions and provides an explicit load-for trigger clause. Trigger-term coverage is strong but could include more colloquial variations like 'fuzzy search' or 'fuzzy sorting'.

Suggestions

Add one or two natural user phrasings (e.g., 'fuzzy search' or 'fuzzy sorting') to the trigger clause to broaden keyword coverage beyond library jargon.

DimensionReasoningScore

Specificity

Lists multiple concrete API-level actions ('Rank fuzzy matches with rankItem, filter with RankingInfo.passed, compare saved ranking metadata with compareItems, and configure rankings, thresholds, accessors, min/max bounds, or diacritics') in third-person voice with comprehensive coverage of the library's surface.

5 / 5

Completeness

Clearly answers 'what' via named actions and 'when' via the explicit trigger clause 'Load for @tanstack/match-sorter-utils itself or fuzzy Table filterMeta wiring', which names concrete load conditions rather than leaving 'when' implied.

5 / 5

Trigger Term Quality

Good natural-term coverage ('fuzzy matches', 'rank', 'filter', 'thresholds', '@tanstack/match-sorter-utils'), but misses common user phrasings like 'fuzzy search' or 'fuzzy sorting', and leans slightly on jargon ('fuzzy Table filterMeta wiring').

4 / 5

Distinctiveness Conflict Risk

Names the exact library and a narrow integration scenario, giving it a clear niche with minimal overlap risk; the only adjacency (TanStack Table) is explicitly delegated to another skill.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

TanStack/table

Path

packages/match-sorter-utils/skills/fuzzy-ranking/SKILL.md

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.