Build or change a customer-system integration with explicit data mapping, permissions, retries and reconciliation. Use for connectors, imports, write-back and upstream APIs.
Start a fresh conversation. Replace the highlighted placeholders.
Use integrate to define the boundary and evidence for [authorized customer integration], mapping the producer, consumer, owner, direction, side effects, authentication scopes, network/data-retention boundaries, and permitted test environment. Provide one real input with its expected downstream result and one rejection/failure example, separating evidence for configuration, authentication, connectivity, contract compatibility, and end-to-end behavior.
Required inputs
[authorized customer integration]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: integratedescription: Build or change a customer-system integration with explicit data mapping, permissions, retries and reconciliation. Use for connectors, imports, write-back and upstream APIs.
integrate
Purpose
An integration with tested mapping and failure handling.
Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.
Principles
Work directly from the supplied permitted context. Standalone work does not require an engagement folder or initialization. Record filenames in the method are optional persistence destinations when no engagement is bound.
If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.