# External Bot Integration

Builds and qualifies two-way external bots with identity, wakeup and recovery.

- Repository: https://github.com/paperclipai/paperclip (109885 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add paperclipai/paperclip --skill create-external-bot-integration -g -a claude-code -y`
Codex: `npx skills add paperclipai/paperclip --skill create-external-bot-integration -g -a codex -y`
Cursor: `npx skills add paperclipai/paperclip --skill create-external-bot-integration -g -a cursor -y`
Gemini CLI: `npx skills add paperclipai/paperclip --skill create-external-bot-integration -g -a gemini-cli -y`

## Description

Build and qualify external bots such as Dot in Paperclip. Use for two-way work, invitation, identity, wakeup, Runner lifecycle, native tools, recovery, and Cloud delivery. CLI adapters and app-only connectors use their existing skills.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Create an External Bot Integration

Make an existing external agent a useful Paperclip participant: Paperclip can
assign work to it, and it can initiate governed work from its own conversation.
It uses its relevant native capabilities, returns inspectable results to
Paperclip, and participates in normal admission, authority, and finalization.

This workflow incorporates the September 30, October 9, 2026 Dot integration.
Provider facts and code paths in the references are dated evidence, not a claim
that every future bot supports the same APIs. Verify the current implementation
and official provider documentation before choosing a transport or changing code.

## 1. Establish the release contract before narrowing the implementation

Read [release-contract.md](references/release-contract.md). Infer already-stated
requirements and authorization from the conversation. Ask only about consequential
unknowns; do not ask the user to repeat “two way,” Cloud, or use of Runner.

Record the target environment, acting identity, capabilities, allowed human setup
steps, delivery/stop expectations, and checkable finish line. Keep one compact
matrix in the existing plan or task. Follow repository conventions if creating a
plan file. “Works” must name its level: prototype, real provider, real Runner,
managed sandbox, deployed tenant, or unattended first-time onboarding.

Reuse the current implementation and qualification evidence. Inspect the relevant
checkout, instructions, app/Cloud PRs, and Runner artifact. Do not recreate work
already merged or apply an old plan to a different deployed revision.

## 2. Prove the uncertain provider boundary first

The rest: https://github.com/paperclipai/paperclip/blob/HEAD/.agents/skills/create-external-bot-integration/SKILL.md