Skip to content
Back to skills

Composio Integrations

ASecurity

Use when connecting Claude to external apps (Slack, GitHub, Gmail, etc.) using the Composio Connect framework.

  • 666 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added February 8, 2026
toolsgitapidatabasedocumentation

Works with

  • cli
  • api

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill composio-integrations --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Composio Integrations?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Composio Integrations
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-composio-integrations/badge)](https://www.skillsdirectory.com/skills/majiayu000-composio-integrations)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
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.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.