New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Setup Superconductor Project

by HazAT in HazAT/pi-config

Configures a repository for super.engineering with repo-owned worktree setup and development-server scripts.

MITAuto-check passedDevelopment

Install Setup Superconductor Project

skills CLI
$ npx skills add HazAT/pi-config --skill setup-superconductor-project -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install HazAT/pi-config setup-superconductor-project --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/HazAT/pi-config.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/setup-superconductor-project .claude/skills/setup-superconductor-project && rm -rf skills-src

Use ~/.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/

Facts

Skill name
setup-superconductor-project
GitHub stars
451
Token cost
~999 tokens
SKILL.md length
409 words
Files
1
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Configures a repository for super.engineering with repo-owned worktree setup and development-server scripts.

  • Works in 5 steps: Load Live Guidance → Derive Commands from Repository Evidence → Write Repo-Owned Configuration → …
  • Asked to make this project Superconductor ready
  • SKILL.md covers Step 1: Load Live Guidance, Step 2: Derive Commands from…, Step 3: Write Repo-Owned… and Step 4: Verify, plus 1 more section
  • Calls git, pnpm and npm

What it does

Setup Superconductor Project is an agent skill from HazAT/pi-config. Configures a repository for super.engineering with repo-owned worktree setup and development-server scripts. Use when asked to "make this project Superconductor ready", "set up super.engineering", "add worktree setup", or "configure the dev server".

Its SKILL.md is about 1000 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires the super.engineering app and sc CLI.

It sits in Development, covering Git worktrees. The repository describes itself as: My personal pi coding agent configuration - skills and extensions. The licence is MIT.

When your agent uses it

  • Asked to make this project Superconductor ready
  • Set up super.engineering
  • Add worktree setup
  • Configure the dev server

Example prompts

  • “make this project Superconductor ready”
  • “set up super.engineering”
  • “add worktree setup”
  • “/setup-superconductor-project”

Requirements

  • Compatibility (from SKILL.md): Requires the super.engineering app and `sc` CLI.

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Load Live Guidance
  2. Derive Commands from Repository Evidence
  3. Write Repo-Owned Configuration
  4. Verify
  5. Report

What it can do on your machine

Read from SKILL.md and the folder at commit 655acd4. 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

    Shell commands in SKILL.md call:

    • git
    • pnpm
    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, pnpm and npm, which can reach the network depending on how they are called.

    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.

  • Compatibility

    Requires the super.engineering app and `sc` CLI.

    From compatibility in the SKILL.md frontmatter.

Context cost

Setup Superconductor Project loads about 999 tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 409 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~70
When it runs · the whole SKILL.md, loaded when a task matches
~999

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 HazAT/pi-config at commit 655acd4, republished under its MIT licence (© HazAT). 409 words, ~999 tokens.

Download SKILL.mdSave it as .claude/skills/setup-superconductor-project/SKILL.md (or your agent's skills folder).
name
setup-superconductor-project
description
Configures a repository for super.engineering with repo-owned worktree setup and development-server scripts. Use when asked to "make this project Superconductor ready", "set up super.engineering", "add worktree setup", or "configure the dev server".
compatibility
Requires the super.engineering app and `sc` CLI.

Set Up a Superconductor Project

Configure the current repository's .superconductor/config.json through the supported sc project scripts interface. Do not create a worktree, commit, push, or open a browser unless separately requested.

Step 1: Load Live Guidance

  1. Read ~/.pi/agent/skills/superconductor/SKILL.md.
  2. Run sc instructions project and sc project scripts --help before mutation.
  3. Inspect current state:
bash
sc project scripts --json
sc project scripts check --json
sc worktree status --json
git status --short --branch

Treat live instructions and current help as authoritative.

Step 2: Derive Commands from Repository Evidence

Read repository instruction files, the existing .superconductor/config.json when present, root manifests, lockfiles, workspace configuration, and package scripts.

Choose commands only when repository evidence supports them:

  • Derive setup from the committed package-manager lockfile, such as pnpm install --frozen-lockfile or npm ci.
  • Prefer an existing dev or start script for the default run target.
  • Inspect the framework CLI help before adding host, port, or forwarding arguments. Do not guess flag syntax.
  • For a browser-facing development server, configure an IPv4-reachable bind address when the framework supports it; verify the exact invocation. For example, Astro accepts pnpm run dev --host 0.0.0.0, while other frameworks differ.
  • Preserve an existing valid setup or run command unless evidence shows it is wrong.
  • Ask one focused question when the package manager, run script, or intended service is ambiguous.

Do not invent teardown, stop, or cleanup commands. Add them only when the repository already defines the required lifecycle behavior.

Show full SKILL.md (189 more words)Show less

Step 3: Write Repo-Owned Configuration

Use repo scope so managed worktrees inherit the configuration. Use sc, not direct JSON replacement, because it preserves unknown fields and validates atomically.

bash
sc project scripts set setup "<verified setup command>" --scope repo --json
sc project scripts set run devserver --default "<verified run command>" --scope repo --json

If no setup command is needed, do not add an empty one. If the repository already has multiple named run targets, preserve them and choose a descriptive name for the new target rather than replacing unrelated entries.

Step 4: Verify

  1. Validate the resulting config:
bash
sc project scripts check --json
  1. Run the setup command once when it is safe and non-destructive.
  2. Start the configured target through sc project scripts run <name> --json.
  3. Confirm sc project scripts status --json reports it running.
  4. When the service exposes HTTP and its port is known from evidence, request its IPv4 loopback URL and require a successful response.
  5. Stop the target after verification unless the user asked to leave it running, then verify it is idle.
  6. Inspect .superconductor/config.json, git diff, and git status --short.

A successful process launch without a reachable service is not sufficient verification for a browser-facing app.

Step 5: Report

Report:

markdown
Configured `.superconductor/config.json`:
- Setup: `<command>` or none
- Default run target: `<name>` — `<command>`

Verification:
- Config validation — pass/fail
- Setup — pass/skipped with reason
- Runtime state — running/failed
- Service check — URL and result, or not applicable
- Final runtime state — idle or intentionally left running

Files changed:
- `.superconductor/config.json`

Leave the configuration uncommitted unless the user separately requests a commit.

© HazAT, MIT. 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 skills/setup-superconductor-project of HazAT/pi-config.

Open the folder on GitHubat commit 655acd4

Compare with similar skills

Setup Superconductor Project 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.

Setup Superconductor Project compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Setup Superconductor Project this skillHazAT/pi-config451—~999Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Migrate Core Code to Submodulestinyhumansai/openhuman42k—~2.6kAutomated safety check: PassGPL-3.0
Finishing A Development Branchfarm-fe/farm5.6k34 repos~1.8kAutomated safety check: PassMIT
Git Worktree Cleanuplobehub/lobehub83k—~2.8kAutomated safety check: PassCustom licence
Keep Codex Fastvibeforge1111/keep-codex-fast1.6k—~3.1kAutomated safety check: PassMIT

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Migrate Core Code to Submodules

    tinyhumansai/openhuman

    Plans and carries out moving non-host-specific code and its tests from the OpenHuman core into vendored tiny submodule libraries, then releases the submodule and re-pins the host.

    42k GitHub stars~2.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Finishing A Development Branch

    farm-fe/farm

    A skill your agent uses when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for…

    5.6k GitHub starsUsed in 34 repos~1.8k tokens
    DevelopmentAuto-check passed

  • Git Worktree Cleanup

    lobehub/lobehub

    Audits stale Git worktrees and branches with a bundled script, classifies each one, and deletes only after you approve the exact candidates.

    83k GitHub stars~2.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Keep Codex Fast

    vibeforge1111/keep-codex-fast

    A skill your agent uses when Codex feels slow or bloated, when local sessions/logs/worktrees/config have grown over time, or when a user wants safe maintenance for Codex Desktop/CLI state.

    1.6k GitHub stars~3.1k tokensUpdated 5 mo ago
    DevelopmentAuto-check passed

  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from HazAT/pi-config

All 10 skills in this repo

  • Session Reader

    HazAT/pi-config

    Efficiently read and analyze pi agent session JSONL files. An agent skill from HazAT/pi-config.

    451 GitHub stars~808 tokensUpdated 1 mo ago
    Auto-check passed

  • Pi Extension Development

    HazAT/pi-config

    Defines the local standard for standalone Pi extension repositories.

    451 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed

  • Superconductor

    HazAT/pi-config

    Operates the super.engineering/Superconductor sc CLI for app-managed agents, teams, sessions, layouts, worktrees, and review threads.

    451 GitHub stars~1.6k tokensUpdated 1 mo ago
    Auto-check passed

  • Plan

    HazAT/pi-config

    Interactively investigate a request, compare approaches, and write the selected implementation plan to a supplied Markdown path.

    451 GitHub stars~528 tokensUpdated 1 mo ago
    Auto-check passed

  • Review

    HazAT/pi-config

    Coordinate a model-diverse local code review, automatically repair actionable findings with sequential workers, and re-review to a final verdict.

    451 GitHub stars~2.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Worker

    HazAT/pi-config

    Implement one todo or review-fix task supplied by a coordinator, verify it, create one focused commit, and report evidence through the current Superconductor session.

    451 GitHub stars~679 tokensUpdated 1 mo ago
    Auto-check passed

Categories

Questions about Setup Superconductor Project

What does Setup Superconductor Project do?

Configures a repository for super.engineering with repo-owned worktree setup and development-server scripts. Setup Superconductor Project is an agent skill from HazAT/pi-config.engineering with repo-owned worktree setup and development-server scripts.

When should I use Setup Superconductor Project?

Setup Superconductor Project fits situations like: asked to make this project Superconductor ready; set up super.engineering; add worktree setup; configure the dev server.

How do I install Setup Superconductor Project in Claude Code?

Run `npx skills add HazAT/pi-config --skill setup-superconductor-project -a claude-code`. Or copy the skill folder (skills/setup-superconductor-project in HazAT/pi-config) into .claude/skills/setup-superconductor-project in your project. Claude Code loads it when a task matches its description.

How do I install Setup Superconductor Project in Codex?

Run `npx skills add HazAT/pi-config --skill setup-superconductor-project -a codex`. Or copy the skill folder (skills/setup-superconductor-project in HazAT/pi-config) into .agents/skills/setup-superconductor-project in your project. Codex loads it when a task matches its description.

Can I use Setup Superconductor Project 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 HazAT/pi-config --skill setup-superconductor-project -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-superconductor-project, .gemini/skills/setup-superconductor-project, .github/skills/setup-superconductor-project and .opencode/skills/setup-superconductor-project in your project.

What does Setup Superconductor Project need to run?

Going by SKILL.md and its folder, Setup Superconductor Project needs the command-line tools its instructions call (git, pnpm and npm). Compatibility (from SKILL.md): Requires the super.engineering app and `sc` CLI..

Does Setup Superconductor Project access the network?

SKILL.md contains no URLs. Its commands use git and npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Setup Superconductor Project 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 Setup Superconductor Project use?

Setup Superconductor Project is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Setup Superconductor Project use?

About 999 tokens (SKILL.md is roughly 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 Setup Superconductor Project?

Skills that share tags, products or a category with Setup Superconductor Project: Finishing a Development Branch (obra/superpowers, 296k stars), Migrate Core Code to Submodules (tinyhumansai/openhuman, 42k stars), Finishing A Development Branch (farm-fe/farm, 5.6k stars) and Git Worktree Cleanup (lobehub/lobehub, 83k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Setup Superconductor Project?

HazAT (a GitHub user) maintains it in HazAT/pi-config, which has 451 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on August 25, 2026.

Source: HazAT/pi-config on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.