connectors

Database connector and explorer patterns for Gremlin, openCypher, and SPARQL, including the query template tag and escapeString usage.

Quality

31%

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/connectors/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 provides a high-level architectural overview of connector and explorer patterns but lacks the concrete, actionable guidance needed to be useful. There are no code examples showing how to use the `query` template tag or `escapeString()`, no workflow for creating or modifying connectors/explorers, and the content reads more like documentation notes than executable instructions.

Suggestions

Add concrete, executable code examples showing usage of the `query` template tag and `escapeString()` for each query language (Gremlin, openCypher, SPARQL).

Include a step-by-step workflow for creating a new connector or explorer, with specific file paths and interface implementations.

Show the actual interface definition from `src/connector/index.ts` or provide a concrete example of implementing it, rather than just describing it abstractly.

Add example input/output for query construction to make the guidance copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but includes some unnecessary explanatory text like 'Explorers abstract querying databases with different query languages' and 'They shield the application from query language specifics' which describe concepts rather than instruct. Some lines could be tightened.	2 / 3
Actionability	No concrete code examples, no executable commands, no import paths beyond vague references to `@/utils`. The skill describes patterns abstractly ('use the query template tag', 'use escapeString()') without showing actual usage examples or copy-paste ready code.	1 / 3
Workflow Clarity	No sequenced steps, no workflow described, no validation checkpoints. The content is a collection of descriptive bullet points without any process or procedure to follow.	1 / 3
Progressive Disclosure	There is one cross-reference to another skill file (.kiro/skills/typescript/SKILL.md) for branded types, which is good. However, the references to source paths (src/connector/, @/utils) lack links to actual documentation files, and no bundle files exist to support deeper exploration.	2 / 3
	Total	6 / 12 Passed

Description

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 technical niche with specific query languages and utilities, giving it good distinctiveness. However, it lacks explicit trigger guidance ('Use when...') and could be more specific about the concrete actions it enables. The description reads more like a topic label than actionable selection guidance for Claude.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user needs to write or debug Gremlin, openCypher, or SPARQL queries, or when connecting to graph databases like Amazon Neptune or similar.'

List concrete actions the skill enables, e.g., 'Build graph database queries, create connection patterns, escape query strings, and explore graph data using Gremlin, openCypher, and SPARQL.'

Include natural user terms like 'graph database', 'Neptune', 'graph query', 'traversal', 'RDF', or 'property graph' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (database connector/explorer) and specific query languages (Gremlin, openCypher, SPARQL), and mentions specific utilities (query template tag, escapeString), but doesn't list concrete actions like 'create queries', 'traverse graphs', or 'build connection patterns'.	2 / 3
Completeness	Describes what the skill covers (database connector patterns for specific query languages) 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' should cap completeness at 2, and the 'what' is also only partially clear, warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant technical keywords like 'Gremlin', 'openCypher', 'SPARQL', 'escapeString', and 'query template tag' that users working with graph databases might use. However, it misses common natural terms like 'graph database', 'Neptune', 'query', 'traversal', or 'RDF'.	2 / 3
Distinctiveness Conflict Risk	The combination of specific graph query languages (Gremlin, openCypher, SPARQL) and specific utilities (query template tag, escapeString) creates a clear niche that is unlikely to conflict with other skills.	3 / 3
	Total	8 / 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.