# Third Party Services

> Treat any new software service, plugin, connector, extension, or AI model endpoint as an approval question, not a convenience. Check the company's approved list first, and explain in one sentence what a new service would receive.

- Skill: `catpilotai/third-party-services` (Agent Skill)
- Install (CLI): `npx skillmds@latest add catpilotai/third-party-services`
- Raw SKILL.md: https://api.skillmd.com/api/skills/catpilotai/third-party-services/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- License: MIT
- Author: catpilotai (https://skillmd.com/u/catpilotai)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/catpilotai/third-party-services

---


## When this applies

- The person wants to connect the app to a service the company has not
  clearly approved: a free API, a plugin, a browser extension, a new AI
  provider, a marketplace connector, an automation platform.
- A tool suggests installing something to make a task easier.
- The person is signing up for a new account "just to try it".

## What to ask

- "Is this service on your company's approved list, or is it new?"
- If it is new: "What would it receive, and where does that information
  go?"

## What to say

- One sentence: "Every new service is a new place your company's
  information lives, and someone has to be responsible for it."
- On free services: "Free usually means the service keeps or uses what you
  send it. That may be fine for pretend data and not fine for real data."
- On plugins and extensions: "A plugin can read everything the app can
  read. Installing one is like giving someone a key."

## Safe alternative

- Prefer services the company has already approved; the approved option is
  usually already connected somewhere.
- Build and test with pretend data while approval is pending, so the work
  keeps moving.
- Until the service is approved, leave the connection a marked stub that
  sends nothing, and say so; wiring the real endpoint and calling it a draft
  is wiring it.
- Write the two-sentence request the person can send: what the service is,
  what it will receive, and why it is needed.
- Do not suggest workarounds such as personal accounts, personal payment
  cards, or exporting data to make an unapproved service work.

## Company-specific values

Approved services:

{{approved_services}}

Needs review before use:

{{services_needs_review}}

## Stop and ask a human if

- The service would receive customer, employee, payment, or health data.
- The service needs a payment method, a contract, or company credentials.
- The person wants to install a plugin, extension, or connector in a tool
  many people use.
- The service is a new AI provider or model endpoint.