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.
60
72%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.kiro/skills/testing/SKILL.mdQuality
Discovery
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 is strong in specificity and distinctiveness, clearly naming the project (Graph Explorer) and listing concrete testing utilities and patterns. 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 somewhat technical and could benefit from including more natural user-facing language.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when writing, updating, or debugging tests for the Graph Explorer project, or when asking about test patterns, mocking, or test utilities.'
Include more natural trigger terms users might say, such as 'unit test', 'integration test', 'mock data', 'test setup', or 'writing tests'.
| 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' that users working on Graph Explorer testing would use. However, it misses common variations like 'unit test', 'integration test', 'mock', 'test setup', or simpler terms a user might 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 |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, highly actionable testing standards skill with excellent concrete examples covering the full range of Graph Explorer testing patterns. Its main weakness is verbosity — several sections explain concepts Claude already understands (benefits of strict equality, why not to test styling, basic test independence principles), and the file could benefit from splitting advanced patterns into referenced sub-files. Overall it serves as an effective and practical testing guide.
Suggestions
Remove explanatory rationale sections that Claude already knows (e.g., the 'Benefits' bullet list under toStrictEqual, the 'Do Not Test Styling' rationale, and generic best practices like 'Test behavior, not implementation details').
Consider splitting the backward compatibility section and SPARQL/RDF testing patterns into separate referenced files to improve progressive disclosure and reduce the main file's length.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is generally well-structured but includes some unnecessary verbosity, such as the 'Benefits' list for toStrictEqual (Claude knows why strict equality is better), explanations of what setupTests.ts does in detail, and the 'Do Not Test Styling or Layout' section which explains obvious rationale. Some sections like 'Test Independence' and 'Meaningful Assertions' state things Claude already knows. | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples throughout — from DbState setup, renderHookWithState usage, SPARQL test helpers, component testing with TestProvider, to CLI commands for test execution. Every pattern is demonstrated with concrete, runnable TypeScript code. | 3 / 3 |
Workflow Clarity | The test execution strategy section provides a clear decision tree for when to run targeted vs full tests. The backward compatibility section has explicit steps for when to add tests and a clear template. The component testing example shows a complete sequence (create state → apply to store → create query client → render → assert). For a testing standards skill, the workflows are well-sequenced with clear guidance. | 3 / 3 |
Progressive Disclosure | The content is a single large file (~300 lines) that could benefit from splitting — the backward compatibility section, SPARQL testing patterns, and component testing patterns could each be separate referenced files. There is one cross-reference to `.kiro/skills/typescript/SKILL.md` for type annotations, but the bulk of content is inline. The section headers provide good navigation but the file is monolithic. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%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
30587b0
- 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.