CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/hasura-tests

Wraps Hasura GraphQL Engine testing patterns: docker-compose test instance, the metadata API for declarative schema/permission setup, x-hasura-role and x-hasura-user-id session headers for role-based permission tests, the v1/graphql endpoint via curl/HTTPie/native HTTP clients, and the role-by-table-by-operation permission-matrix pattern. Use for a metadata-driven Hasura engine where row-level permissions dominate; for a code-first server runtime harness use graphql-yoga-tests, apollo-server-tests, or mercurius-tests instead, not this skill.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Overview
Quality
Evals
Security
Files

Quality

Content

85%

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 and workflow-rich with executable code, clear validation checkpoints, and a well-signaled real reference file. Its main weakness is mild verbosity — the docker-compose stack is repeated and the Overview explains some Hasura basics Claude already knows.

Suggestions

Remove the duplicate docker-compose bring-up block (it appears in both 'Test instance setup' and 'Running'); reference the first occurrence instead to cut tokens.

Trim the Overview's explanation of Hasura permission mechanics (table/role/operation, row-filter/column-scope) since Claude already knows this; keep only the testable-concerns framing.

Consider offloading the CI integration YAML block into the references file alongside the permission-matrix fixture to keep SKILL.md focused on the core workflow.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete commands and code, but the Overview re-explains Hasura permission mechanics (concepts Claude largely already knows) and the docker-compose stack is shown twice (Authoring and Running/CI), so it could be tightened; matches the level-2 'mostly efficient but includes some unnecessary explanation' anchor rather than the lean level-3.

2 / 3

Actionability

Provides fully executable, copy-paste-ready artifacts: docker-compose YAML, curl and hasura CLI commands, httpx Python test code, pytest commands, and a CI workflow YAML — matching the level-3 anchor for concrete executable code.

3 / 3

Workflow Clarity

The 7-step 'How to use' sequence is clearly ordered with explicit validation/assertion checkpoints (assert response shape, extensions.code = 'permission-error', affected_rows: 0) and a metadata-reset teardown step; the worked example adds a validate->confirm feedback loop, satisfying the level-3 anchor for batch/metadata operations.

3 / 3

Progressive Disclosure

The body is an overview pointing to a single real, one-level-deep, clearly signaled reference ([references/permission-matrix-tests.md], which exists), matching the level-3 anchor of a clear overview with well-signaled one-level references rather than a monolithic wall or nested references.

3 / 3

Total

11

/

12

Passed

Description

100%

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 is specific, trigger-rich, and complete, with explicit 'Use for...' guidance and a strong negative-scope clause that distinguishes it from sibling GraphQL test skills. It does not over-claim and stays in third person.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'docker-compose test instance', 'metadata API for declarative schema/permission setup', 'x-hasura-role and x-hasura-user-id session headers', 'v1/graphql endpoint via curl/HTTPie/native HTTP clients', and 'role-by-table-by-operation permission-matrix pattern' — matching the level-3 anchor of several specific concrete actions.

3 / 3

Completeness

Explicitly answers what ('Wraps Hasura GraphQL Engine testing patterns...') and when ('Use for a metadata-driven Hasura engine where row-level permissions dominate'), plus a negative-scope clause, satisfying the level-3 anchor for both what AND when with explicit triggers; not level 2 because the 'when' is explicit, not implied.

3 / 3

Trigger Term Quality

Natural terms a user would say appear directly — 'Hasura', 'row-level permissions', 'permission tests', 'GraphQL' — with good coverage of common variations, matching the level-3 anchor rather than the jargon-only or partial-coverage anchors.

3 / 3

Distinctiveness Conflict Risk

Has a clear niche (metadata-driven Hasura engine with row-level permissions) and an explicit disambiguator ('for a code-first server runtime harness use graphql-yoga-tests, apollo-server-tests, or mercurius-tests instead, not this skill'), making conflict with sibling skills unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents