Composio
ComposioHQ/composio
Route and complete Composio work across Composio For You and Composio Platform.
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.
Install Superset Integration Tools
The automated check flagged lines worth reading first. See the safety section below.
$ npx skills add superset-sh/superset --skill integrations -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install superset-sh/superset integrations --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/superset-sh/superset.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/superset/skills/integrations .claude/skills/integrations && 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 "integrations" agent skill from https://github.com/superset-sh/superset/tree/main/plugins/superset/skills/integrations into .claude/skills/integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrations", 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/superset-sh/superset/tree/main/plugins/superset/skills/integrationsType 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 superset-sh/superset --skill integrations -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install superset-sh/superset integrations --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/superset-sh/superset.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/superset/skills/integrations .agents/skills/integrations && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "integrations" agent skill from https://github.com/superset-sh/superset/tree/main/plugins/superset/skills/integrations into .agents/skills/integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrations", 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 superset-sh/superset --skill integrations -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install superset-sh/superset integrations --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/superset-sh/superset.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/superset/skills/integrations .cursor/skills/integrations && 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 "integrations" agent skill from https://github.com/superset-sh/superset/tree/main/plugins/superset/skills/integrations into .cursor/skills/integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrations", 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/superset-sh/superset.git --path plugins/superset/skills/integrations--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 superset-sh/superset --skill integrations -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install superset-sh/superset integrations --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/superset-sh/superset.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/superset/skills/integrations .gemini/skills/integrations && 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 "integrations" agent skill from https://github.com/superset-sh/superset/tree/main/plugins/superset/skills/integrations into .gemini/skills/integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrations", 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 superset-sh/superset integrationsInstalls 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 superset-sh/superset --skill integrations -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/superset-sh/superset.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/superset/skills/integrations .github/skills/integrations && 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 "integrations" agent skill from https://github.com/superset-sh/superset/tree/main/plugins/superset/skills/integrations into .github/skills/integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrations", 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 superset-sh/superset --skill integrations -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install superset-sh/superset integrations --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/superset-sh/superset.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/superset/skills/integrations .opencode/skills/integrations && 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 "integrations" agent skill from https://github.com/superset-sh/superset/tree/main/plugins/superset/skills/integrations into .opencode/skills/integrations/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "integrations", 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
integrations- GitHub stars
- 15k
- Token cost
- ~1.6k tokens
- SKILL.md length
- 791 words
- Files
- 2
- Skills in repo
- 47
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
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.
- Works in 3 steps: Find the integration → List the tools before calling one → Call it
- Creating or updating an issue in a connected service such as Linear
- SKILL.md covers 1. Find the integration, 2. List the tools before…, 3. Call it and When another skill expects…, plus 2 more sections
- Calls jq
What it does
An integration here means an installed plugin with a connected account, and this skill explains how to reach its tools through the superset command line. The agent runs superset plugins list and reads the STATUS column: a connected account can be called, needs connection means nobody has authorized an account yet, and not installed means the plugin is gone while its credential is still live. Installing and connecting plugins belongs to a separate plugins skill.
Calling a tool takes two more steps. The agent lists a plugin's tools with superset mcp tools and reads the full description of the one it wants, since the listing carries no input schema, and it never calls a tool it has not listed. Then superset mcp call-tool takes the tool name, the plugin flag and JSON arguments, with secrets passed on stdin to keep them out of shell history. Superset's API attaches the stored credential and forwards the call, so no token is written to the machine.
When your agent uses it
- Creating or updating an issue in a connected service such as Linear
- Finding out which tools a connected integration exposes
- Working out why an integration's tools are failing
- Replacing mcp__linear__-style tools that another skill expects but are missing
Example prompts
- “Create a Linear issue titled Export 500s for the ENG team.”
- “What tools does the Sentry integration expose?”
- “List the open issues in Linear through Superset.”
- “Why are the Notion tools failing in this session?”
Requirements
- The superset CLI with at least one connected integration account
- Network access to Superset's API
- Pre-approved tools (allowed-tools): Bash(superset mcp:*), Bash(superset plugins:*), Bash(superset skills:*)
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- Find the integration
- List the tools before calling one
- Call it
What it can do on your machine
Read from SKILL.md and the folder at commit 5021353. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash(superset mcp:*)Bash(superset plugins:*)Bash(superset skills:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
jq
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
Superset Integration Tools loads about 1.6k tokens when it runs. Until then it costs about 106 tokens; SKILL.md has 791 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: warnings
The automated check found patterns that need a careful read before installing.
- WarningContains instruction-override wording (e.g. “without asking the user”)SKILL.md:74
do not tell the user the integration is unavailable. The same operations sit on the connected
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 791 words (~1,553 tokens).
“An integration is an installed plugin with a connected account. Its tools do not run here. superset mcp hands the call to Superset's API, which attaches the stored credential and forwards it to the plugin's MCP server. No token is…”
- name
- integrations
- allowed-tools
- Bash(superset mcp:*), Bash(superset plugins:*), Bash(superset skills:*)
- argument-hint
- what you want done in a connected service
Files
SKILL.md and 1 other file in plugins/superset/skills/integrations of superset-sh/superset.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 5021353
Compare with similar skills
Superset Integration Tools 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 |
|---|---|---|---|---|---|---|
| Superset Integration Tools this skillsuperset-sh/superset | 15k | — | ~1.6k | Automated safety check: Warn | Custom licence | |
| ComposioComposioHQ/composio | 30k | 1 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Ops Triagedavepoon/buildwithclaude | 3.6k | — | ~2k | Automated safety check: Notes | MIT | |
| Dev MCP Setupevolution-foundation/evo-nexus | 545 | — | ~615 | Automated safety check: Pass | Custom licence | |
| MCP ServersPostHog/code | 179 | — | ~1.9k | Automated safety check: Pass | MIT | |
| Adding MCP Store ServersPostHog/posthog | 40k | — | ~1.6k | Automated safety check: Pass | Custom licence |
Similar skills
Ops Triage
davepoon/buildwithclaude
Cross-platform issue triage. An agent skill from davepoon/buildwithclaude.
Dev MCP Setup
evolution-foundation/evo-nexus
Configure MCP servers for the workspace — web search, filesystem, GitHub, Stripe, etc.
- Official
MCP Servers
PostHog/code
Install, configure, authenticate, and troubleshoot MCP (Model Context Protocol) servers for this agent.
- Official
Adding MCP Store Servers
PostHog/posthog
Add a third-party MCP server (Linear, Notion, GitHub, ...) to the PostHog MCP store catalog.
Integrate MCP
davekilleen/Dex
Install and wire up an existing MCP server from Smithery.ai or a GitHub repo.
More from superset-sh/superset
All 47 skills in this repoMobile Demo Film Editor
superset-sh/superset
Edits real mobile screen recordings into a configurable demo video with phone framing, title cards, cutaways and an end card, using a bundled renderer.
Superset Agent Standup
superset-sh/superset
Sweeps every Superset workspace, task and agent terminal to report what finished, what needs review and what is blocked, read-only, and can publish the digest as a page.
Superset Browser Control
superset-sh/superset
Opens pages, takes screenshots, reads the console, clicks and types in the browser panes of a Superset workspace, with Browser Use as a fallback for other browsers.
Superset Automate
superset-sh/superset
Turns a recurring chore into a scheduled or event-triggered Superset agent, drafting its prompt, picking a target and trigger, and reviewing the first run.
Drizzle Migration Safety on Neon
superset-sh/superset
Generates a Drizzle migration on a fresh Neon branch and runs a production-safety checklist for table sizes, lock order and load rehearsal before the PR opens.
Superset Feedback Reporter
superset-sh/superset
Turns a bug report or feature request about Superset into a short, scannable write-up and submits it privately or as a public GitHub issue.
Related
Categories
Questions about Superset Integration Tools
What does Superset Integration Tools do?
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. An integration here means an installed plugin with a connected account, and this skill explains how to reach its tools through the superset command line. The agent runs superset plugins list and reads the STATUS column: a connected account can be called, needs connection means nobody has authorized an account yet, and not installed means the plugin is gone while its credential is still live.
When should I use Superset Integration Tools?
Superset Integration Tools fits situations like: creating or updating an issue in a connected service such as Linear; finding out which tools a connected integration exposes; working out why an integration's tools are failing; replacing mcp__linear__-style tools that another skill expects but are missing.
How do I install Superset Integration Tools in Claude Code?
Run `npx skills add superset-sh/superset --skill integrations -a claude-code`. Or copy the skill folder (plugins/superset/skills/integrations in superset-sh/superset) into .claude/skills/integrations in your project. Claude Code loads it when a task matches its description.
How do I install Superset Integration Tools in Codex?
Run `npx skills add superset-sh/superset --skill integrations -a codex`. Or copy the skill folder (plugins/superset/skills/integrations in superset-sh/superset) into .agents/skills/integrations in your project. Codex loads it when a task matches its description.
Can I use Superset Integration Tools 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 superset-sh/superset --skill integrations -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/integrations, .gemini/skills/integrations, .github/skills/integrations and .opencode/skills/integrations in your project.
What does Superset Integration Tools need to run?
Going by SKILL.md and its folder, Superset Integration Tools needs the command-line tools its instructions call (jq). Our summary lists: The superset CLI with at least one connected integration account; Network access to Superset's API. Its frontmatter pre-approves these tools: Bash(superset mcp:*), Bash(superset plugins:*), Bash(superset skills:*).
Does Superset Integration Tools 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 Superset Integration Tools safe to install?
Our automated static check of SKILL.md flagged 1 warning(s): contains instruction-override wording (e.g. “without asking the user”). Read the flagged lines before installing; the check is not a guarantee either way.
What licence does Superset Integration Tools use?
Superset Integration Tools has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Superset Integration Tools use?
About 1.6k tokens (SKILL.md is roughly 6.2k 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 Superset Integration Tools?
Skills that share tags, products or a category with Superset Integration Tools: Composio (ComposioHQ/composio, 30k stars), Ops Triage (davepoon/buildwithclaude, 3.6k stars), Dev MCP Setup (evolution-foundation/evo-nexus, 545 stars) and MCP Servers (PostHog/code, 179 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Superset Integration Tools?
superset-sh (a GitHub organization) maintains it in superset-sh/superset, which has 15,013 GitHub stars. The repository holds 47 skills in this directory. The repository was last updated on October 9, 2026.
Source: superset-sh/superset on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.