/ratel-integrate — load an agent's tools and skills through Ratel

Turn an existing agent repository into a working Ratel integration. First understand the agents and the capabilities they already own; then wire those same tools and skills through Ratel with the smallest framework-native change.

The deliverable is code, dependency, and test changes in the customer's repository. Do not create a .ratel/ratel-integrate.md plan unless the user explicitly asks for one.

Scope

Keep this integration deliberately narrow:

• Discover agents, tools, skills, and their current ownership boundaries.
• Register executable tools and skill bodies with Ratel.
• Give each agent Ratel's stable capability tools and, where the host adapter supports it, per-turn recall.
• Use @ratel-ai/vercel-ai-sdk for Vercel AI SDK agents and @ratel-ai/mastra for Mastra agents.
• Use the core SDK directly for other supported hosts; do not invent adapter packages.
• Preserve prompts, models, executors, schemas, middleware, memory, and request context unless a small wiring change is required.
• Do not add telemetry, experiments, feature flags, pilot logic, dashboards, A/B tests, or rollout machinery.

Observability is not a prerequisite. A small tool catalog or a skills-only agent is still valid when the user explicitly wants Ratel integrated.