Name: edgedb
Rating: 60 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

edgedb

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

Quality

70%

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/edgedb/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 skill body is highly actionable with copy-paste Membrane CLI commands and a state-driven connection workflow with feedback loops. Its main weakness is conciseness: a marketing-style intro and a few explanatory asides add tokens Claude does not need.

Suggestions

Cut the opening "EdgeDB is a graph-relational database..." paragraph and the "so you can focus on the integration logic rather than auth plumbing" aside; assume Claude knows what EdgeDB and auth plumbing are.

Label the section referenced as "Step 2" (e.g. rename "Searching for actions" / "Running actions" to "Step 2: Search and run actions") so the "skip to Step 2" pointer resolves.

Consider moving the proxy flags table and the full clientAction state breakdown into a reference file to keep SKILL.md as an overview, since the skill is over 50 lines.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient concrete commands, but the opening paragraph ("graph-relational database designed as a successor to SQL... those who find traditional ORMs cumbersome") and asides like "so you can focus on the integration logic rather than auth plumbing" explain concepts Claude already knows.	3 / 5
Actionability	Commands are fully executable and copy-paste ready throughout — `membrane connection ensure`, `npx @membranehq/cli connection get <id> --wait --json`, `membrane action run ... --input '{...}'` — with a flag table covering the proxy use case.	5 / 5
Workflow Clarity	The connection workflow has a clear state-based sequence with checkpoints (READY / BUILDING / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a poll-again feedback loop, but "skip to Step 2" references a header that is not labeled, leaving a navigation gap.	4 / 5
Progressive Disclosure	Content is well-sectioned (Overview, Authentication, Connecting, Searching, Running, Proxy, Best practices) with no nested references, and no bundle files exist to verify; the inlined proxy flag table and connection-state detail could arguably live in separate files.	4 / 5
	Total	16 / 20 Passed

Description

66%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 names a distinct niche and includes an explicit use-when trigger, but its capability list is generic and its trigger vocabulary is thin. Tightening the actions and adding common synonyms (EdgeQL, queries, schema) would lift it.

Suggestions

Replace generic verbs with concrete EdgeDB capabilities, e.g. "Run EdgeQL queries, apply schema migrations, and manage records".

Expand trigger terms to include user-natural phrases like "EdgeQL", "query EdgeDB", "schema migrations", and "database records".

Keep the explicit "Use when..." clause but pair it with the more specific actions for a stronger what+when pairing.

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the EdgeDB domain plus a couple of actions, but the actions are generic (data/records are near-synonyms) rather than concrete like schema migration or EdgeQL execution.	3 / 5
Completeness	It explicitly answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with EdgeDB data"), but the what is somewhat generic so it falls short of the fully-concrete anchor 5.	4 / 5
Trigger Term Quality	The only natural trigger phrase is "interact with EdgeDB data"; common variations a user would say (EdgeQL, query, schema, migration, database) are missing.	3 / 5
Distinctiveness Conflict Risk	"EdgeDB integration" is a clear named-product niche with a distinct trigger ("EdgeDB data"), giving minimal overlap risk with other skills.	5 / 5
	Total	15 / 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/edgedb/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.