How do I install the Superset Contribute skill?

Run npx skillmds@latest add superset-sh/superset-contribute in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Superset Contribute safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Superset Contribute?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Superset Contribute free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Superset Contribute?

superset-sh (@superset-sh) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Superset Contribute by superset-sh — Agent Skill

Name: Superset Contribute
Author: superset-sh

Superset Contribute

Set up a Superset open-source contribution — fork and clone superset-sh/superset, run local dev setup, and follow the repo's contribution rules through to a merge-ready PR. Use when the user wants to contribute to Superset, fix a Superset bug themselves, or prepare a PR against superset-sh/superset.

superset-sh Updated Sep 17, 2026

File contents

Contribute to Superset

Take the user from "I want to fix/build X in Superset" to a merge-ready PR that follows the repo's rules. If the checked-out repo has CONTRIBUTING.md / DEVELOPMENT.md / AGENTS.md, those files are authoritative — read them and prefer them over this summary.

1. Scope first

Bug fixes, docs, small improvements → straight to a PR, no issue needed
New features or larger changes → open an issue first at https://github.com/superset-sh/superset/issues/new/choose to agree on the approach before building
Questions → Superset Discord, not an issue

2. Set up

gh auth status, then fork and clone: gh repo fork superset-sh/superset --clone (or add a fork remote to an existing clone)
Best experience: add the clone as a project in the Superset app and create a workspace per change — contributions develop inside managed worktrees
In the new workspace/worktree, run ./.superset/setup.local.sh once (configures per-workspace ports, app identity, local services, and a seeded dev account — no external credentials needed), then bun run dev
Bun only — never npm/yarn/pnpm. Read the root AGENTS.md and follow it.

3. Make it merge-ready

Branch from main; one change per PR — unrelated finds become a second PR
Before pushing: bun run lint:fix, then verify bun run lint exits clean (CI fails on warnings too), bun run typecheck, bun run test
PR title must be a conventional commit (feat(desktop): ..., fix(web): ...) — PRs are squash-merged with the title as the commit subject
Include proof it works: screenshots or recordings for anything user-visible, before/after for fixes. The dev desktop app exposes CDP for clean captures — see "Capturing screenshots via CDP" in CONTRIBUTING.md
Check "Allow edits from maintainers" and link the issue for non-trivial changes

4. Open it

gh pr create against superset-sh/superset main, fill in the PR template honestly (what you ran, what you clicked, what's covered by tests), and report the PR URL back to the user.

---name: superset-contributedescription: Set up a Superset open-source contribution — fork and clone superset-sh/superset, run local dev setup, and follow the repo's contribution rules through to a merge-ready PR. Use when the user wants to contribute to Superset, fix a Superset bug themselves, or prepare a PR against superset-sh/superset.---# Contribute to SupersetTake the user from "I want to fix/build X in Superset" to a merge-ready PR that follows the repo's rules. If the checked-out repo has `CONTRIBUTING.md` / `DEVELOPMENT.md` / `AGENTS.md`, those files are authoritative — read them and prefer them over this summary.## 1. Scope first- Bug fixes, docs, small improvements → straight to a PR, no issue needed- New features or larger changes → open an issue first at https://github.com/superset-sh/superset/issues/new/choose to agree on the approach before building- Questions → Superset Discord, not an issue## 2. Set up1. `gh auth status`, then fork and clone: `gh repo fork superset-sh/superset --clone` (or add a fork remote to an existing clone)2. Best experience: add the clone as a project in the Superset app and create a workspace per change — contributions develop inside managed worktrees3. In the new workspace/worktree, run `./.superset/setup.local.sh` once (configures per-workspace ports, app identity, local services, and a seeded dev account — no external credentials needed), then `bun run dev`4. Bun only — never npm/yarn/pnpm. Read the root `AGENTS.md` and follow it.## 3. Make it merge-ready- Branch from `main`; **one change per PR** — unrelated finds become a second PR- Before pushing: `bun run lint:fix`, then verify `bun run lint` exits clean (CI fails on warnings too), `bun run typecheck`, `bun run test`- PR title must be a conventional commit (`feat(desktop): ...`, `fix(web): ...`) — PRs are squash-merged with the title as the commit subject- Include proof it works: screenshots or recordings for anything user-visible, before/after for fixes. The dev desktop app exposes CDP for clean captures — see "Capturing screenshots via CDP" in CONTRIBUTING.md- Check "Allow edits from maintainers" and link the issue for non-trivial changes## 4. Open it`gh pr create` against `superset-sh/superset` `main`, fill in the PR template honestly (what you ran, what you clicked, what's covered by tests), and report the PR URL back to the user.

Frequently asked questions