Scan Results: https://git-aic.pages.dev/docs
Vanity URL: scan.glintbase.xyz/git-aic-scan
64/100
Agent Readiness Score
AI-Friendly Docs
Parseable by AI models but has high token usage or lacks standard machine-readable hooks.
Category Breakdown
Context Optimization14 / 30
Code Block Execution10 / 30
Machine Readability20 / 20
Agent Tooling & MCP20 / 20
Detailed Findings
⚡
Context Optimization
14/30
llms.txt Auto-Discovery
llms-full.txt Consolidated Docs
Markdown Content Negotiation (Accept: text/markdown)
↳ AI Agent Fix Prompt
My documentation is returning excessive HTML to AI agents. Implement server-side content negotiation in my app. When a request includes the header 'Accept: text/markdown', return ONLY the technical content as clean Markdown. Strip completely: navigation menus, footers, cookie banners, sidebar links, breadcrumbs, social sharing buttons, interactive widgets, and any HTML not containing technical content. The response should contain only: - Page title as H1 - Section headings as H2/H3 - Body text - Code blocks with language tags - Parameter tables - No HTML tags, no CSS, no scripts
DOM Cleanliness Ratio (15% markdown/HTML)
↳ AI Agent Fix Prompt
Reduce layout boilerplate (header, footers, scripts) or use Markdown Content Negotiation to strip DOM noise.
🔧
Code Block Execution
10/30
This category was analyzed using structural heuristics. Results reflect your documentation's observable patterns.
Terminal Prompt Pollution (No "$" prefixes in copyable code)
Dependency & Import Completeness
↳ AI Agent Fix Prompt
No code blocks found to analyze.
Dynamic Variable Placeholders
↳ AI Agent Fix Prompt
No code blocks found to analyze.
🔍
Machine Readability
20/20
OpenAPI/Swagger Spec Auto-Discovery
JSON-LD Structured Schema (TechArticle / APIReference / Guide)
All checks passed — this category is agent-ready.
🤖
Agent Tooling & MCP
20/20
Model Context Protocol (MCP) Server Integration
Error Code Diagnostics & Cross-Referencing Index
All checks passed — this category is agent-ready.