Conciseness

A ~1670-line monolith with substantial padding Claude does not need: conceptual "Core Concepts" bullet lists ("Zero Code: No resolver writing...", "Real-time by Default: Every query automatically has a subscription counterpart"), generic best-practice advice ("Create appropriate indexes", "Document custom actions"), five complete example applications, and a links section — much of which restates Hasura's documented behavior. Not 1 because a large share is concrete configuration and commands rather than pure concept explanation; not 3 because the padding is extensive and time-sensitive details ("hasura/graphql-engine:v2.36.0", "Last Updated: January 2025") are not isolated in a deprecated/old-patterns section.

Actionability

Provides extensive concrete, mostly executable guidance: a full docker-compose.yml, Kubernetes manifests, `hasura migrate create/apply/status` commands, complete Metadata API JSON bodies, JWT claim structures, Auth0/Firebase/webhook code, and CI/CD YAML. Not 5 because several examples depend on undefined placeholder functions (`sendEmail`, `processPayment`, `fetchOrderDetails`, `validateToken`, `esClient`) and some listed env vars (e.g. `HASURA_GRAPHQL_RATE_LIMIT_PER_MINUTE`) are not standard engine configuration, leaving minor gaps.

Workflow Clarity

Sequences are present and coherent ("How it works" 1-2-3, the six-step Auth Flow, the create/edit/apply migration flow, the GitHub Actions deploy pipeline), and a Troubleshooting section lists error fixes, but workflows involving database and batch operations (metadata apply, migrate apply, production deployment) lack explicit validation checkpoints and feedback loops — `hasura migrate status` is shown but there is no verify-after-apply or rollback-on-failure step — which caps workflow clarity at 3 per the batch/database-operation rule. Not 4 because checkpoints are absent rather than a minor gap; not 2 because steps are clearly listed and ordered.

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/ directories) and everything is inlined in a single ~1670-line file: deployment manifests, five full application patterns, troubleshooting recipes, and API-level examples clearly belong in separate reference files, and the body never links out to any other file. Not 1 because section headers do provide navigable structure; not 3 because references are not merely unclearly signaled — they are entirely absent, and the inlined bulk is the core problem.

Specificity

Enumerates specific feature areas — "instant GraphQL APIs, permissions, authentication, event triggers, actions, and production deployment" — but they are topic nouns under the framing "Complete guide for Hasura GraphQL Engine including", with no concrete action verbs, so it reads as a table of contents rather than a capability statement. Not 2 because the enumerated areas go beyond minimal or generic; not 4 because no concrete actions are actually stated as verbs.

Completeness

Has a clear "what" ("Complete guide for Hasura GraphQL Engine including instant GraphQL APIs, permissions, ... production deployment") but entirely lacks a "Use when..." clause or any equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the "when" is not even weakly implied; not 2 because the "what" half is explicit and specific.

Trigger Term Quality

Contains strong natural keywords a user would say — "Hasura", "GraphQL", "permissions", "authentication", "event triggers" — but misses common variations and synonyms like "Postgres", "subscriptions", "real-time", or "schema stitching". Not 5 because coverage of natural terms is incomplete; not 3 because the terms present are natural and relevant rather than mere jargon.

Distinctiveness Conflict Risk

Names the specific product "Hasura GraphQL Engine" together with product-specific feature terms ("event triggers", "actions"), establishing a clear niche with minimal conflict risk against generic GraphQL skills. Confirmed against the 4 anchor: no meaningful overlap — the Hasura name is unambiguous and unlikely to trigger a wrong skill.