# Donebear

[donebear.com](https://donebear.com)

- **Overall score:** 83/100 (Grade B)
- **Checks passed:** 16 / 29
- **Last computed:** 2026-05-11

## Components

### Content Discoverability

- **Score:** 88/100 · **Status:** fail
- **Summary:** 2 failed and 1 warning across 6 AFDocs checks.
- **Rationale:** Agents need a clear entry point and crawl map before they can reliably discover the right pages.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ✅ **LLMS TXT Exists** — llms.txt found at 1 location(s)
- ✅ **LLMS TXT Valid** — llms.txt follows the proposed structure (H1, blockquote, heading-delimited link sections)
- ✅ **LLMS TXT Size** — llms.txt is 3,225 characters (under 50,000 threshold)
- ❌ **LLMS TXT Links Resolve** — Only 11/15 same-origin sampled links resolve (73%); 4 broken 4 of 15 links in your llms.txt return errors. A stale llms.txt with broken links is worse than no llms.txt at all because it sends agents down dead ends with high confidence.
- ❌ **LLMS TXT Links Markdown** — Same-origin links point to HTML and no markdown alternatives detected Your llms.txt links point to HTML pages. Update them to .md URL variants so agents receive markdown instead of converted HTML.
- ⚠️ **LLMS TXT Directive** — llms.txt directive found in 10 of 15 sampled pages (5 missing) An llms.txt directive was found on some pages but is missing from others, or is buried deep in the page. Ensure the directive appears near the top of every documentation page.

### Markdown Availability

- **Score:** 62/100 · **Status:** partial
- **Summary:** 2 warnings across 2 AFDocs checks.
- **Rationale:** When markdown is available directly, agents spend less effort stripping presentation markup and guessing structure.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ⚠️ **Markdown Url Support** — 8/14 sampled pages support .md URLs (57%); inconsistent support 0 of 14 pages support .md URLs inconsistently. Ensure all documentation pages serve markdown when .md is appended to the URL.
- ⚠️ **Content Negotiation** — Content negotiation partially supported: 10 correct type, 0 wrong type, 4 HTML only Your server returns markdown content for Accept: text/markdown requests but with an incorrect Content-Type header. Set the response Content-Type to text/markdown for proper agent handling.

### Page Size and Truncation Risk

- **Score:** 74/100 · **Status:** fail
- **Summary:** 2 failed and 1 warning across 4 AFDocs checks.
- **Rationale:** Large pages and delayed primary content increase truncation risk and make retrieval less reliable.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ❌ **Rendering Strategy** — 4 of 15 sampled pages appear to be client-side rendered SPA shells (root detected); agents using HTTP fetches will see no content 4 of 15 pages use client-side rendering. Agents receive an empty shell with no documentation content. Enable server-side rendering or pre-rendering for documentation pages.
- ✅ **Page Size Markdown** — All 11 pages under 50K chars (median 2K, max 8K)
- ⚠️ **Page Size Html** — 7 of 15 sampled pages convert to 50K–100K chars (max 97K, 42% boilerplate) 7 of 15 pages convert to 50K-100K characters of markdown. These may be truncated on some agent platforms.
- ❌ **Content Start Position** — 4 of 15 sampled pages have content starting past 50% (worst 100%) 4 of 15 pages have content starting past 50% of the converted output. Agents may never see the documentation content. Move or remove inline CSS/JS that precedes the content area.

### Content Structure

- **Score:** 100/100 · **Status:** pass
- **Summary:** 3 AFDocs checks pass.
- **Rationale:** Predictable sections, valid code fences, and serialized tabs make the content easier for agents to parse correctly.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ✅ **Tabbed Content Serialization** — No tabbed content detected across 15 sampled pages
- ✅ **Section Header Quality** — No tabbed content found; header quality check not applicable
- ✅ **Markdown Code Fence Validity** — All 20 code fences properly closed across 12 pages

### URL Stability and Redirects

- **Score:** 66/100 · **Status:** fail
- **Summary:** 1 failed across 2 AFDocs checks.
- **Rationale:** Stable URLs and sane redirect behavior prevent retrieval drift and broken tool references.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ❌ **Http Status Codes** — 8 of 15 sampled pages return 200 for non-existent URLs (soft 404) Your site returns 200 for non-existent pages (soft 404). Agents try to extract information from the error page content instead of recognizing the page is missing. Configure your server to return 404 for pages that don't exist.
- ✅ **Redirect Behavior** — No redirects detected across 15 sampled pages

### Observability and Content Health

- **Score:** 100/100 · **Status:** fail
- **Summary:** 1 failed across 3 AFDocs checks.
- **Rationale:** Coverage, parity, and cache behavior determine whether agents can trust the content they retrieve.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ✅ **LLMS TXT Freshness** — llms.txt covers 100% of 3 sitemap doc pages; 29 llms.txt links not in sitemap (may indicate stale links or incomplete sitemap)
- ❌ **Markdown Content Parity** — 4 of 11 pages have substantive content differences between markdown and HTML (avg 27% missing) 4 pages have substantive content differences between markdown and HTML (avg 27% missing). Agents receiving the markdown version are getting outdated or incomplete content. Regenerate markdown from source or fix the build pipeline.
- ✅ **Cache Header Hygiene** — All 16 endpoints have appropriate cache headers

### Authentication and Access

- **Score:** 100/100 · **Status:** partial
- **Summary:** 1 skipped across 2 AFDocs checks.
- **Rationale:** Agents need either public access or a clear alternative path when documentation is gated behind auth.
- **Reference:** [AFDocs reference](https://afdocs.dev)

**Checks**

- ✅ **Auth Gate Detection** — All 15 sampled pages are publicly accessible
- ⏭️ **Auth Alternative Access** — All docs pages are publicly accessible; no alternative access paths needed

### Full Content Discoverability

- **Score:** 100/100 · **Status:** pass
- **Summary:** llms-full.txt passes all checks.
- **Rationale:** A full-document snapshot gives long-context agents a single canonical corpus to ingest without repeated crawling.
- **Reference:** [llms-full.txt guide](https://www.mintlify.com/docs/ai/llmstxt#llms-full-txt)

**Checks**

- ✅ **LLMS Full Exists** — Found llms-full.txt.
- ✅ **LLMS Full Size** — llms-full.txt size is within the expected range.
- ✅ **LLMS Full Valid** — llms-full.txt has a recognizable markdown structure.
- ✅ **LLMS Full Links Resolve** — llms-full.txt links resolve successfully.

### Agent Skills

- **Score:** 100/100 · **Status:** pass
- **Summary:** skill.md passes all checks.
- **Rationale:** Agent skills provide product-specific operating guidance that plain documentation pages do not encode on their own.
- **Reference:** [skill.md guide](https://www.mintlify.com/docs/ai/skillmd)

**Checks**

- ✅ **Skill MD** — Found a legacy skill.md file.

### MCP Server

- **Score:** 0/100 · **Status:** fail
- **Summary:** MCP has 1 failing check.
- **Rationale:** A discoverable MCP server lets agents use first-class tools instead of scraping pages and inferring behavior.
- **Reference:** [MCP guide](https://www.mintlify.com/docs/ai/model-context-protocol)

**Checks**

- ❌ **MCP Server Discoverable** — No MCP server was discovered at the expected endpoints.
- ⏭️ **MCP Tool Count** — Skipped because the MCP server was not discoverable.