schema
Schema storage and discovery in Graph Explorer, including SchemaStorageModel persistence, edge connections, incremental schema growth, and related Jotai atoms.
35
31%
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/schema/SKILL.mdQuality
Discovery
40%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 identifies a clear and distinctive technical niche around Graph Explorer schema storage, which minimizes conflict risk. However, it lacks a 'Use when...' clause entirely, and the listed capabilities read more like a component inventory than concrete actions a user would request. The trigger terms are overly technical and miss natural language variations.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about storing, retrieving, or growing schemas in Graph Explorer, or when working with SchemaStorageModel or schema-related Jotai atoms.'
Rephrase capabilities as concrete actions rather than component names, e.g., 'Persists and retrieves graph schemas, manages edge connections between schema nodes, supports incremental schema growth' instead of listing model names.
Include natural trigger terms a user might say, such as 'schema management', 'add to schema', 'graph schema discovery', or 'schema persistence'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Graph Explorer schema storage) and lists several specific concepts (SchemaStorageModel persistence, edge connections, incremental schema growth, Jotai atoms), but these read more like technical component names than concrete user-facing actions. | 2 / 3 |
Completeness | Describes what the skill covers (schema storage and discovery) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also only moderately clear, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant technical keywords like 'Graph Explorer', 'SchemaStorageModel', 'Jotai atoms', 'edge connections', and 'incremental schema growth', but these are highly technical terms rather than natural phrases a user would say. Missing common variations like 'schema management', 'store schema', or 'graph schema'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'Graph Explorer', 'SchemaStorageModel', 'Jotai atoms', and 'incremental schema growth' creates a very specific niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 8 / 12 Passed |
Implementation
22%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as architectural documentation rather than an actionable skill. It explains the schema storage design well but provides no concrete code examples, no step-by-step workflows, and no executable guidance for Claude to follow when working with schema storage. The three-state explanation for edgeConnections is the strongest piece of non-obvious domain knowledge.
Suggestions
Add concrete code examples showing how to use `updateSchemaFromEntities()`, read from `SchemaStorageModel`, and interact with the Jotai atoms (e.g., how to access or update schema state).
Include a step-by-step workflow for common tasks like 'adding a new vertex type to the schema' or 'debugging a failed edge connection discovery', with validation checkpoints.
Convert the descriptive prose into actionable instructions — e.g., instead of 'these are automatically merged', show the exact function call and expected input/output.
Add a quick-start section at the top with the most common operation Claude would need to perform with schema storage.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some explanatory prose that Claude wouldn't need, such as explaining why edge connections run separately and the general concept of persistent caching. The three-state explanation for edgeConnections is useful domain knowledge, though. | 2 / 3 |
Actionability | No executable code, no concrete commands, no examples of how to use the atoms or call updateSchemaFromEntities(). The content describes architecture and types but never shows how to actually do anything — it reads as documentation rather than instruction. | 1 / 3 |
Workflow Clarity | There is no sequenced workflow or process steps. The content describes what happens conceptually (schema sync, incremental growth) but never provides a step-by-step procedure for any task, nor any validation checkpoints. | 1 / 3 |
Progressive Disclosure | Key files are listed with clear paths, which is helpful for navigation. However, there are no bundle files to reference, no links to deeper documentation, and the content is a single flat document with no layered structure beyond basic headings. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 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.