Conciseness

The body is dense and free of padding, but the Overview re-explains Hasura's per-table/role/operation model Claude largely knows, and the "Running" section repeats the exact docker compose up and hasura metadata apply commands already given in Authoring - minor over-explanation that could be trimmed, matching anchor 4 rather than the every-token-earns-its-place level.

Actionability

Fully executable throughout: a complete docker-compose.test.yml with required-variable interpolation, curl and hasura CLI commands, a worked example with exact headers and assertions, a runnable httpx/pytest test function, and a full CI services config - copy-paste ready and covering the common cases (row-filter hold, permission-error responses, admin contrast).

Workflow Clarity

The 7-step "How to use" sequence is clear (bring-up, metadata apply, seed, query, assert, matrix coverage, teardown) with concrete validation checkpoints (assert row filters, extensions.code = "permission-error", affected_rows: 0, status_code), but there is no explicit error-recovery feedback loop (e.g. what to check when metadata apply or a matrix assertion fails), so it sits at anchor 4 rather than 5.

Progressive Disclosure

The bundle structure is clean - one real, one-level-deep reference (references/permission-matrix-tests.md) that is clearly signaled for the detailed by-role and matrix patterns, plus named cross-plugin references - but the body itself carries heavy inline detail (full CI workflow, full compose file, full worked example), making it a dense overview with minor organization gaps rather than a lean one.

Specificity

Enumerates concrete components - "a docker-compose test instance, metadata API setup, x-hasura-role and x-hasura-user-id headers, and a role by table by operation permission matrix against the v1/graphql endpoint" - which is several specific items, but they are phrased as deliverables rather than actions with minor coverage gaps, matching the anchor-4 shape rather than comprehensive action coverage.

Completeness

Explicitly answers when ("Use when a Hasura GraphQL Engine needs tests, especially role-based row permissions") and what (the enumerated test-instance, metadata, header, and permission-matrix apparatus) with concrete trigger phrases, matching the anchor-5 example structure.

Trigger Term Quality

Natural terms a user would say are present - "Hasura", "tests", "role-based row permissions", "GraphQL Engine" - giving good keyword coverage, though common synonyms like "authorization" and "row-level security" are missing.

Distinctiveness Conflict Risk

"Hasura GraphQL Engine" pins a clear niche with distinct triggers and minimal conflict risk, even against closely related GraphQL-testing skills (apollo/yoga variants).