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.

61

Quality

73%

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

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 a lean, well-structured composition guide with executable examples and strong Wrong/Correct mistake pairs, held back only by a minor undefined-symbol gap in the Setup example and the lack of a fully explicit verification sequence.

Suggestions

Define or stub `columns` in the Setup example (even a one-line placeholder) so the snippet is copy-paste compilable.

Add a short explicit verification step, e.g. confirm `rowCount`/`pageCount` is set and the query key includes every server-owned signal, after wiring the table.

Consider moving the three Common Mistakes into a dedicated reference file once the skill grows, keeping SKILL.md as a concise overview.

DimensionReasoningScore

Conciseness

The body is lean and efficient — a compact Setup example plus terse directives like 'Manual flags only bypass client row processing; Query performs network work' — assuming Claude's competence with no padding or introductory explanations of Angular/signals.

5 / 5

Actionability

It provides a mostly executable Setup block and concrete Wrong/Correct code pairs for each common mistake, but the Setup references an undefined `columns` symbol, a minor gap preventing full copy-paste execution.

4 / 5

Workflow Clarity

The Setup → Core Patterns → Common Mistakes → API Discovery structure gives a clear progression, and the Wrong/Correct pairs act as implicit checkpoints; this is not a destructive or batch operation, so the missing explicit feedback loop does not cap the score.

4 / 5

Progressive Disclosure

The single SKILL.md is well-organized into clearly headed sections with no nested or buried references and no bundle files to navigate, though inline 'Source:' citations are informational rather than navigable reference links.

4 / 5

Total

17

/

20

Passed

Description

63%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 names a clear, distinctive niche, but it is jargon-heavy and lacks any explicit 'Use when...' trigger guidance, which caps its completeness and weakens its trigger-term quality.

Suggestions

Add a 'Use when ...' clause naming concrete trigger phrases, e.g. 'Use when wiring Angular Query into a TanStack Angular Table with server-side pagination, sorting, or filtering.'

Soften the jargon and add user-natural synonyms such as 'TanStack Query' and '@tanstack/angular-query' alongside 'Angular Query'.

Lead with the core action before enumerating implementation concerns, so the trigger terms surface first.

DimensionReasoningScore

Specificity

The description lists multiple specific concrete actions and concerns — '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' — giving comprehensive coverage of the composition's moving parts.

5 / 5

Completeness

It gives a clear 'what' (composing Angular Query with server-owned table state) but provides no 'Use when...' clause or equivalent trigger guidance, so per the rubric completeness is capped at 3.

3 / 5

Trigger Term Quality

It includes some relevant natural keywords ('Angular Query', 'Table filtering, sorting, and pagination') but leans heavily on jargon ('signal-owned', 'manual row-model boundaries', 'valid injection context') and omits common synonyms a user might actually say, such as 'TanStack Query' or '@tanstack/angular-query'.

3 / 5

Distinctiveness Conflict Risk

The Angular-Query-plus-manual-table-stages niche is mostly distinct with minimal conflict risk, though there is minor overlap with closely related prerequisite skills like getting-started and table-state.

4 / 5

Total

15

/

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.