# App Integration Shaping

> Decide how an external app or service should be integrated, including boundaries, auth scopes, ownership, and failure handling.

- Skill: `aibot88/app-integration-shaping` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add aibot88/app-integration-shaping`
- Raw SKILL.md: https://api.skillmd.com/api/skills/aibot88/app-integration-shaping/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: aibot88 (https://skillmd.com/u/aibot88)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/aibot88/app-integration-shaping

---


Use this skill when deciding whether a new external integration belongs in the system and how it should be shaped.

Compare these options explicitly:

- direct API client inside the application
- separate service or worker
- MCP server or connector-style integration
- no integration yet because the problem is still underspecified

Checklist:

- define the user or system workflow that needs the integration
- identify data movement, ownership, and trust boundaries
- specify required auth scopes and whether they are acceptable
- call out rate limits, retries, partial failure, and observability needs
- end with the recommended integration style and why it is the least-wrong option

Avoid:

- defaulting to MCP because it is fashionable
- burying auth scope risk inside implementation detail
- merging integration design with product prioritization