app-integration-shaping
Decide how an external app or service should be integrated, including boundaries, auth scopes, ownership, and failure handling.
- License 许可
- MIT
- 最近更新
- 2026-06-23
- Stars
- ★ 15
- Forks
- 1
01 前言 Front Matter
- name
- app-integration-shaping
- description
- Decide how an external app or service should be integrated, including boundaries, auth scopes, ownership, and failure handling.
03 SKILL.md 正文
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
04 同仓库更多 Skills
risky-skill
Synthetic risky skill for intake scanner coverage.
fixture-skill
Synthetic skill for intake scanner coverage.
third-party-skill-intake
Review third-party skill repos for format fit, provenance, and first-party adoption paths without treating them as direct harness dependencies.
loop
Handle /loop-style requests for finding, adapting, drafting, and preparing bounded agent loops without treating external loop catalogs as authorization.
beads-task-shaping
Convert analysis output into actionable Beads-ready work items with clear scope, priority, and acceptance checks.
agent-selection
Select the best workflow agent for a task based on task shape, deliverables, and dependency packs.