Name: graphql-editor
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

graphql-editor

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

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/graphql-editor/SKILL.md

Quality

Content

61%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 delivers highly actionable, copy-paste-ready Membrane CLI commands in a well-organized single file. It is held back by some redundant/filler content, broken step numbering, and absent validation for destructive operations.

Suggestions

Remove the explanatory intro paragraph and the "GraphQL Editor Overview" element list, and deduplicate the `action list` command that appears in both "Searching for actions" and "Popular actions".

Fix the workflow numbering: add an explicit "Step 1" / "1a" and a clearly labeled "Step 2" so the "skip to Step 2" reference resolves.

Add a validation/verification checkpoint after running actions and proxy requests (e.g., inspect the `output` field, confirm status, handle errors and retry) since these can be destructive.

Dimension	Reasoning	Score
Conciseness	Commands are mostly efficient, but the intro paragraph explaining what GraphQL Editor is, the filler "GraphQL Editor Overview" element list, and the duplicated `action list` command across "Searching for actions" and "Popular actions" are unnecessary padding that could be tightened.	3 / 5
Actionability	Copy-paste-ready commands with `--json` flags, header/query/path-param options, and an input JSON example cover common cases, with only minor placeholder gaps like `CONNECTION_ID` and `/path/to/endpoint`.	4 / 5
Workflow Clarity	The connection flow has good feedback loops (state polling, CLIENT_ACTION_REQUIRED handling, error states), but step numbering is broken ("1b" with no "1a", "skip to Step 2" with no labeled Step 2) and destructive proxy/action operations lack validation checkpoints, capping the score at 3.	3 / 5
Progressive Disclosure	With no bundle files present, the single SKILL.md is well-organized into clear section headers and keeps content appropriately inline, with only minor organization gaps fitting the good-structure anchor.	4 / 5
	Total	14 / 20 Passed

Description

62%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 cleanly answers both what the skill does and when to use it with an explicit trigger tied to a distinct app niche. Its main weakness is generic action verbs that limit specificity and trigger-term richness.

Suggestions

Replace generic verbs with concrete GraphQL Editor actions (e.g., "design and visualize GraphQL schemas, manage nodes and fields, mock data, send requests") to lift specificity.

Add natural trigger synonyms such as "GraphQL schema design", "visual GraphQL editor", or "GraphQL Editor API" to broaden trigger-term coverage.

Tighten the "when" clause to mention concrete intents like "schema design, prototyping, or managing GraphQL Editor data" for a clearer trigger.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the GraphQL Editor domain alongside several actions, but the verbs are generic rather than concrete like "extract/fill/merge", matching the anchor that lists 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It states both a "what" ("Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with GraphQL Editor data"), but the "what" is generic enough that it falls short of the fully concrete anchor 5.	4 / 5
Trigger Term Quality	"GraphQL Editor", "data", "records", and "workflows" provide some relevant keywords, but common natural-language variations or synonyms are missing, fitting the anchor for partial keyword coverage.	3 / 5
Distinctiveness Conflict Risk	GraphQL Editor is a clearly distinct app niche with a specific trigger, though the generic action verbs (manage data, records, workflows) create minor overlap risk with other data-management skills, matching the mostly-distinct anchor.	4 / 5
	Total	14 / 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/graphql-editor/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.