testing

Testing standards, patterns, and utilities for Graph Explorer including Vitest, DbState, renderHookWithState, test data factories, SPARQL test helpers, and backward compatibility testing for persisted data.

Quality

66%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./.kiro/skills/testing/SKILL.md

Quality

Content

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid, highly actionable testing guide with excellent concrete examples covering the full range of Graph Explorer testing patterns. Its main weaknesses are moderate verbosity (some repeated patterns and general testing advice Claude already knows) and a monolithic structure that could benefit from splitting into focused sub-documents. The backward compatibility section is a standout — well-motivated and precisely structured.

Suggestions

Remove general testing advice Claude already knows (e.g., 'Each test should be independent', 'Test behavior, not implementation details', 'Use descriptive test names') to improve conciseness.

Split detailed sections like SPARQL test helpers, backward compatibility testing, and component testing into separate referenced files to improve progressive disclosure.

Add an explicit validation workflow or checklist (e.g., 'Before submitting: 1. Run targeted tests → 2. Fix failures → 3. Run pnpm checks → 4. Run full suite if needed') to improve workflow clarity.

Dimension	Reasoning	Score
Conciseness	The skill is fairly comprehensive but includes some redundancy (e.g., the same imports and patterns are repeated across multiple sections, and some guidance like 'test behavior, not implementation details' is general knowledge Claude already possesses). The backward compatibility section is well-justified but the overall document could be tightened by ~20-30%.	2 / 3
Actionability	The skill provides fully executable, copy-paste-ready code examples throughout — from hook testing with renderHookWithState and DbState, to SPARQL test helpers, component rendering patterns, CLI commands for test execution, and backward compatibility test templates. Every section includes concrete, specific guidance.	3 / 3
Workflow Clarity	The test execution strategy section provides a clear sequence (targeted tests → full suite → pnpm checks), and the backward compatibility section has clear 'when to add these tests' criteria. However, there's no explicit validation/verification workflow for the overall testing process — e.g., no feedback loop for when tests fail, no checklist for ensuring test coverage before PR submission. The document reads more as a reference than a guided workflow.	2 / 3
Progressive Disclosure	The document is well-organized with clear section headers and a quick reference at the top, but at ~300+ lines it's a monolithic file that could benefit from splitting detailed patterns (SPARQL helpers, backward compatibility, component testing) into separate referenced files. The single cross-reference to '.kiro/skills/typescript/SKILL.md' for type annotations is good but more decomposition would improve navigability.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 excels at specificity and distinctiveness by naming concrete tools, utilities, and the target project. Its main weakness is the lack of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The trigger terms are domain-appropriate but could benefit from more natural user-facing language.

Suggestions

Add a 'Use when...' clause such as 'Use when writing, updating, or debugging tests for the Graph Explorer project, or when the user asks about test patterns, test utilities, or test setup in Graph Explorer.'

Include more natural trigger terms users might say, such as 'unit test', 'integration test', 'mock', 'test setup', 'writing tests', or 'test coverage'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions and tools: Vitest, DbState, renderHookWithState, test data factories, SPARQL test helpers, and backward compatibility testing for persisted data. These are concrete, named utilities and patterns.	3 / 3
Completeness	Clearly answers 'what does this do' by listing testing standards, patterns, and utilities. However, there is no explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill, which caps this at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Includes relevant technical terms like 'Vitest', 'SPARQL', 'test data factories', 'backward compatibility testing', and 'Graph Explorer' that users working in this domain would use. However, it misses common variations like 'unit test', 'integration test', 'mock', 'test setup', or 'writing tests' that users would naturally say.	2 / 3
Distinctiveness Conflict Risk	Highly distinctive due to the specific project name 'Graph Explorer' and named utilities like 'DbState', 'renderHookWithState', and 'SPARQL test helpers'. Unlikely to conflict with generic testing skills or other project-specific skills.	3 / 3
	Total	10 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (571 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	9 / 11 Passed

Repository: aws/graph-explorer
Commit: 5f2262e

Reviewed: 4 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.