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

High

Do not use without reviewing

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.

A thorough, executable skill body with strong concrete examples and a clear multi-step workflow that includes the necessary validation/reset steps for a destructive permission-testing context. Tightening the small redundancies and making the validate-then-proceed checkpoints more explicit would push it higher.

Suggestions

De-duplicate the role/header and docker/metadata-apply material between 'How to use', the worked example, and the CI block so each section adds new information.

Make validation feedback loops explicit (e.g., 'apply metadata, then verify the permission rule is loaded before running queries') rather than relying on assertions inside tests.

Consider extracting the permission-matrix fixture format and the JWT smoke-test detail into the references file to keep the SKILL.md overview tighter.

DimensionReasoningScore

Conciseness

Lean, well-sectioned content that assumes Claude's competence with no padding about what Hasura/GraphQL is; minor redundancy where the worked example and CI block restate role/header mechanics and docker/metadata-apply commands already shown.

4 / 5

Actionability

Copy-paste-ready guidance throughout—docker-compose, curl and hasura CLI commands, httpx test code, a parametrized pytest matrix, and CI YAML—covering the common cases concretely.

5 / 5

Workflow Clarity

The 7-step 'How to use' sequence is clear with validation present (asserting response shapes, permission-error codes, per-test seeding, teardown with -v and metadata reset between suites), satisfying the destructive/batch cap; minor gaps in explicit validate-then-proceed feedback loops keep it just below 5.

4 / 5

Progressive Disclosure

Overview kept inline while the detailed by-role queries and permission matrix are pushed to a real one-level-deep reference file (references/permission-matrix-tests.md, which exists) that is clearly signaled; organization is good with only minor gaps around external cross-skill pointers.

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.

A highly specific, well-triggered description that clearly states both capability and activation conditions, plus strong negative boundary guidance against sibling skills. Only minor room for broader synonym coverage in trigger terms.

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 the 'role-by-table-by-operation permission-matrix pattern'—giving comprehensive coverage.

5 / 5

Completeness

Explicitly answers both what (the wrapped testing patterns) and when ('Use for a metadata-driven Hasura engine where row-level permissions dominate') with concrete trigger phrasing.

5 / 5

Trigger Term Quality

Strong natural and technical terms a user would say ('Hasura GraphQL Engine', 'x-hasura-role', 'v1/graphql', 'metadata API', 'permission-matrix', 'row-level permissions'), but slightly short of full synonym/extension coverage that would warrant a 5.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (metadata-driven Hasura engine) and explicitly disambiguates from sibling skills ('graphql-yoga-tests', 'apollo-server-tests') with a 'not this skill' boundary clause, minimizing conflict risk.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents