Todos los casos de uso

Ingeniería

Add an API once as a shared plugin, not in one bot's chat

Every bot reinvents the same API connection, each with its own secrets.

Compartir

Qué dolía

Paul (@PaulShipsAI) gave a five-step answer on connecting an API to a fleet of bots. Not affiliated with xAI.

Qué instalar o crear

Check whether a shared plugin already exists; if not, add it once as a shared plugin or MCP; connect the account and secrets there; tell the fleet to use it rather than reinvent it; and require a human OK before paid API spend.

Bots

  • Fleet

    Uses the shared plugin instead of its own connection.

Plugins

  • Ninguno el primer día. Sigue los pasos del primer uso.

Rutinas

  • Ninguna en el primer uso. Mira primero una pasada manual.

El prompt

His five steps (author-quoted)

Quoted from @PaulShipsAI — as published. Do not invent a second system prompt.

1. Check if a shared plugin for that API already exists
2. If not → add it once as a shared plugin/MCP (not in one bot’s chat)
3. Connect the account / secrets there
4. Tell the fleet: use this plugin, don’t reinvent it
5. Paid APIs → human OK before spend

Primer uso

  1. 1Read https://x.com/PaulShipsAI/status/2108456937557762345 (credit @PaulShipsAI).
  2. 2Check the plugin list for an existing shared connection.
  3. 3If none, add the API once as a shared plugin/MCP and connect secrets there.
  4. 4Tell every bot to use that plugin.
  5. 5Add an approval rule before any paid API spend.

Valla de aprobación

Paid APIs need your OK before spend.

Qué ajustar

One connection, one place for secrets, one instruction to the fleet.

Fuente

Paul @PaulShipsAI · Publicación original

Sin afiliación con xAI. No escribimos este prompt. Siguen aplicando las condiciones de las plantillas de terceros.

Explorar plantillas

Explorar planos de equipo

Paquete Pro

¿Quieres la configuración completa, no solo la idea?

Los paquetes Pro te dan el texto de la tarea, los prompts, los horarios y los tropiezos de los casos de uso más populares.

Ver Pro