Name: devtools
Rating: 61.6 (1 reviews)
Author: TanStack

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

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

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

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 a compact, executable reference with strong guardrails via Wrong/Correct mistake pairs and complete setup code, though the Devtools host setup and API specifics are deferred to external files rather than included or bundled.

Suggestions

Inline or bundle the Angular Devtools host-provision step (currently deferred to docs/devtools.md) so the setup is self-contained.

Add a short validation/verification cue after registration (e.g., confirm the table appears in the Devtools panel in isDevMode) to strengthen the workflow.

Replace the generic API Discovery pointer with a couple of concrete option signatures pulled from the .d.ts files.

Dimension	Reasoning	Score
Conciseness	The body is lean — a complete minimal setup example, brief hooks note, and Wrong/Correct mistake pairs with sources — assuming Claude's competence and avoiding concept explanations; only minor tightening possible (e.g., the intro line and Source citations).	4 / 5
Actionability	Provides a complete, copy-paste-ready Setup code block and concrete Wrong/Correct guidance, but defers the Devtools host setup to an external doc and relies on inspecting .d.ts files for API discovery, leaving minor gaps.	4 / 5
Workflow Clarity	The single registration action is unambiguous via the Setup example and Common Mistakes guardrails, with a rough sequence (setup table -> register devtools -> provide host); not a 5 because the host-provision step and validation feedback are not explicitly sequenced.	4 / 5
Progressive Disclosure	Well-organized into clear sections (Setup, Hooks and Components, Common Mistakes, API Discovery) with no nested references, but the host setup is offloaded to an unbundled docs/devtools.md rather than inlined or placed in a bundled reference.	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.

The description is specific to a well-defined niche and answers both what and when, but its trigger guidance leans technical and feature-list-like rather than using natural user phrasing.

Suggestions

Rewrite the 'Load for ...' clause as an explicit 'Use when ...' trigger phrase using natural terms a developer would say (e.g., 'Use when registering an Angular TanStack table with devtools, debugging table state, or enabling the devtools panel').

Add common synonyms/extensions to improve trigger term coverage (e.g., 'TanStack table devtools', 'devtools panel', 'debug table').

Lead with the single concrete action ('Register Angular Table v9 table instances with devtools') and separate trigger conditions from capability claims for cleaner completeness.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions/conditions ('Register Angular Table v9 instances with injectTanStackTableDevtools inside injection context', 'reactive table registration', 'cleanup', 'Angular isDevMode gating', 'explicit production exports') but the core action is essentially one (register) framed with conditions, leaving minor coverage gaps versus the comprehensive anchor 5.	4 / 5
Completeness	Clearly states the 'what' ('Register Angular Table v9 instances with injectTanStackTableDevtools inside injection context') and provides trigger guidance via 'Load for reactive table registration, required options.key, ...', but the 'when' reads more as a feature list than explicit natural trigger phrases.	4 / 5
Trigger Term Quality	Includes relevant technical keywords an Angular/TanStack developer would say ('Angular Table v9', 'injectTanStackTableDevtools', 'isDevMode', 'options.key') but the language is jargon-heavy and missing common natural variations like 'devtools panel' or 'debug table'.	3 / 5
Distinctiveness Conflict Risk	Targets a precise niche (Angular + TanStack Table v9 devtools registration via injectTanStackTableDevtools) with distinct triggers and minimal conflict risk against other skills.	5 / 5
	Total	16 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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
Commit: 9e523bc

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.