CtrlK
BlogDocsLog inGet started
Tessl Logo

the-graph

The Graph integration. Manage data, records, and automate workflows. Use when the user wants to interact with The Graph data.

55

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/the-graph/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a solid, command-driven integration guide with a clear workflow and validation checkpoints for connection readiness. Trimming the introductory concept explanation and the vague overview tree would improve token efficiency.

Suggestions

Remove or condense the opening "The Graph is a decentralized indexing protocol..." sentence and auth-plumbing commentary, which explain concepts Claude already knows.

Replace the vague "Use action names and parameters as needed." under the overview tree with a concrete example of mapping a user need to a discovered action.

Expand error-state handling beyond "check the error field for details" with a retry or diagnostic step for CONFIGURATION_ERROR/SETUP_FAILED.

DimensionReasoningScore

Conciseness

Mostly command-focused and efficient, but it opens by explaining what The Graph is ("decentralized indexing protocol...") and includes filler like "so you can focus on the integration logic rather than auth plumbing" that Claude does not need.

3 / 5

Actionability

Provides concrete, executable commands throughout (install, login, connection ensure, action list/run, request proxy) with clear flag tables; minor gaps remain around CONNECTION_ID substitution and discovering specific action IDs.

4 / 5

Workflow Clarity

Clear sequence (install → auth → connect → poll for readiness → search → run) with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a re-poll feedback loop; error recovery is limited to "check the error field for details".

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no external bundle files needed; the standalone "The Graph Overview" tree plus "Use action names and parameters as needed" is a minor organization gap rather than nested references.

4 / 5

Total

15

/

20

Passed

Description

57%Weight 40%Scale 1-5

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 clearly identifies its niche (The Graph) and provides an explicit use-when trigger, but the capability list is generic. Tightening the action verbs to reflect The Graph-specific operations would lift specificity.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with The Graph-specific actions such as querying subgraphs, indexing blockchain data, or running GraphQL queries.

Add natural trigger synonyms users might say, e.g. "subgraphs", "indexing", "blockchain data", or "GraphQL".

Make the 'what' clause concrete enough to distinguish from general data-management skills.

DimensionReasoningScore

Specificity

Names the domain ("The Graph") but the actions — "Manage data, records, and automate workflows" — are minimal and generic rather than concrete capabilities tied to the protocol.

2 / 5

Completeness

It explicitly answers both what ("The Graph integration. Manage data, records, and automate workflows.") and when ("Use when the user wants to interact with The Graph data."), though the what is somewhat generic.

4 / 5

Trigger Term Quality

The natural term "The Graph" and "interact with The Graph data" are present, but common variations or synonyms (blockchain data, querying, subgraphs, indexing) are missing.

3 / 5

Distinctiveness Conflict Risk

The "The Graph" trigger carves a clear niche with minimal conflict risk, though the generic "manage data, records" phrasing leaves minor overlap with adjacent data-integration skills.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-skills
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.