Skip to main content
The Hobbes API skill gives AI coding agents reviewed instructions for reading Hobbes data, updating the Playbook in staging, and publishing an explicitly approved agent version. It includes the endpoint map, scope requirements, pagination rules, preview safeguards, and publishing confirmation boundary.

View the Hobbes API skill

Review the complete agent instructions before installing the skill.

​
Install the skill

Use a client that supports the open Agent Skills format:
The listing shows hobbes-read-api. The package keeps this existing identifier for compatibility with earlier installations. If it still shows the older hobbes entry immediately after a documentation deployment, wait for Mintlify’s skill discovery cache to refresh before installing it. The hosted skill and its discovery metadata stay synchronized with this documentation.

​
Provide credentials safely

Create a minimum-scope key in Hobbes Settings, then provide it to the agent’s server-side environment:
Do not paste a key into an agent conversation, commit it to a repository, or place it in browser code. Remove it from the shell when the task is complete:

​
Example requests

Ask an agent to use the installed skill for tasks such as:
  • “Use the Hobbes Read API to incrementally sync qualified sessions into our CRM.”
  • “Export the last seven days of Hobbes sessions to newline-delimited JSON.”
  • “Find recently active high-intent prospects and rank them by lastSeenAt.”
  • “Retrieve one selected session transcript and preserve request IDs on errors.”
  • “Preview a change to our Playbook opening and show me the summary before applying it.”
  • “After I approve the exact staged version, publish it and report whether the tests passed.”
The skill tells the agent how to build or review the integration. It does not contain an API key, grant access to an organization, or bypass the confirmation required before a Playbook change or production publish.

​
Machine-readable resources

Use the OpenAPI specification as the field-level contract. The skill provides the workflow and safety rules that an API schema alone cannot express.