Algolia Agent Studio

Use this skill for Agent Studio work after confirming the product goal and the quality of the underlying Algolia data, events, and search configuration. Agent Studio experiences are only as good as the tools, records, guardrails, and measurement loops they can rely on.

Customer-Facing Standard

• Define the agent contract before setup: purpose, audience, tools, allowed actions, guardrails, escalation, and measurement.
• Treat data, events, permissions, and tool security as prerequisites, not follow-up polish.
• Use public academy.algolia.com for learning alignment and public algolia.com/doc for current implementation guidance when source-backed context is needed.
• When an Academy metadata reference pack is available, use only its title, url, course, module, learning_objectives, and updated_at fields for structure. If it is stale or no match exists, fall back to live Academy/docs lookup. Do not treat cached metadata as course content or implementation authority.
• Do not require custom Academy/docs access; use customer-provided sources only as optional context.
• When live Algolia data, analytics, index inspection, settings changes, or account actions are needed, use Algolia MCP, the Algolia CLI, or official Algolia skills for the live operation, then apply this skill to interpret results and validate the customer-ready implementation path.
• Produce a launch recommendation: launch, limited rollout, fix first, or do not start.
• Start the first agent with one narrow, high-intent job and the smallest tool/data surface that can solve it; breadth comes after evidence.

Official Companion Skills