Skip to content
Is Agentic

github.com

Ready with a few material gaps

75/ 100

Technical readiness score

What should the prompt cover?

19 findings · 5 selected

Failures (10)

Warnings (9)

How the score adds up

37 checks

The agent completed the observed task

One run shows how an agent performed, but it does not determine the technical score.

Task

What does github.com do and who is it for? Explain it back to me.

15 steps5 reasoning steps5 searches

home
docs
docs
/enterprise
search
search
search
search
search
/features
1 observed runView journey ↗

Critical access needs attention

These checks describe whether an ordinary agent can enter, read, and operate the public site.

  • Agents can reach the site

    Crawler access, bot defenses, and explicit agent policy.

    3 / 3 passed

  • Core content is available

    Useful content remains accessible without a fragile browser-only path.

    0 / 1 passed

  • Navigation fails safely

    Redirects and missing pages give agents a recoverable path.

    1 / 2 passed

  • Controls are understandable

    Forms and interactive controls expose usable names and structure.

    4 / 4 passed

Advertised capabilities have material gaps

Optional surfaces appear only when the scan finds positive evidence that the site offers them.

Public website

Needs work

69%

10 of 18 mature checks passed

API

Blocked

49%

6 of 14 mature checks passed

Authentication

Ready with gaps

80%

2 of 3 mature checks passed

MCP

Blocked

42%

0 of 2 mature checks passed

Fix these gaps first

Critical access gaps come first, followed by gaps in capabilities the site advertises.

  1. 01

    Agent-friendly 404s

    Return a real HTTP 404 (or 410) status for nonexistent paths - never a 200 with your app shell, which makes agents believe every path exists. For full credit, give the 404 response a short markdown body pointing agents at your sitemap, llms.txt, or docs index. Verify with `curl -s -o /dev/null -w "%{http_code}" https://yourdomain.com/some-path-that-does-not-exist` - it must print 404.

    Critical access
  2. 02

    Content without JavaScript

    Server-side render your homepage so AI crawlers see meaningful content without JavaScript. Ensure an H1 and 500+ chars of text in raw HTML.

    Critical access
  3. 03

    OpenAPI spec published

    Publish an OpenAPI (Swagger) specification at /openapi.json or /api/openapi.yaml. This is how agents understand your API surface automatically.

    Advertised capabilities
  4. 04

    OAuth 2.0 support

    Implement OAuth 2.0 for API authentication. Publish your authorization server metadata at /.well-known/oauth-authorization-server.

    Advertised capabilities
  5. 05

    MCP Apps support

    Add MCP Apps support to your MCP server using @modelcontextprotocol/ext-apps. Expose ui:// resources and add _meta.ui.resourceUri to tools so agents can render interactive UIs directly in conversation.

    Advertised capabilities

Audit the checks behind the score

Applicable evidence is grouped by how it contributes to this preview model. Bonus checks appear only when they add points.

Essential6 of 10 passed · 60.5 / 80 points
  • Content without JavaScriptPartial (67%)
  • Not blocked by bot detectionPassed
  • robots.txt agent-user policyPassed
  • Redirect hygienePassed
  • OpenAPI spec publishedFailed
  • Agent crawler reachabilityPassed
  • OAuth 2.0 supportPartial (40%)
  • Scoped permissionsPassed
  • JSON error responsesPassed
  • Agent-friendly 404sPartial (50%)
Recommended12 of 27 passed · 11.1 / 20 points
  • Developer resource discoverabilityPartial (33%)
  • Brand name discoverabilityPassed
  • robots.txt AI crawler policyPartial (50%)
  • Sitemap existsFailed
  • Content efficiencyPartial (50%)
  • JSON-LD structured dataFailed
  • Public API/docs linked from homepagePassed
  • Agent instruction / when-to-usePassed
  • Metadata completenessPassed
  • Organization schema completenessFailed
  • Trust anchor pagesPassed
  • Page token budgetPassed
  • Code fence validityPassed
  • Developer portalPassed
  • Public API with reachable endpointsPassed
  • Agent onboarding frictionPassed
  • MCP server / manifestPartial (83%)
  • Rate limit response headersPartial (50%)
  • Idempotency-Key supportFailed
  • REST typed error modelFailed
  • REST versioning / deprecation policyPartial (33%)
  • REST async-job patternFailed
  • CLI tool availablePassed
  • Multi-language SDK packagesPassed
  • MCP Apps supportFailed
  • API schema complexity analysisFailed
  • Function calling compatibilityFailed
Bonus signals16 positive · +3.8 points
  • Wikipedia / Wikidata entity presencePassed
  • NPM/PyPI SDK packagePassed
  • Listed on skills.shPassed
  • ChatGPT app listedPassed
  • pricing.md existsPartial (50%)
  • MCP well-known discoveryPassed
  • llms.txt existsPassed
  • llms.txt formattingPassed
  • Skills.sh skill qualityPassed
  • llms.txt links resolvePartial (50%)
  • Sandbox / test environmentPassed
  • Accessible document structurePassed
  • Native interactive controlsPassed
  • Accessible names on controlsPassed
  • Form control labelingPassed
  • Accessibility-tree injection safety (bonus)Passed

Inspect the underlying audit

The complete Ora audit uses evidence from the scan on . After applying changes, run another scan from the homepage to refresh these recommendations.

Score alerts

A weekly report with ranking changes, new agent feedback, and score alerts for github.com.

Source: Ora API

Snapshot 2026-08-15T05-27-15-631+00-00