Name: graphlinq
Rating: 56.8 (1 reviews)
Author: membranedev

graphlinq

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

Quality

65%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/graphlinq/SKILL.md

Quality

Content

81%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 highly actionable with executable CLI commands and a clear connection-state workflow including a polling feedback loop. It is mostly concise and well-structured, with only minor verbosity and weak validation on proxy/write operations.

Suggestions

Add an explicit validation/verification step after proxy and action-run write operations (e.g., check the response state or re-query to confirm the change took effect) to lift workflow_clarity.

Remove duplicated action-list commands (the command appears under both 'Searching for actions' and 'Popular actions') to tighten conciseness.

Tighten prose around connection setup into an explicit numbered sequence so the BUILDING -> READY / CLIENT_ACTION_REQUIRED branching reads as a checklist.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable commands and flag tables, but includes some mild over-explanation (e.g., restating 'You should always search for actions in the context of a specific connection' and repeating the action-list command twice) that could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste ready commands for install, login, connection ensure/get with --wait, action list/run with --input, and proxy requests, plus a concrete flag table covering the common cases.	5 / 5
Workflow Clarity	The connection setup has a clear sequence with state-based polling (READY/BUILDING/CLIENT_ACTION_REQUIRED) and a feedback loop (poll again after user action), but lacks an explicit validation checkpoint for the destructive/proxy write operations and the numbered steps are mixed with prose.	4 / 5
Progressive Disclosure	Well-organized into overview, install, auth, connection, searching, running, proxy, and best-practices sections; no bundle files exist so everything is inline at one level, which is appropriate for this size, though some content (e.g., the full clientAction object schema) could be separated if the skill grew.	4 / 5
	Total	17 / 20 Passed

Description

50%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 names the domain and includes a 'Use when' trigger but uses generic verbs and lacks concrete trigger phrases or synonyms. It is functional but not exemplary on completeness or specificity.

Suggestions

Replace generic verbs with concrete platform actions (e.g., 'search actions, run workflows, query subgraphs, proxy API requests').

Expand the 'Use when' clause with specific natural triggers users would say (e.g., 'use when the user wants to automate GraphLinq workflows, query blockchain data, or run GraphLinq actions').

Add synonyms/brand variants in the trigger (e.g., 'GraphLinq, graphlinq.io, GLQ workflows') to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	It names the domain ('GraphLinq Protocol') and concrete actions ('Manage data, records, and automate workflows') but offers only generic verbs without comprehensive coverage of the platform's capabilities.	3 / 5
Completeness	It has a clear 'what' ('Manage data, records, and automate workflows') and a 'Use when' clause ('Use when the user wants to interact with GraphLinq Protocol data'), but the 'when' is only weakly implied and not elaborated with concrete trigger phrases, capping completeness at 3 per the guideline.	3 / 5
Trigger Term Quality	The phrase 'interact with GraphLinq Protocol data' is a natural trigger, but it lacks synonyms and the platform-specific terms users would say (e.g., workflows, automation, charts, subgraphs) beyond a single repeat of the brand name.	3 / 5
Distinctiveness Conflict Risk	The repeated brand name 'GraphLinq Protocol' creates a clear niche with minimal overlap risk, though the generic 'Manage data, records' verbs could still overlap with other data-management skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/graphlinq/SKILL.md
Commit: f484c82

Reviewed: 5 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.