CtrlK
BlogDocsLog inGet started
Tessl Logo

with-tanstack-query

Compose Angular Query with signal-owned Table filtering, sorting, and pagination state using reactive query options, manual row-model boundaries, direct query data, server counts, and valid injection context.

57

Quality

66%

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/angular-table/skills/with-tanstack-query/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 lean, actionable, and well-structured, with concrete executable code and wrong/correct mistake patterns that target real failure modes. It is a strong single-purpose composition skill with only minor gaps in example completeness and overview framing.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence ("Signal reads inside the options function establish refetch dependencies"), with no padding about what Angular or Query is; only minor repetition in the wrong/correct snippets keeps it from anchor 5.

4 / 5

Actionability

The Setup block is near copy-paste ready and Common Mistakes pair wrong/correct executable snippets, but minor gaps (undefined `columns` in the Setup class, `queryFn` referenced without definition in a mistake snippet) keep it just below the fully-executable anchor 5.

4 / 5

Workflow Clarity

Core Patterns sequence the composition concerns (track server-owned inputs, then keep Query data authoritative) and the Setup example makes the single action unambiguous; this is a single-purpose composition task with no destructive/batch step requiring validation checkpoints, so the missing-cap concern does not apply.

4 / 5

Progressive Disclosure

Sections (Setup, Core Patterns, Common Mistakes, API Discovery) are well-organized with clearly signaled one-level Source pointers, and no bundle files exist to split out; only the absence of a brief overview/TOC and the terse API Discovery section keep it from anchor 5.

4 / 5

Total

16

/

20

Passed

Description

58%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 occupies a clear niche, but it omits any explicit "Use when..." trigger guidance and leans heavily on technical jargon over natural user phrasing. Completeness is consequently capped.

Suggestions

Append an explicit trigger clause, e.g. "Use when wiring TanStack Query to an Angular Table with server-side pagination, sorting, or filtering."

Add natural synonyms users actually say ("TanStack", "server-side table", "angular-query") alongside the jargon.

Consider framing the facets as discrete actions (e.g. "Track server-owned state in the query key, read query data directly into the table, supply server rowCount") rather than one long compose sentence.

DimensionReasoningScore

Specificity

Lists several concrete concerns ("signal-owned Table filtering, sorting, and pagination state", "reactive query options", "manual row-model boundaries", "direct query data, server counts", "valid injection context"), but they read as facets of one compose action rather than discrete listed actions, leaving minor coverage gaps versus the comprehensive anchor 5.

4 / 5

Completeness

The description gives a clear "what" (compose Angular Query with table state via query options) but provides no "Use when..." clause or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant keywords exist ("Angular Query", "Table filtering, sorting, and pagination") but the phrase leans on jargon ("signal-owned", "manual row-model boundaries", "valid injection context") and omits natural user variations like "TanStack", "server-side table", or "angular-query".

3 / 5

Distinctiveness Conflict Risk

The Angular + TanStack Query + server-side Table composition is a clear niche with minimal conflict risk, though it overlaps slightly with sibling skills it declares as required (getting-started, table-state, client-vs-server).

4 / 5

Total

14

/

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.