Composio
ComposioHQ/composio
Route and complete Composio work across Composio For You and Composio Platform.
A skill your agent uses when the user wants to add, connect, sign in to or fix an MCP connector (a server that gives you tools for an app such as GitHub, Linear or Notion).
Install Connector Setup
$ npx skills add katipally/openlive --skill connector-setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install katipally/openlive connector-setup --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/katipally/openlive.git skills-src && mkdir -p .claude/skills && cp -r skills-src/services/agent/skills/connector-setup .claude/skills/connector-setup && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "connector-setup" agent skill from https://github.com/katipally/openlive/tree/main/services/agent/skills/connector-setup into .claude/skills/connector-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connector-setup", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/katipally/openlive/tree/main/services/agent/skills/connector-setupType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add katipally/openlive --skill connector-setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install katipally/openlive connector-setup --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/katipally/openlive.git skills-src && mkdir -p .agents/skills && cp -r skills-src/services/agent/skills/connector-setup .agents/skills/connector-setup && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "connector-setup" agent skill from https://github.com/katipally/openlive/tree/main/services/agent/skills/connector-setup into .agents/skills/connector-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connector-setup", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add katipally/openlive --skill connector-setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install katipally/openlive connector-setup --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/katipally/openlive.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/services/agent/skills/connector-setup .cursor/skills/connector-setup && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "connector-setup" agent skill from https://github.com/katipally/openlive/tree/main/services/agent/skills/connector-setup into .cursor/skills/connector-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connector-setup", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/katipally/openlive.git --path services/agent/skills/connector-setup--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add katipally/openlive --skill connector-setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install katipally/openlive connector-setup --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/katipally/openlive.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/services/agent/skills/connector-setup .gemini/skills/connector-setup && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "connector-setup" agent skill from https://github.com/katipally/openlive/tree/main/services/agent/skills/connector-setup into .gemini/skills/connector-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connector-setup", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install katipally/openlive connector-setupInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add katipally/openlive --skill connector-setup -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/katipally/openlive.git skills-src && mkdir -p .github/skills && cp -r skills-src/services/agent/skills/connector-setup .github/skills/connector-setup && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "connector-setup" agent skill from https://github.com/katipally/openlive/tree/main/services/agent/skills/connector-setup into .github/skills/connector-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connector-setup", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add katipally/openlive --skill connector-setup -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install katipally/openlive connector-setup --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/katipally/openlive.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/services/agent/skills/connector-setup .opencode/skills/connector-setup && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "connector-setup" agent skill from https://github.com/katipally/openlive/tree/main/services/agent/skills/connector-setup into .opencode/skills/connector-setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "connector-setup", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
connector-setup- GitHub stars
- 336
- Token cost
- ~860 tokens
- SKILL.md length
- 518 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when the user wants to add, connect, sign in to or fix an MCP connector (a server that gives you tools for an app such as GitHub, Linear or Notion).
- Works in 2 steps: Find out which server. Most services… → The user is asked to approve the add.…
- The user wants to add
- SKILL.md covers Secrets, Adding one, Signing in and Fixing one
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Connector Setup is an agent skill from katipally/openlive. Use when the user wants to add, connect, sign in to or fix an MCP connector (a server that gives you tools for an app such as GitHub, Linear or Notion).
Its SKILL.md is about 860 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Media & Creative, covering App automation through connectors and Text to speech and voice. It works with GitHub and Notion. The repository describes itself as: Opensource, on-device voice + vision layer for AI agents. Bring any model or coding agent; the whole speech loop (VAD, STT, TTS, barge-in) runs locally. An open alternative to… The licence is Apache-2.0.
When your agent uses it
- The user wants to add
- Fix an MCP connector (a server that gives you tools for an app such as GitHub
Example prompts
- “/connector-setup”
Requirements
- Docker
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Find out which server. Most services document either
- The user is asked to approve the add. Then read the result
What it can do on your machine
Read from SKILL.md and the folder at commit c9121eb. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Connector Setup loads about 860 tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 518 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from katipally/openlive at commit c9121eb, republished under its Apache-2.0 licence (© katipally). 518 words, ~860 tokens.
Download SKILL.mdSave it as
.claude/skills/connector-setup/SKILL.md (or your agent's skills folder).- name
- connector-setup
- description
- Use when the user wants to add, connect, sign in to or fix an MCP connector (a server that gives you tools for an app such as GitHub, Linear or Notion).
Setting up connectors
A connector is an MCP server that gives every brain in OpenLive more tools.
Its tools show up as <connector>__<tool> once it is connected. You help the
user add one, sign in, and fix one that is not working.
Your tools: list_connectors, add_connector, connector_sign_in,
reconnect_connector.
Secrets
- Never ask the user to say an API key or token out loud, and never repeat one back. Suggest they paste it in Settings, Capabilities, Connectors, where it is stored encrypted.
- If they paste one to you, pass it in
headers(or insidejson) and do not mention its value again. Tool results never show it.
Adding one
- Find out which server. Most services document either:
- A URL (a remote server), as
https://mcp.example.com/mcp. Calladd_connectorwithurland a shortname. - A JSON block in the
mcpServersshape, with acommandsuch asnpx(a local server). Calladd_connectorwithjsonset to that block, as text.
- A URL (a remote server), as
- The user is asked to approve the add. Then read the result:
- connected: done. Say how many tools it offers.
- needs sign-in: go to "Signing in".
- waiting for the user to allow it to run: a local server runs a
program on their computer, so only the user can allow it: Settings,
Capabilities, Connectors, then Review and Allow on that connector. You
cannot allow it, and no tool can.
Tell them where to click, then check with
list_connectors. - failed: go to "Fixing one".
If they do not know the URL or JSON, offer to look it up (the research skill) on the service's own documentation site.
Signing in
For a connector that needs sign-in, call connector_sign_in with its id. It
opens the service's sign-in page in their browser, or gives you the address
to pass on. Ask them to finish signing in there, then call list_connectors
to confirm it is connected.
Only remote (URL) connectors sign in. A local one takes its keys as env values in Settings, Capabilities, Connectors.
Show full SKILL.md (190 more words)Show less
Fixing one
Start with list_connectors. Then by status:
- switched off: they turned it off in Settings. Ask if they want it on; they switch it there.
- waiting to be allowed: as above, only they can allow it, in Settings.
- needs sign-in:
connector_sign_in. - not connected yet: normal. It connects when one of its tools is first
used, or call
reconnect_connector. - failed: read the error, then
reconnect_connectoronce. If it fails again, explain the likely cause in plain words:- "command not found" or ENOENT: the program (
npx,uvx,docker) is not installed or not on the PATH. - 401 or 403: the key or sign-in is wrong or expired. Sign in again, or update the key in Settings.
- 404 or a connection error: the URL is wrong or the server is down.
- A crash right after starting: a missing env value the server needs.
- "command not found" or ENOENT: the program (
- connected but a tool is missing: tools can be switched off one by one
in Settings, Capabilities, Connectors. A server that changed its tools
shows them after
reconnect_connector.
Never retry the same thing more than twice. Tell the user what you found and what they can do in Settings.
© katipally, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in services/agent/skills/connector-setup of katipally/openlive.
Open the folder on GitHubat commit c9121eb
Compare with similar skills
Connector Setup next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Connector Setup this skillkatipally/openlive | 336 | — | ~860 | Automated safety check: Pass | Apache-2.0 | |
| ComposioComposioHQ/composio | 30k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Connect Apps with ComposioComposioHQ/awesome-claude-skills | 77k | 3 repos | ~557 | Automated safety check: Pass | None | |
| Composio Cloud Toolsquarqlabs/argus | 277 | — | ~543 | Automated safety check: Pass | Apache-2.0 | |
| Superset Integration Toolssuperset-sh/superset | 15k | — | ~1.6k | Automated safety check: Warn | Custom licence | |
| Bmad Install Agentvibespaulpreibisch/AgentVibes | 155 | — | ~557 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Connect Apps with Composio
ComposioHQ/awesome-claude-skills
Connects an agent to 1000+ external apps through the Composio Tool Router plugin, so it can actually send emails, create issues and post messages instead of only drafting them.
Composio Cloud Tools
quarqlabs/argus
Routes requests to external SaaS apps such as GitHub, Gmail, Google Calendar, Slack, Notion and Linear through cloud tools, with safeguards on irreversible actions.
Superset Integration Tools
superset-sh/superset
Lists and calls the tools of connected integrations such as Linear, GitHub, Sentry or Notion through the superset mcp command, without storing a token on the machine.
Bmad Install Agentvibes
paulpreibisch/AgentVibes
Install AgentVibes TTS voice system for BMAD agents. An agent skill from paulpreibisch/AgentVibes.
Integrations
butterbase-ai/butterbase-skills
Use BEFORE recommending or installing any third-party SaaS SDK for email (Resend, SendGrid, Postmark, Mailgun), SMS (Twilio), messaging (Slack), calendar (Google Calendar), CRM (HubSpot…
More from katipally/openlive
Research
katipally/openlive
A skill your agent uses when the user asks you to research, compare, fact-check or find current information, and the answer should come with sources.
Skill Creator
katipally/openlive
A skill your agent uses when the user wants to teach you a workflow, save how they like something done, or make a new skill.
Computer Use
katipally/openlive
Use before operating an app on the user's computer, such as clicking, filling a field, reading a window or moving through a website in their browser.
Related
Questions about Connector Setup
What does Connector Setup do?
A skill your agent uses when the user wants to add, connect, sign in to or fix an MCP connector (a server that gives you tools for an app such as GitHub, Linear or Notion). Connector Setup is an agent skill from katipally/openlive. Use when the user wants to add, connect, sign in to or fix an MCP connector (a server that gives you tools for an app such as GitHub, Linear or Notion).
When should I use Connector Setup?
Connector Setup fits situations like: the user wants to add; fix an MCP connector (a server that gives you tools for an app such as GitHub.
How do I install Connector Setup in Claude Code?
Run `npx skills add katipally/openlive --skill connector-setup -a claude-code`. Or copy the skill folder (services/agent/skills/connector-setup in katipally/openlive) into .claude/skills/connector-setup in your project. Claude Code loads it when a task matches its description.
How do I install Connector Setup in Codex?
Run `npx skills add katipally/openlive --skill connector-setup -a codex`. Or copy the skill folder (services/agent/skills/connector-setup in katipally/openlive) into .agents/skills/connector-setup in your project. Codex loads it when a task matches its description.
Can I use Connector Setup in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add katipally/openlive --skill connector-setup -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/connector-setup, .gemini/skills/connector-setup, .github/skills/connector-setup and .opencode/skills/connector-setup in your project.
What does Connector Setup need to run?
SKILL.md names no scripts, command-line tools or credentials: Connector Setup is instructions for the agent only. Our summary lists: Docker.
Does Connector Setup access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Connector Setup safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Connector Setup use?
Connector Setup is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Connector Setup use?
About 860 tokens (SKILL.md is roughly 3.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Connector Setup?
Skills that share tags, products or a category with Connector Setup: Composio (ComposioHQ/composio, 30k stars), Connect Apps with Composio (ComposioHQ/awesome-claude-skills, 77k stars), Composio Cloud Tools (quarqlabs/argus, 277 stars) and Superset Integration Tools (superset-sh/superset, 15k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Connector Setup?
katipally (a GitHub user) maintains it in katipally/openlive, which has 336 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 7, 2026.
Source: katipally/openlive on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.