CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

64

Quality

78%

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 ./packages/match-sorter-utils/skills/fuzzy-ranking/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 concise, actionable, and well-structured with executable examples and high-value common-mistake guidance. The main gap is the Table filterMeta integration, which is described in prose rather than fully runnable code.

Suggestions

Convert the Table filterMeta integration into a concrete, executable code block (filterFn + metaHelper + sortFn) rather than prose with inline fragments.

Add a brief example of the comparator fallback for absent metadata so the sortFn behavior is copy-paste ready.

DimensionReasoningScore

Conciseness

Lean and efficient: jumps straight to executable code and non-obvious gotchas without explaining fuzzy matching or TanStack basics, and every section earns its tokens.

5 / 5

Actionability

Setup and accessor examples are copy-paste ready, but the Table filterMeta integration is prose with inline code fragments rather than a fully executable block, leaving a minor gap.

4 / 5

Workflow Clarity

The core 'rank once, filter on passed, retain RankingInfo, then compareItems' sequence is clearly ordered; no validation checkpoints are needed since this is not a destructive or batch operation, so the cap does not apply.

4 / 5

Progressive Disclosure

Well-organized into Setup, Core Patterns, Common Mistakes, and API Discovery with one-level-deep external pointers (global-filtering/sorting skills, the installed .d.ts file); no nested references, though it slightly exceeds the under-50-line simple-skill case.

4 / 5

Total

17

/

20

Passed

Description

75%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 and distinctive with strong concrete action coverage, but lacks an explicit 'Use when...' trigger clause, leaving the activation guidance only weakly implied. Adding natural trigger phrasing would raise completeness.

Suggestions

Add an explicit 'Use when...' clause naming natural user phrases (e.g., 'Use when adding fuzzy matching, fuzzy filtering, or fuzzy search to a TanStack Table').

Soften reliance on API-specific identifiers (rankItem, RankingInfo.passed) in favor of plain-language triggers users would actually say.

DimensionReasoningScore

Specificity

Names many concrete actions (rankItem, filter via RankingInfo.passed, compareItems, configure rankings/thresholds/accessors/min-max bounds/diacritics) with comprehensive coverage.

5 / 5

Completeness

Has a clear 'what' but the 'when' is only weakly implied via the load instruction 'Load for @tanstack/match-sorter-utils itself or fuzzy Table filterMeta wiring' with no explicit 'Use when...' trigger clause, capping completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms like 'fuzzy matches' and 'fuzzy Table filterMeta wiring' plus the library name, but leans on API-specific jargon (rankItem, RankingInfo.passed) and misses some common phrasings.

4 / 5

Distinctiveness Conflict Risk

Targets a narrow, well-defined niche (@tanstack/match-sorter-utils fuzzy ranking) with distinct triggers and minimal overlap risk.

5 / 5

Total

17

/

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.

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