product

Graph Explorer product overview including supported graph types, query languages, databases, key features, and high-level architecture.

Quality

27%

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/product/SKILL.md

Quality

Content

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 a product fact sheet rather than an actionable skill. While it's well-organized and reasonably concise, it provides zero executable guidance — no commands, no code, no workflows. It tells Claude what Graph Explorer is but not how to do anything with it.

Suggestions

Add actionable content such as connection setup commands, Docker deployment steps, or example configuration snippets that Claude can execute.

Include at least one concrete workflow (e.g., 'How to connect to a Neptune database' or 'How to deploy locally') with sequential steps and validation checkpoints.

Either reference bundle files for detailed guides (e.g., DEPLOYMENT.md, CONNECTION_SETUP.md) or inline the most critical how-to procedures.

Remove or minimize purely descriptive content (feature lists, architecture overview) and replace with task-oriented instructions Claude can act on.

Dimension	Reasoning	Score
Conciseness	Generally efficient but includes some unnecessary framing (e.g., 'Graph Explorer is a React-based web application that enables users to visualize and explore graph data without writing queries' is somewhat descriptive rather than instructive). The bullet points are reasonably tight but this is a product overview rather than actionable guidance, so some content feels like it's explaining things Claude could infer.	2 / 3
Actionability	The content is entirely descriptive — it lists features, supported databases, and architecture but provides no concrete commands, code examples, configuration steps, or executable guidance. There's nothing Claude can act on directly.	1 / 3
Workflow Clarity	There are no workflows, sequences, or steps described. The content is a static product overview with no process guidance for any task such as setup, connection, deployment, or exploration.	1 / 3
Progressive Disclosure	The content is well-organized with clear section headers and logical grouping. However, there are no references to deeper documentation, no bundle files, and no pointers to where Claude could find more detailed information about any of the listed features or setup procedures.	2 / 3
	Total	6 / 12 Passed

Description

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 identifies the domain (Graph Explorer product) and lists categories of information it covers, but it reads more like a table of contents than a skill description. It lacks concrete actions Claude would perform, has no explicit 'Use when...' trigger guidance, and could benefit from more specific terminology and natural user keywords.

Suggestions

Add an explicit 'Use when...' clause specifying triggers, e.g., 'Use when the user asks about Graph Explorer features, supported databases, graph query languages, or how Graph Explorer works.'

Replace the category listing with concrete actions, e.g., 'Explains Graph Explorer's supported graph types (property graph, RDF), compatible databases (Neptune, Neo4j), and query languages (Gremlin, SPARQL, openCypher).'

Include natural user keywords and variations such as 'graph database', 'graph visualization tool', 'graph queries', or specific product/technology names users might reference.

Dimension	Reasoning	Score
Specificity	The description names the domain (Graph Explorer product) and lists some areas it covers (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	The description answers 'what' at a high level (product overview covering certain topics) but completely lacks any 'when should Claude use it' guidance — there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric should cap completeness at 2, and since the 'what' is also weak, a score of 1 is appropriate.	1 / 3
Trigger Term Quality	Includes relevant terms like 'graph types', 'query languages', 'databases', and 'Graph Explorer' that users might mention, but misses common variations and natural phrasing users would use (e.g., 'graph database', 'graph visualization', 'Neptune', specific graph DB names).	2 / 3
Distinctiveness Conflict Risk	The mention of 'Graph Explorer' as a specific product name provides some distinctiveness, but 'graph types, query languages, databases' are broad enough to potentially overlap with other database or graph-related skills.	2 / 3
	Total	7 / 12 Passed

Validation

90%

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 — 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: 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.