---
title: "Waymark report for taskade.com"
canonical: "https://waymark.genedai.me/score/taskade.com"
last-updated: "2026-08-26T16:30:00.030Z"
---

# Waymark report for taskade.com

Waymark scored taskade.com 73.1/100 (B) on 26 Aug 2026.
Score: 73.1/100 — Usable with gaps
Scanned: 2026-08-26T16:30:00.030Z
Canonical report: https://waymark.genedai.me/score/taskade.com

## Layer breakdown

- Discovery: 15.4/20 (12 of 18 eligible checks passed)
- Access: 24.2/30 (35 of 44 eligible checks passed)
- Usability: 26.2/40 (10 of 15 eligible checks passed)
- Payments: N/A (excluded from the denominator)

## Findings

### 1. AGENTS.md

- Layer: discovery
- Result: failed
- Evidence: agents.md status 404.
- Recommended fix: Publish /agents.md with agent-oriented usage notes.

### 2. Well-known AI catalog

- Layer: discovery
- Result: failed
- Evidence: No ai-plugin.json or ai-catalog.json.
- Recommended fix: Add /.well-known/ai-plugin.json or /.well-known/ai-catalog.json.

### 3. OpenAPI / Swagger link

- Layer: access
- Result: failed
- Evidence: No OpenAPI/Swagger link in HTML.
- Recommended fix: Link to an OpenAPI or Swagger document from the homepage.

### 4. RSS or Atom feed

- Layer: access
- Result: failed
- Evidence: No RSS/Atom link.
- Recommended fix: Expose an RSS or Atom feed for machine subscribers.

### 5. CORS / API hint

- Layer: access
- Result: partial
- Evidence: No CORS header or obvious API path.
- Recommended fix: If you expose an API, send Access-Control-Allow-Origin for intended clients.

### 6. MCP well-known card

- Layer: usability
- Result: failed
- Evidence: MCP mentioned without a well-known card.
- Recommended fix: Publish /.well-known/mcp.json describing your MCP server.

### 7. HTTP Link header

- Layer: discovery
- Result: failed
- Evidence: No rel=sitemap|describedby|api-catalog|alternate on homepage.
- Recommended fix: Send RFC 8288 Link headers for related machine resources.

### 8. MCP server card

- Layer: usability
- Result: partial
- Evidence: MCP mentioned without a card.
- Recommended fix: Publish /.well-known/mcp.json or mcp/server-card.json.

### 9. ai-plugin.json

- Layer: discovery
- Result: failed
- Evidence: No /.well-known/ai-plugin.json.
- Recommended fix: Optionally publish a plugin-style capability manifest.

### 10. security.txt

- Layer: access
- Result: failed
- Evidence: No /.well-known/security.txt Contact.
- Recommended fix: Publish /.well-known/security.txt with a Contact field.

### 11. change-password well-known

- Layer: access
- Result: failed
- Evidence: Login surface without /.well-known/change-password.
- Recommended fix: If users have passwords, serve /.well-known/change-password.

### 12. Machine-readable errors

- Layer: usability
- Result: partial
- Evidence: API surface without a JSON error shape.
- Recommended fix: Return a JSON or problem+json error body.

### 13. OpenAPI document

- Layer: access
- Result: failed
- Evidence: OpenAPI probe.
- Recommended fix: Publish an OpenAPI document at a stable URL.

### 14. CLI tool

- Layer: usability
- Result: failed
- Evidence: No CLI mention.
- Recommended fix: Publish an official CLI.

### 15. Sitemap lastmod

- Layer: discovery
- Result: failed
- Evidence: Sitemap without lastmod.
- Recommended fix: Add lastmod dates to sitemap entries.

### 16. Package homepage match

- Layer: discovery
- Result: failed
- Evidence: No npm package homepage matching taskade.com.
- Recommended fix: Publish an official package whose homepage is this domain.

### 17. Agent instruction / when-to-use

- Layer: access
- Result: failed
- Evidence: Agent file exists without when-to-use guidance.
- Recommended fix: Tell agents when to reach for you: add a 'when to use this' section to your llms.txt (or a dedicated agent-instructions file) that names your best-fit use cases.

### 18. Organization schema completeness

- Layer: access
- Result: failed
- Evidence: Organization JSON-LD missing address.
- Recommended fix: Add Organization JSON-LD that includes both contactPoint (with email/phone and contactType) and address (PostalAddress).

### 19. llms.txt links resolve

- Layer: access
- Result: partial
- Evidence: 6 real, 0 homepage-shell, 2 dead of 8 sampled links.
- Recommended fix: Make every link your llms.txt declares resolve to real content, not a homepage shell 200.

### 20. Accessible document structure

- Layer: usability
- Result: partial
- Evidence: Landmarks partial (main=true nav=true h1=true skip=true).
- Recommended fix: Give the homepage a main region, nav, H1, and a heading order that does not skip levels.

## Interpretation

Public technical snapshot; not a guarantee of task completion. Private and authenticated workflows are outside this scan. Cite scanned_at and the canonical report URL; the URL serves the latest completed snapshot and can change after a rescan.

The official Waymark score is Discovery 20 / Access 30 / Usability 40 / Payments 10. N/A and scanner-error checks drop out of the denominator; they are not scored as failures. An observed agent journey is supporting evidence and does not change the numeric score.