Skip to the content.

Courtesy DM — Cloudflare 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. ~100 words.


Subject: Agent Readiness Report: Cloudflare scored 40/100


Howdy [Name],

Heads up — we shipped the first Agent Readiness Report scorecard this week, and Cloudflare was the test case. Score: 40/100 (Level 2). Net-positive on the Content-Signal directive you invented (we shipped a v0.1.2 rubric fix to credit it). Net-negative on the blog at 15/100 — the surface hosting your original Agent Readiness Score post lands at Level 1 against the rubric that post helped popularize.

Single highest-leverage fix to land you at Level 3: publish an MCP Server Card from cloudflare.com and reference it from the homepage hero. The capability is real. The signal isn’t.

Full report: https://agentsfirst.dev/reports/cloudflare/

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 — author of the cited post is the natural fit; press address is the lukewarm fallback.

Person Role Why them Channel
Vance Morrison Co-author of the April 2026 Agent Readiness Score post Most natural recipient — peer-reviewing their own post LinkedIn DM
André Jesus Co-author of the April 2026 Agent Readiness Score post Same LinkedIn DM
Matthew Prince CEO, Cloudflare Has personally posted on Content Signals and AI policy; will see signal even if he doesn’t reply X DM (he replies on X)
[email protected] Developer relations / press Lukewarm fallback if author DMs go unanswered after 5 days Email

Notes for the sender (Josh)