Courtesy DM — Cursor Agent Readiness Report
Plain-text email or LinkedIn DM, sent the day the report ships. Modeled on Josh’s daily email style guide: “Howdy”, short, direct, no hedging, “Yeehaw!” close. Celebratory tone — this is L3, congratulating. ~120 words.
Subject: Agent Readiness Report: Cursor scored 70/100
Howdy [Name],
Heads up — we shipped an Agent Readiness Report on Cursor today. 70/100, Level 3 — only the second product in our public series to crack ‘Agents First.’ What stood out: docs.cursor.com is the first surface in the series to max out the agent-capabilities dimension at 30/30 — real /AGENTS.md at the docs root, MCP Server Card at the well-known path, OAuth-with-PKCE discovery, and a homepage hero that names MCP / CLI / SDK / API alongside human onboarding. The team building the product lives the way it builds.
One move would push you to Level 4: lift the docs playbook to cursor.com itself — /AGENTS.md + MCP Server Card + a Content-Signal directive on robots.txt. Same hosting, same team, same conventions; pulls the marketing root from L2 → L3 and the docs from L3 → L4 in one shipment.
Full report: https://agentsfirst.dev/reports/cursor/
No need to respond — sharing in case useful, and gladly re-score once anything ships.
Yeehaw!
🤖 Josh
Recipient candidates
Send to one of these. Pick based on warmth — Eric Zakariasson is the natural DevX/DevRel fit and is publicly the most active Cursor voice on agent-tooling topics; Sualeh is the founder closest to the product/docs surface.
| Person | Role | Why them | Channel |
|---|---|---|---|
| Eric Zakariasson | Developer Experience, Cursor | Owns the surface that scored 70 — actively posts about MCP, AGENTS.md workflows, and agent-native dev practice. The most likely person to triage and route the fix list internally. Author of public Cursor content on AGENTS.md self-learning experiments. | LinkedIn DM or X (@ericzakariasson) |
| Sualeh Asif | Co-founder & CPO, Cursor | Owns product vision and developer experience end-to-end. Active on X. Will see signal even if he doesn’t reply directly. | X DM (@sualehasif993) |
| Aman Sanger | Co-founder & COO, Cursor | Runs growth + developer-community. Active on X about agent tooling and Cursor’s roadmap. Public-facing co-founder voice for the company. | X DM (@amanrsanger) |
[email protected] |
Cursor general inbound | Lukewarm fallback if author DMs go unanswered after 5 days. |
Notes for the sender (Josh)
- Pick ONE recipient on day-of-publish. DevRel/DevX lead > co-founder > general inbound.
- Eric Zakariasson is the right first send — he runs the surface that scored 70, and he routinely engages on developer-experience-with-agents posts. Highest reply odds.
- Send via X DM if the recipient is mutuals; LinkedIn DM otherwise. Email last.
- Hold the general inbound address for week-2 if neither author replies.
- If a reply comes back with “we just shipped the marketing-root fixes,” queue a re-score for the next bi-weekly slot. The follow-up report (“Cursor moved cursor.com from L2 to L3 in 14 days, lifting docs to L4”) is even better content than the first one — and given Cursor’s release cadence, it’s plausible.