CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

devtools

Register Angular Table v9 instances with injectTanStackTableDevtools inside injection context. Load for reactive table registration, required options.key, enabled or undefined tables, cleanup, Angular isDevMode gating, or explicit production exports.

Quality

77%

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-devtools/skills/devtools/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.

A tight, executable skill: complete setup code, concrete wrong/right patterns for the three main pitfalls, and pointers to authoritative API sources. The main gap is that application-level devtools host provisioning is mentioned but never shown, leaving the full workflow one step short of self-contained.

DimensionReasoningScore

Conciseness

The body is lean with no re-teaching of known concepts; mistake entries are compact Wrong/Correct pairs and setup defers host details to docs rather than restating them. The only trimmable padding is full Angular component boilerplate (decorator, template) in the Setup example.

4 / 5

Actionability

Setup provides a complete, copy-paste-ready code example and each mistake gives concrete Wrong/Correct guidance. The host-provision step ('as documented in docs/devtools.md') lacks inline code, but that is reasonably delegated to the declared @tanstack/table-devtools#devtools dependency.

4 / 5

Workflow Clarity

As a single-purpose skill the registration action is unambiguous, and the Common Mistakes section supplies error-recovery guidance (injection context, missing key, isDevMode no-op) that functions as checkpoints. Not a 5 because the two-step workflow leaves the app-level host provisioning underspecified with no code or command.

4 / 5

Progressive Disclosure

No bundle files exist; the ~63-line body is well-sectioned (Setup, Hooks and Components, Common Mistakes, API Discovery) with a clearly signaled one-level reference (docs/devtools.md) and a sound runtime API-discovery pointer to node_modules .d.ts files. Not a 5 because the body slightly exceeds the simple-skill length and the inline 'Source:' citations reference repo paths that are not loadable files in the skill bundle.

4 / 5

Total

16

/

20

Passed

Description

71%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 specific, distinctive description with an explicit trigger clause, but the trigger terms skew toward internal API jargon ('options.key', 'enabled or undefined tables') and omit the most natural user vocabulary ('devtools', 'TanStack'). Adding natural synonyms would materially improve discoverability.

Suggestions

Include the words 'devtools' and 'TanStack' in the description itself — they are the terms a user would most naturally say, yet neither appears in the description text.

Rewrite the 'Load for...' clause in natural user phrasing (e.g., 'Load when setting up TanStack Table devtools in an Angular app, debugging table state, or configuring production devtools exports') instead of compressed API fragments like 'enabled or undefined tables'.

Add common synonyms such as 'debug table state' or 'table inspector' to broaden natural keyword coverage without changing the skill's scope.

DimensionReasoningScore

Specificity

Names the exact API ('injectTanStackTableDevtools'), version ('Angular Table v9'), and concrete concerns (options.key, cleanup, isDevMode gating, production exports). Not a 5 because only one true action ('Register ... instances') is stated while the remaining items are trigger topics rather than additional concrete actions.

4 / 5

Completeness

Has a clear 'what' ('Register Angular Table v9 instances with injectTanStackTableDevtools inside injection context') and an explicit 'Load for...' when-clause listing concrete triggers, satisfying the Use-when requirement. Not a 5 because the trigger phrasing ('enabled or undefined tables') is compressed and reads as keyword stuffing rather than natural trigger guidance.

4 / 5

Trigger Term Quality

Includes some relevant keywords ('reactive table registration', 'cleanup', 'isDevMode', 'production exports') but omits the most natural user phrasings — 'devtools' and 'TanStack' never appear in the description text itself. A user asking about 'TanStack table devtools' or 'debugging my table' would not naturally match these terms.

3 / 5

Distinctiveness Conflict Risk

Highly specific niche — Angular Table v9 devtools registration via a named injection function — with trigger conditions (options.key, isDevMode gating, production exports) that no other skill would plausibly match. Minimal conflict risk.

5 / 5

Total

16

/

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/angular-table-devtools/skills/devtools/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.