Name: hasura
Rating: 62.4 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

hasura

Hasura integration. Manage Users, Organizations. Use when the user wants to interact with Hasura data.

Quality

74%

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

Quality

Content

82%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 strong state-based validation checkpoints for the connection workflow. Its weak spots are mild over-explanation of known concepts, broken step numbering in the connection flow, and a popular-actions table that borders on bulk reference material better suited to a separate file.

Suggestions

Fix the connection-flow numbering: add an explicit "Step 1"/"1a" heading, label the action search/run steps as subsequent numbered steps, and make every "skip to Step N" reference resolve to a real heading.

Trim concept explanations Claude already knows, e.g. the "Developers use Hasura to build data-driven applications faster..." sentence and the "focus on the integration logic rather than auth plumbing" aside.

Consider moving the 16-row popular-actions table into a references/ file and keeping only a few key examples inline, so SKILL.md stays a lean overview pointing to detailed material.

Dimension	Reasoning	Score
Conciseness	Largely efficient CLI commands with minimal padding, but a few lines over-explain concepts Claude already knows (e.g. what Hasura is, "focus on the integration logic rather than auth plumbing"). It is not a 5 because some trimming is possible, and not a 3 because it is mostly lean rather than carrying several unnecessary explanations.	4 / 5
Actionability	Provides fully executable, copy-paste-ready membrane commands with flags and JSON examples, plus a concrete popular-actions table and parameter-passing examples covering the common cases. It clearly meets the anchor for fully executable, specific examples covering common cases.	5 / 5
Workflow Clarity	The connection flow has explicit validation checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a polling feedback loop, but the step numbering is broken ("skip to Step 2" with no labeled Step 2; "1b" under a section with no "1a"). It is not a 5 because the sequence labels are confusing, and not a 3 because checkpoints are explicit rather than merely implied.	4 / 5
Progressive Disclosure	A single well-organized file with clear section headers and a scoped popular-actions overview; no bundle files exist. It is not a 5 because the 16-row actions table is borderline bulk reference content that could be split out with no external reference layer, and not a 3 because the structure is clearly organized rather than only "some structure".	4 / 5
	Total	17 / 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 successfully states both what the skill does and when to use it, anchored to a clearly distinct product (Hasura). Its main weakness is thin action specificity and limited trigger-term variety, keeping it in the mid-range rather than top-tier.

Suggestions

Replace the generic verb "Manage" with concrete Hasura actions, e.g. "Run GraphQL queries and mutations, track/untrack tables, manage metadata and event triggers, execute raw SQL".

Expand the "Use when" clause with natural trigger phrases users would say, e.g. "Use when the user wants to query or mutate Hasura data, manage Hasura metadata, or run SQL against a Hasura-connected database".

Dimension	Reasoning	Score
Specificity	Names the domain (Hasura) and 1-2 actions ("Manage Users, Organizations"), but the actions are generic ("Manage") and not a comprehensive concrete list. It is not a 4 because several specific actions aren't listed, and not a 2 because domain and concrete targets are both named.	3 / 5
Completeness	Both "what" (Hasura integration; manage Users, Organizations) and an explicit "when" ("Use when the user wants to interact with Hasura data") are present, but the trigger is a single clause rather than a rich concrete list. It is not a 5 because the trigger phrases aren't comprehensive, and not a 3 because the "when" is explicitly stated rather than only weakly implied.	4 / 5
Trigger Term Quality	Includes the natural keyword "Hasura" / "Hasura data" but offers no synonyms, variations, or common phrasings beyond that. It is not a 4 because coverage is thin rather than "good with a few missing", and not a 2 because "Hasura" is a specific, relevant term rather than purely generic language.	3 / 5
Distinctiveness Conflict Risk	Names the specific product Hasura with its own distinct trigger ("Hasura data"), giving it a clear niche with minimal overlap risk against other skills. This matches the anchor for a clear niche with distinct triggers.	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/hasura/SKILL.md
Commit: f484c82

Reviewed: ~18 hours 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.