Make Your Site Agent-Ready with Link Headers

Where this fits

You've just launched a developer-facing homepage. You expect AI agents to discover your API catalog automatically, but when you run an agent-readiness scan, linkHeaders fails because your server returns no Link headers. This skill fixes that by codifying the RFC 8288 link headers you need to expose machine-readable resources to agents, directly on Cloudflare.

Why agents benefit

• Agents can discover /.well-known/api-catalog from the homepage without guessing site paths.
• service-desc and service-doc relation types tell agents whether to fetch an OpenAPI description or human documentation first.
• describedby gives agents a stable URL to retrieve additional context alongside the machine-readable resource.
• Multiple Link headers can point to different resources in one response, so agents get a complete discovery map in a single round trip.
• Passing the linkHeaders check in isitagentready.com gives you an objective signal that agent discovery works.

Practical scenarios

Expose an API catalog on a SaaS homepage

Your homepage is marketing content, not an API reference. Add Link: </.well-known/api-catalog>; rel="api-catalog" so agents know exactly where to look for available endpoints instead of scraping a landing page.

Route agents to the right docs

You have both OpenAPI and generated docs. Use service-desc for the OpenAPI file and service-doc for the human-readable docs. An agent can then choose the content type that fits its task, avoiding expensive markdown-to-OpenAPI guessing.

Add headers without touching origin code

You don't want to redeploy the origin server just for headers. Use Cloudflare Transform Rules or Workers to inject Link headers at the edge. This skill gives you the exact rule format and validation steps to confirm the edge response is correct.

Add it to your agent workflow

Install the skill with:

npx skills add fabricioctelles/skills --skill agent-ready-link-headers

Then ask your agent to implement it for a specific site:

Add agent-ready Link headers for https://example.com using Cloudflare Transform Rules.
Include api-catalog and service-desc relations, then validate with isitagentready.com.

The skill walks your agent through creating the response header rule, setting the proper registered relation types, and running a scan to verify the linkHeaders.status is "pass".

Compare before adopting

Before using this skill, compare it against manual Cloudflare rules and similar agent-discovery skills. Look at the quality of the README, whether the relation types follow registered RFC values, and how often the author updates it for Cloudflare API changes. Also ask whether the skill fits your workflow: it assumes Cloudflare and a homepage you control, so if you're on another edge provider, you'll need to adapt the transform rule configuration.

Why it is worth tracking

The skill has 74 stars and sits inside a larger agent-ready-cloudflare collection, which signals community interest in making sites agent-discoverable at the edge. Maintenance freshness matters here because Cloudflare Transform Rules and agent discovery conventions evolve; check commits and pull requests before relying on it in production. If you're building agent-ready infrastructure, keep this skill on your radar and see how it compares to alternatives by visiting the skill page on OpenAgentSkill. https://www.openagentskill.com/skills/fabricioctelles-agent-ready-link-headers