typescript
TypeScript conventions and rules for Graph Explorer, including branded types, function style preferences, and type safety patterns.
70
58%
Does it follow best practices?
Impact
85%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.kiro/skills/typescript/SKILL.mdQuality
Discovery
32%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 provides a reasonable high-level summary of the skill's domain but lacks concrete actions and explicit trigger guidance. It reads more like a topic label than a functional description that would help Claude distinguish this skill from other TypeScript or coding convention skills. The absence of a 'Use when...' clause is a significant weakness.
Suggestions
Add a 'Use when...' clause specifying triggers like 'Use when writing or reviewing TypeScript code in the Graph Explorer project, or when the user asks about coding conventions, branded types, or type patterns for Graph Explorer.'
List specific concrete actions the skill enables, such as 'Enforces branded type patterns, applies function declaration style rules, validates type-safe API contracts, and reviews code for Graph Explorer TypeScript standards.'
Include natural trigger terms users might say, such as 'code style', 'coding standards', 'TS rules', 'type patterns', or 'code review' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (TypeScript/Graph Explorer) and some actions (branded types, function style preferences, type safety patterns), but these are more like categories than concrete actions. It doesn't list specific things the skill does, like 'enforce branded type usage' or 'convert interfaces to type aliases'. | 2 / 3 |
Completeness | Describes what the skill covers at a high level but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'TypeScript', 'branded types', 'type safety', and 'Graph Explorer', but misses common variations users might say such as 'coding standards', 'style guide', 'linting rules', 'TS conventions', or 'code review'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Graph Explorer' provides some specificity, but 'TypeScript conventions and rules' could overlap with general TypeScript style guides or other project-specific coding convention skills. The branded types mention adds some distinctiveness. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise conventions skill that efficiently communicates project-specific TypeScript rules and branded type usage. Its main strength is the comprehensive branded types reference table with creator functions and locations. The primary weakness is the lack of concrete code examples showing correct usage patterns (e.g., a before/after example of using branded types instead of raw strings).
Suggestions
Add a brief code example showing correct branded type usage, e.g., `const id: VertexId = createVertexId("v1")` vs the incorrect `const id: string = "v1"`
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what branded types are conceptually (Claude already knows) and instead provides a direct reference table of types, creator functions, and locations. The general rules are terse and actionable. No wasted tokens. | 3 / 3 |
Actionability | The branded types table is a useful concrete reference, and the general rules are specific. However, there are no executable code examples showing correct vs incorrect usage of branded types or the function style preference, which would make the guidance more immediately actionable. | 2 / 3 |
Workflow Clarity | This is a conventions/reference skill rather than a multi-step workflow skill. The single-purpose nature (TypeScript conventions) is clearly communicated with unambiguous rules. No destructive or batch operations are involved, so no validation checkpoints are needed. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized with clear sections (General Rules, Branded Types) and a well-structured table. The import paths in the table serve as implicit navigation to source locations. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- 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.