Use when connecting Claude to external apps (Slack, GitHub, Gmail, etc.) using the Composio Connect framework.
Scanned 2/12/2026
Install via CLI
Skills Directoryopenskills install majiayu000/claude-skill-registry---
name: integrations
description: Use when connecting Claude to external apps (Slack, GitHub, Gmail, etc.) using the Composio Connect framework.
---
# App Integrations (Composio Connect)
## Overview
This skill enables the Antigravity SDK to interact with 1000+ external applications via the Composio "Connect" protocol. Use it to automate engineering communication, issue tracking, and cross-platform synchronization.
## The /connect Workflow
**USAGE**: Trigger this internally or via `/connect` when a task requires interacting with an external system.
### Core Steps
1. **Identify the App**: Determine which service handles the requirement (e.g., GitHub for issues, Slack for notices).
2. **Authorize (If Needed)**: Use the `connect` tool to initiate OAuth or API key setup.
3. **Execute Action**: Send emails, create tickets, post messages, or update databases.
4. **Verify Result**: Confirm the external state has changed (read back the created issue or sent message).
## Integration Patterns
| Action | Example Command | Intent |
| :--- | :--- | :--- |
| **Email/Slack** | `connect-slack-message --channel #dev --text "Build passed"` | Automated status updates. |
| **Issue Tracking** | `connect-github-create-issue --repo client-repo --title "Bug: Login fails"` | Direct bug reporting from IDE. |
| **Data Sync** | `connect-notion-append-block --page id --content "Phase 2 done"` | Documentation synchronization. |
## Common Integration Mistakes
- **Shadow Executions**: Taking action without notifying the user (always confirm significant external mutations).
- **Hardcoded IDs**: Attempting to use static IDs without first listing/searching for the correct entities.
- **Pollution**: Sending too many automated messages (group notifications into summaries).
## Verification Checklist
- [ ] Correct app and action identified.
- [ ] Authorization status verified.
- [ ] Execution result confirmed (idempotency checked).
- [ ] User notified of external side effects.
No comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Run a single Terminal-Bench problem through Paperclip in a bounded, human-in-the-loop improvement cycle until the smoke passes, the board rejects the next fix, the iteration budget is exhausted, or a real blocker is named. Each iteration runs a bounded smoke against an isolated Paperclip App worktree, captures artifacts, diagnoses the exact stop point with `/diagnose-why-work-stopped`, requests board confirmation before any product fix, then reruns against the same worktree. Use whenever an i...
