/integrate

Make it your own.

In Claude Code, use the slash command and add your context. In Codex, select integrate from the just-vibe skill picker, then send the same brief.

Version 0.11.0 also supports /jv integrate, /just-vibe integrate and /jv:integrate in Claude. See shortcut setup and context examples.

What the agent does

1. Resolve the provider version and request/response schemas, and verify compatibility with the project.
2. Implement a narrow boundary that keeps secrets out of code and logs and adds timeout and error behavior.
3. Validate against a controlled fake or sandbox for success, refusal, timeout and malformed replies before any live verification.

Inputs

• service/library, intended use, environment, and credentials mechanism. Requires supported interface documentation and local integration points.

Optional context: scope, references, constraints, successCriteria, environment, mode, budget.

Scope

Reads

Client/server adapter, configuration names, errors, and tests; no account purchase or live side effects unless requested.

Writes

Apply: only the requested local changes and relevant isolated verification. Inspect/plan requests remain inspection/planning. External actions require their exact action and target in session authorization.

Mode

Apply; service/library, intended use, environment, and credentials mechanism. Requires supported interface documentation and local integration points.

Prerequisites

Resolve the user brief and inspect the relevant project or supplied evidence. External capabilities are optional unless the selected action actually needs them.

Expected output

• Integration code behind a boundary contract, configuration names and instructions, a failure matrix, and fake or sandbox validation evidence.

How the work is checked

• A valid response works; authentication failure or timeout produces a useful recoverable error.

When to stop or clarify

• Missing credentials block live verification only. Never hard-code secrets or imply sandbox checks prove production readiness.

Handling missing context

Infer

Resolve the named files, existing scripts, current task and earlier corrections from the conversation and repository.

Assume

Use the narrowest interpretation that completes a reversible local task; state a consequential assumption once.

Ask

Ask when competing targets or incompatible success conditions would change the result; continue independent inspection first.

Technical guidance

Evidence

Resolve provider/library version, credentials ownership, request/response contracts and failure semantics.

Method

Use the supported client and boundary adaptation, validate external data and reconcile uncertain mutating responses.

Pitfall

A mock success does not prove provider configuration, and retrying after timeout can duplicate a remote effect.

Check

Exercise a controlled successful exchange, rejected/malformed response and timeout, recording which boundaries were real.

Situational decisions

When a timeout may follow a completed external mutation: Reconcile by stable operation identity before retrying, and expose uncertainty to the caller.

When the provider reports results by callback or webhook: Implement or reuse a verified receiver with api-webhooks (raw-body signature check, idempotent receipt, replay window) and reconcile state from it, not from client redirects.

The coding agent follows this workflow using its available tools. Installation does not grant service access or guarantee an outcome. Read the compatibility notes.

Keep exploring