Name: devtools
Rating: 68.8 (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

84%

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

Quality

Content

90%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 content is lean, executable, and well-structured with strong guardrails via Common Mistakes and a concrete API-discovery pointer. It falls just short of full marks on workflow clarity and progressive disclosure because it uses conceptual sections rather than an explicit numbered/checkpointed workflow and keeps everything inline.

Dimension	Reasoning	Score
Conciseness	The body is lean: a complete executable setup block, terse Wrong/Correct pairs, and behavior notes ("Core registration logs an error and skips keyless targets") that each earn their place without explaining Angular basics Claude already knows.	5 / 5
Actionability	The Setup block is copy-paste-ready executable TypeScript covering the common registration case, and Common Mistakes give concrete Wrong/Correct fixes plus a concrete API Discovery path (node_modules .d.ts inspection).	5 / 5
Workflow Clarity	The registration sequence is unambiguous via the complete example and Common Mistakes guardrails, but the body uses conceptual sections rather than an explicit numbered sequence with checkpoints.	4 / 5
Progressive Disclosure	Sections are well-organized and source/doc references ("Source: ...", "as documented in docs/devtools.md", API Discovery pointing to .d.ts) are one-level-deep and signaled, but all content lives inline in a single file with no split reference files.	4 / 5
	Total	18 / 20 Passed

Description

78%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, third-person, and distinct, with an explicit "Load for..." trigger clause that satisfies the when-requirement. It sits just below top marks because the trigger conditions are technical/scenario-based rather than natural user-utterance phrases.

Suggestions

Reframe the "Load for..." clause around user utterances (e.g., "Use when registering Angular Table v9 devtools, wiring reactive table registration, or gating production exports") to lift completeness and trigger_term_quality toward 5.

Add natural synonyms/end-users phrasing ("TanStack Table devtools", "Angular devtools panel") alongside the API names.

Dimension	Reasoning	Score
Specificity	Names the concrete primary action ("Register Angular Table v9 instances with injectTanStackTableDevtools inside injection context") plus several specific scenarios (options.key, enabled/undefined tables, isDevMode gating, production exports), with minor coverage gaps versus the multi-action 5 anchor.	4 / 5
Completeness	It states a clear "what" (register devtools inside injection context) and an explicit equivalent "when" clause ("Load for reactive table registration, required options.key, ... or explicit production exports"), but the when is condition-based rather than concrete user-utterance triggers.	4 / 5
Trigger Term Quality	Terms a target developer would naturally say ("injectTanStackTableDevtools", "Angular Table v9", "isDevMode", "injection context") give good keyword coverage, though a few natural synonyms are missing versus the comprehensive 5 anchor.	4 / 5
Distinctiveness Conflict Risk	The niche is highly specific (Angular Table v9 + injectTanStackTableDevtools registration), with distinct triggers and minimal realistic overlap with other skills.	5 / 5
	Total	17 / 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: 36733a3

Reviewed: 5 days 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.