Build Px4 macOS
PX4/PX4-Autopilot
Build PX4 board firmware on macOS in the px4-dev Docker container, including git worktrees, and stage commit-labeled artifacts without flashing hardware.
Makes a repository Superset-ready by writing .superset/config.json with setup, teardown and run scripts, then proving it with a real throwaway workspace.
Install Superset Project Setup
$ npx skills add superset-sh/superset --skill setup -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install superset-sh/superset 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/superset-sh/superset.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/superset/skills/setup .claude/skills/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 "setup" agent skill from https://github.com/superset-sh/superset/tree/main/plugins/superset/skills/setup into .claude/skills/setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/superset-sh/superset/tree/main/plugins/superset/skills/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 superset-sh/superset --skill setup -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install superset-sh/superset setup --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/setup .agents/skills/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 "setup" agent skill from https://github.com/superset-sh/superset/tree/main/plugins/superset/skills/setup into .agents/skills/setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 superset-sh/superset --skill setup -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install superset-sh/superset setup --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/setup .cursor/skills/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 "setup" agent skill from https://github.com/superset-sh/superset/tree/main/plugins/superset/skills/setup into .cursor/skills/setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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/superset-sh/superset.git --path plugins/superset/skills/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 superset-sh/superset --skill setup -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install superset-sh/superset setup --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/setup .gemini/skills/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 "setup" agent skill from https://github.com/superset-sh/superset/tree/main/plugins/superset/skills/setup into .gemini/skills/setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 superset-sh/superset 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 superset-sh/superset --skill setup -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/setup .github/skills/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 "setup" agent skill from https://github.com/superset-sh/superset/tree/main/plugins/superset/skills/setup into .github/skills/setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 superset-sh/superset --skill 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 superset-sh/superset setup --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/setup .opencode/skills/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 "setup" agent skill from https://github.com/superset-sh/superset/tree/main/plugins/superset/skills/setup into .opencode/skills/setup/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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
setup- GitHub stars
- 15k
- Token cost
- ~577 tokens
- SKILL.md length
- 230 words
- Files
- 2
- Skills in repo
- 47
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Makes a repository Superset-ready by writing .superset/config.json with setup, teardown and run scripts, then proving it with a real throwaway workspace.
- Works in 3 steps: Inspect the repo → Author .superset/config.json → Verify for real
- Preparing a repo so new Superset workspaces boot configured
- SKILL.md covers 1. Inspect the repo, 2. Author .superset/config.json and 3. Verify for real
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
The goal is that every new workspace, an isolated git worktree, comes up with dependencies installed, env files present and services reachable without manual steps. The agent inspects the repo first: the package manager and install command, which lockfiles reveal (bun, pnpm, yarn, npm, cargo, uv), env files, which are usually gitignored and so must be copied from the main checkout or generated from `.env.example`, services such as docker-compose and databases with their dev command and ports, and monorepo layout.
It then writes `.superset/config.json`, the file that wires in lifecycle scripts; a bare `setup.sh` is not picked up. Setup, teardown and run are arrays of shell commands executed in the worktree. Setup should be idempotent and fast, secrets are copied at setup time and never committed, and an individual user can extend scripts through a gitignored `config.local.json`. You approve the proposed files before writing, and the job is finished only when `superset workspaces create` yields a test workspace whose setup terminal completes cleanly, after which it is deleted.
When your agent uses it
- Preparing a repo so new Superset workspaces boot configured
- Fixing new workspaces that lack node_modules
- Fixing a missing .env or a setup script that never runs in workspaces
Example prompts
- “Set up this repo for Superset so new workspaces install dependencies and copy my .env.”
- “My setup script isn't running in new workspaces, so find out why.”
- “Add a teardown script that stops the docker-compose services when a workspace is deleted.”
Requirements
- The Superset CLI
- A repository with an install command and env files
- Pre-approved tools (allowed-tools): Bash(superset:*)
Workflow steps
3 steps, taken from the step headings in SKILL.md.
- Inspect the repo
- Author .superset/config.json
- Verify for real
What it can do on your machine
Read from SKILL.md and the folder at commit 2e47842. 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:*)
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
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 Project Setup loads about 577 tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 230 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: notes
The automated check noted patterns worth knowing about, such as sudo or a known installer.
- NoteMentions a .env fileSKILL.md:3
workspaces don't have node_modules", "my .env is missing in workspaces", "setup script isn't running"). - NoteMentions a .env fileSKILL.md:17
- Env files: `.env` is usually gitignored, so new worktrees need it copied from the main checkout or generated from `.en
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 230 words (~577 tokens).
“Goal: every new workspace (isolated git worktree) for this repo comes up ready, with dependencies installed, env present, and services reachable, without manual steps.”
- name
- setup
- allowed-tools
- Bash(superset:*)
- argument-hint
- optional notes about the project's setup needs
Files
SKILL.md and 1 other file in plugins/superset/skills/setup of superset-sh/superset.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit 2e47842
Compare with similar skills
Superset Project 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 |
|---|---|---|---|---|---|---|
| Superset Project Setup this skillsuperset-sh/superset | 15k | — | ~577 | Automated safety check: Notes | Custom licence | |
| Build Px4 macOSPX4/PX4-Autopilot | 13k | — | ~1.1k | Automated safety check: Pass | BSD-3-Clause | |
| Tnr Dev Serverstudie-tech/TheNinjaRPG | 104 | — | ~2.5k | Automated safety check: Notes | None | |
| Dx Harnesspproenca/dot-skills | 215 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Polyphonyalinaqi/maggy | 707 | — | ~980 | Automated safety check: Pass | MIT | |
| Git Worktree Managerborghei/Claude-Skills | 881 | — | ~1.6k | Automated safety check: Notes | MIT |
Similar skills
Tnr Dev Server
studie-tech/TheNinjaRPG
Run a TheNinjaRPG dev server locally from any git worktree, provision disposable test users, and call tRPC endpoints as those users.
Dx Harness
pproenca/dot-skills
Developer-experience friction auditing and fixing — slow onboarding, repeated manual setup steps, missing bootstrap/reset/seed scripts, undiscoverable conventions.
Polyphony
alinaqi/maggy
Multi-agent orchestration with container-isolated workspaces — each agent session runs in its own Docker container with independent git branches
Git Worktree Manager
borghei/Claude-Skills
Manage parallel development with Git worktrees: creation with port allocation, environment sync, branch isolation, and cleanup.
Subwave Worktree Dev
perminder-klair/subwave
Stage a SUB/WAVE git worktree so the dev stack can run from it, then start it.
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 Project Setup
What does Superset Project Setup do?
Makes a repository Superset-ready by writing .superset/config.json with setup, teardown and run scripts, then proving it with a real throwaway workspace. The goal is that every new workspace, an isolated git worktree, comes up with dependencies installed, env files present and services reachable without manual steps.example`, services such as docker-compose and databases with their dev command and ports, and monorepo layout.
When should I use Superset Project Setup?
Superset Project Setup fits situations like: preparing a repo so new Superset workspaces boot configured; fixing new workspaces that lack node_modules; fixing a missing .env or a setup script that never runs in workspaces.
How do I install Superset Project Setup in Claude Code?
Run `npx skills add superset-sh/superset --skill setup -a claude-code`. Or copy the skill folder (plugins/superset/skills/setup in superset-sh/superset) into .claude/skills/setup in your project. Claude Code loads it when a task matches its description.
How do I install Superset Project Setup in Codex?
Run `npx skills add superset-sh/superset --skill setup -a codex`. Or copy the skill folder (plugins/superset/skills/setup in superset-sh/superset) into .agents/skills/setup in your project. Codex loads it when a task matches its description.
Can I use Superset Project 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 superset-sh/superset --skill 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/setup, .gemini/skills/setup, .github/skills/setup and .opencode/skills/setup in your project.
What does Superset Project Setup need to run?
SKILL.md names no scripts, command-line tools or credentials: Superset Project Setup is instructions for the agent only. Our summary lists: The Superset CLI; A repository with an install command and env files. Its frontmatter pre-approves these tools: Bash(superset:*).
Does Superset Project 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 Superset Project Setup safe to install?
Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.
What licence does Superset Project Setup use?
Superset Project Setup 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 Project Setup use?
About 577 tokens (SKILL.md is roughly 2.3k 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 Project Setup?
Skills that share tags, products or a category with Superset Project Setup: Build Px4 macOS (PX4/PX4-Autopilot, 13k stars), Tnr Dev Server (studie-tech/TheNinjaRPG, 104 stars), Dx Harness (pproenca/dot-skills, 215 stars) and Polyphony (alinaqi/maggy, 707 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Superset Project Setup?
superset-sh (a GitHub organization) maintains it in superset-sh/superset, which has 14,974 GitHub stars. The repository holds 47 skills in this directory. The repository was last updated on October 8, 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.