API purpose, base URL, auth requirements, environment variables, and account-safety boundaries.
Skill files
Draft skill files that teach agents how to use your API.
A skill file should be reviewed product guidance, not a raw endpoint dump. Sourced's current public path is the playbook: use the OpenAPI contract to draft the right auth, workflow, example, and safety instructions before installing anything in an agent environment.
01Details
What belongs in a reviewed skill file
Common workflows described as agent steps, not just endpoint lists.
Operation examples, request/response shapes, pagination, rate-limit notes, and destructive-action warnings.
Links back to canonical docs, llms.txt, generated SDKs, and MCP tools.
02Teams
How teams should use the playbook
Start from the OpenAPI contract and existing docs, then draft the agent-facing workflow guidance.
Have an engineer review safety constraints, auth wording, and destructive operations.
Install the reviewed skill file into the agent environment or repo alongside SDK/docs artifacts.
Refresh the file after OpenAPI changes so the agent instructions do not drift.
03Details
Manual path vs Sourced path
Manual path: write a skill from scratch, audit every endpoint, and remember to update it on each API release.
Sourced path today: generate SDKs, docs, llms.txt, and MCP artifacts from one OpenAPI source, then use the skill-file playbook for reviewed agent instructions until first-party skill-file emission is shipped.