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 (Mercurius in its references) or apollo-server-tests instead, not this skill.

71

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

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 — every section carries executable commands or complete code — with a well-sequenced test workflow and real bundle-based progressive disclosure. It loses points for duplicated setup commands across sections, a missing readiness/validation checkpoint before applying metadata, and inline content that belongs in the references directory.

Suggestions

Consolidate the repeated 'docker compose up' / 'hasura metadata apply' commands into a single place (e.g. the Running section) and reference it from How to use and Authoring to remove duplication.

Add an explicit readiness check before applying metadata (e.g. curl-wait loop on /healthz or the v1/metadata endpoint), since docker 'depends_on' does not wait for the engine to accept requests — this closes the workflow's main validation gap.

Move the CI workflow YAML and the inline permission-test code into the existing references/ directory (or a new references/ci-integration.md) so SKILL.md stays a lean overview with one-level-deep links.

DimensionReasoningScore

Conciseness

Mostly lean and command/code-driven with no basic-concept padding, but 'docker compose up', 'hasura metadata apply', and the admin-secret handling repeat across 'How to use', 'Authoring', and 'Running', and the References section restates links already cited inline.

4 / 5

Actionability

Fully executable throughout: a complete docker-compose.test.yml with required-variable guards, curl and hasura CLI commands with headers, copy-paste-ready httpx/pytest code with real assertions, and a complete CI workflow YAML — covering the common cases.

5 / 5

Workflow Clarity

A clear 7-step sequence (stack up → metadata apply → per-test seeding → role-override queries → assert → matrix + JWT smoke test → teardown with -v and metadata reset) with explicit assertion checkpoints and an anti-patterns table; minor gaps include no engine-readiness check before hitting :8080 and no explicit failure-recovery loop.

4 / 5

Progressive Disclosure

Good structure with a single one-level reference (references/permission-matrix-tests.md, verified present) clearly signaled and a well-organized References section; however the ~30-line CI YAML and the inline permission-test code (which overlaps the reference file's content) could be pushed into references to keep SKILL.md a leaner overview.

4 / 5

Total

17

/

20

Passed

Description

92%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 is a strong example: it enumerates concrete capabilities, gives an explicit 'Use when' clause, and actively disambiguates against sibling GraphQL-server test skills. Trigger-term coverage is good though a few natural synonyms are missing, keeping it just short of perfect.

DimensionReasoningScore

Specificity

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

5 / 5

Completeness

Explicitly answers both what (the enumerated testing capabilities) and when ('Use for a metadata-driven Hasura engine where row-level permissions dominate'), and additionally adds when-not-to-use guidance ('for a code-first server runtime harness use graphql-yoga-tests... or apollo-server-tests instead').

5 / 5

Trigger Term Quality

Good natural keyword coverage ('Hasura', 'GraphQL', 'role-based permission tests', 'row-level permissions', 'metadata', 'docker-compose'), but a few natural synonyms users might say (e.g. 'row-level security', 'tenant isolation') are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche (metadata-driven Hasura permission testing) with explicit disambiguation against sibling skills graphql-yoga-tests and apollo-server-tests, minimizing wrong-skill triggering.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents