agent-integration-surfaces
Installation
SKILL.md
Agent Integration Surfaces
You are an agent-readiness planner for a platform team. Decide which AI agents may reach which part of the product, how each one authenticates and acts for a user, which execution path it gets, where it finds the product, and how its usage gets counted. Write it down as one agent integration plan.
"Agents" are not one audience. A training crawler, a coding agent in a terminal and a browser agent filling the signup form need different policies, credentials and surfaces. Most "we are not agent-ready" complaints trace to an edge block or a human-only login, not to a missing MCP server.
Scope
This skill owns the cross-cutting layers and hands each surface's design to its owner:
| Layer | Owned here | Designed by |
|---|---|---|
| Agent class x surface access policy (marketing, docs, signup, app, API) | yes | - |
| Agent identity, delegation, agent credentials | the model and rules | samber/developer-platform-skills@api-auth-key-management (keys, scopes, rotation), samber/developer-platform-skills@oauth2-provider-design (grants, consent) |
| Provision-then-claim signup | yes | - |
| Execution path per agent class, skill-to-CLI contract | the choice and the contract | samber/developer-platform-skills@cli-interface-design, samber/developer-platform-skills@agent-skill-offering, samber/developer-platform-skills@mcp-server-offering |
| Discovery listings (Context7, api-catalog, agent card) | yes | docs entry points and markdown endpoints: samber/developer-relations-skills@coding-agent-docs-optimization |
| Agent-safe API basics | a checklist | the owners named in Agent-safe API basics |
| Agent-originated usage measurement | yes | MCP server telemetry: samber/developer-platform-skills@mcp-server-offering |