Name: slash-graphql
Rating: 59.2 (1 reviews)
Author: membranedev

slash-graphql

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

Quality

68%

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

Quality

Content

75%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 concrete, copy-paste CLI commands and a well-sequenced connection workflow with state checkpoints. Its main weaknesses are conceptual padding in the intro/overview and the absence of verification steps after mutating operations.

Suggestions

Trim the opening paragraph and the "Slash GraphQL Overview" bullet list of GraphQL concepts that Claude already knows, leading with the first command instead.

Add an explicit verify/inspect step after running mutating actions or proxy POSTs (e.g. re-query to confirm the change) to satisfy the validation checkpoint for destructive operations.

Consider moving the proxy flag table and the clientAction object schema into a short reference file and linking to it, keeping SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable commands, but the opening paragraph ("fully-managed GraphQL backend service... without managing infrastructure or writing resolvers") and the "Slash GraphQL Overview" list of Type/Field/Query/Mutation explain concepts Claude already knows, fitting the anchor for mostly efficient content with some unnecessary explanation.	3 / 5
Actionability	Every section gives copy-paste-ready commands ("npm install -g @membranehq/cli@latest", "membrane connection ensure", "membrane action run ... --input '{\"key\": \"value\"}'") with a flag table, fully executable and covering the common cases per the top anchor.	5 / 5
Workflow Clarity	The connection workflow is clearly sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll loop, but mutating actions and proxy requests lack an explicit verify-after-run step, matching the anchor for clear sequence with minor validation gaps.	4 / 5
Progressive Disclosure	Content is well-organized into clearly headed sections with no nested references and no bundle files present; the only gap is that inlineable detail like the proxy flag table and clientAction schema could live in a separate reference file, fitting the good-structure anchor with minor organization gaps.	4 / 5
	Total	16 / 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 correctly answers both what and when and targets a specific, distinct product, but its action verbs are generic and its trigger phrasing relies on a single keyword without synonyms. Tightening the actions and adding concrete trigger terms would lift it.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with specific operations such as "query and mutate GraphQL data, run actions, and proxy raw API requests".

Expand the "Use when" clause with concrete natural triggers, e.g. "Use when the user wants to query or mutate Slash GraphQL data, run GraphQL actions, or proxy requests to a Slash GraphQL endpoint".

Add common synonyms or file/URL cues (e.g. dgraph.io/slash-graphql, Slash endpoints) so the trigger matches how users actually phrase the request.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the domain plus 2-3 actions, but the actions are generic rather than concrete, matching the anchor for 1-2 concrete actions without comprehensive coverage.	3 / 5
Completeness	It states both a what ("Manage data, records, and automate workflows") and a when ("Use when the user wants to interact with Slash GraphQL data"), but the when lacks concrete trigger phrases beyond the product name, matching the anchor where both are present yet the when could be more explicit.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Slash GraphQL data" surfaces the relevant keyword "Slash GraphQL" but offers only one main term with no synonyms or variations, fitting the anchor for some relevant keywords missing common variations.	3 / 5
Distinctiveness Conflict Risk	"Slash GraphQL" names a specific product giving it a clear niche and minimal conflict risk, but the generic accompanying actions keep it just below the fully distinct anchor that pairs specific triggers with specific actions.	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/slash-graphql/SKILL.md
Commit: f484c82

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.