Skip to main content
Use this scorecard before shipping a docs change. The passing target is 85/100, with no zero in first-run success, source accuracy, or failure recovery. It complements the installed techtrailhead/devrelskills gates:
  • use technical-tutorial for path pages and builder guides;
  • use api-docs-audit for API and MCP reference;
  • use code-examples for any page that teaches a request, CLI workflow, or service integration;
  • use tech-social and dev-newsletter when the page will feed launch, community, or changelog copy.

​
Rubric

​
Page gate

For each page:
  1. Does the first screen say what job the reader can finish?
  2. Is there a command, request, or concrete artifact to verify?
  3. Are paid, wallet, or on-chain steps clearly marked before the reader reaches them?
  4. Are protocol names explained only after the working path?
  5. Does the page link to the next likely step?
  6. Does the page avoid hype, filler, and generic capability claims?
  7. Does a tutorial page have prerequisites, expected output, common errors, and next steps?
  8. Does an API page include auth, params, response fields, error bodies, and rate limits?

​
Journey gate

For each journey:

​
API gate

For each API page:

​
Content gate

Run the high-quality-content-writer tools on changed MDX files:
Target: zero trope hits and quality score above 8.0.

​
Next