product
Graph Explorer product overview including supported graph types, query languages, databases, key features, and high-level architecture.
37
35%
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/product/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.
This description reads more like a table of contents for a reference document than a skill description. It lacks concrete actions Claude would perform and has no explicit trigger guidance ('Use when...'). While it names a specific product (Graph Explorer), the description needs actionable verbs and clear selection criteria to be effective among many skills.
Suggestions
Add a 'Use when...' clause specifying triggers, e.g., 'Use when the user asks about Graph Explorer, its supported graph databases, query languages like Gremlin or SPARQL, or its architecture.'
Replace the passive listing with concrete actions, e.g., 'Provides details on Graph Explorer's supported graph types (property graph, RDF), compatible databases (Amazon Neptune), query languages, and architecture.'
Include natural user phrasings and specific product/technology names users might mention, such as 'Neptune', 'Gremlin', 'SPARQL', 'graph visualization', or 'what is Graph Explorer'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Graph Explorer product) and lists some areas covered (supported graph types, query languages, databases, key features, architecture), but these are categories of information rather than concrete actions Claude would perform. | 2 / 3 |
Completeness | Describes what the skill covers (product overview information) 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 weak (it's a reference document description, not an action description), warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'graph types', 'query languages', 'databases', and 'Graph Explorer', but misses common user phrasings like 'what is Graph Explorer', 'graph visualization', 'Neptune', or specific graph database names users might mention. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'Graph Explorer' as a specific product provides some distinctiveness, but 'graph types', 'query languages', and 'databases' are broad terms that could overlap with general database or graph-related skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
37%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 a product fact sheet rather than an actionable skill. While it is concise and well-organized, it provides zero executable guidance — no commands to set up, connect to, or use Graph Explorer. It describes what the product does but never instructs Claude on how to do anything with it.
Suggestions
Add actionable content such as concrete commands for setting up Graph Explorer (e.g., Docker run commands, connection configuration examples).
Include at least one executable workflow, such as steps to connect to a Neptune database, explore a graph, or export data.
Add references to supporting files (e.g., SETUP.md, CONNECTIONS.md) for detailed configuration and authentication procedures.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and well-structured. It avoids explaining what graph databases or React are, assumes Claude's competence, and every section delivers only essential information. | 3 / 3 |
Actionability | The skill is purely descriptive — it lists features and architecture but provides no concrete commands, code examples, configuration steps, or executable guidance for any task. | 1 / 3 |
Workflow Clarity | There are no workflows, steps, or processes described. The content is a static product overview with no sequenced actions or validation checkpoints. | 1 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and headers, but there are no references to supporting files for deeper topics like setup, configuration, or authentication details that would benefit from separate documents. | 2 / 3 |
Total | 7 / 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.