Agent skill

Superconductor

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

MITAuto-check passedDevelopment

Install Superconductor

skills CLI

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

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

GitHub CLI

$ gh skill install HazAT/pi-config superconductor --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/superconductor .claude/skills/superconductor && 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/

Paste into Claude Code

Install the "superconductor" agent skill from https://github.com/HazAT/pi-config/tree/main/skills/superconductor into .claude/skills/superconductor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superconductor", 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

$skill-installer install https://github.com/HazAT/pi-config/tree/main/skills/superconductor

Type 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.

skills CLI

$ npx skills add HazAT/pi-config --skill superconductor -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install HazAT/pi-config superconductor --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

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

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "superconductor" agent skill from https://github.com/HazAT/pi-config/tree/main/skills/superconductor into .agents/skills/superconductor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superconductor", 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.

skills CLI

$ npx skills add HazAT/pi-config --skill superconductor -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install HazAT/pi-config superconductor --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

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

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "superconductor" agent skill from https://github.com/HazAT/pi-config/tree/main/skills/superconductor into .cursor/skills/superconductor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superconductor", 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

$ gemini skills install https://github.com/HazAT/pi-config.git --path skills/superconductor

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add HazAT/pi-config --skill superconductor -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install HazAT/pi-config superconductor --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

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

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

Paste into Gemini CLI

Install the "superconductor" agent skill from https://github.com/HazAT/pi-config/tree/main/skills/superconductor into .gemini/skills/superconductor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superconductor", 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.

GitHub CLI

$ gh skill install HazAT/pi-config superconductor

Installs 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).

skills CLI

$ npx skills add HazAT/pi-config --skill superconductor -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

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

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

Paste into GitHub Copilot

Install the "superconductor" agent skill from https://github.com/HazAT/pi-config/tree/main/skills/superconductor into .github/skills/superconductor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superconductor", 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.

skills CLI

$ npx skills add HazAT/pi-config --skill superconductor -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install HazAT/pi-config superconductor --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

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

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "superconductor" agent skill from https://github.com/HazAT/pi-config/tree/main/skills/superconductor into .opencode/skills/superconductor/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "superconductor", 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: superconductor
GitHub stars: 451
Token cost: ~1.6k tokens
SKILL.md length: 653 words
Files: 3 (incl. references)
Skills in repo: 10
Repo updated: Aug 25, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

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

A workflow explicitly calls for SC orchestration
SKILL.md covers Boundaries, Live Preflight, Individual Pi Worker and Independent Teams, plus 3 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
App-managed UI/session behavior

What it does

Superconductor is an agent skill from HazAT/pi-config. Operates the super.engineering/Superconductor sc CLI for app-managed agents, teams, sessions, layouts, worktrees, and review threads. Use when a workflow explicitly calls for SC orchestration or app-managed UI/session behavior.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/orchestration.md` and `references/worktrees-and-reviews.md`). Compatibility notes: Requires the super.engineering/Superconductor app and the sc CLI. Some operations require Experimental Agent orchestration.

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

A workflow explicitly calls for SC orchestration
App-managed UI/session behavior

Example prompts

“Use the superconductor skill to operate the super.engineering/Superconductor sc CLI for app-managed agents, teams, sessions, layouts, worktrees, and…”
“/superconductor”

Requirements

Compatibility (from SKILL.md): Requires the super.engineering/Superconductor app and the `sc` CLI. Some operations require Experimental Agent orchestration.

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
No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).
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.
Compatibility
Requires the super.engineering/Superconductor app and the `sc` CLI. Some operations require Experimental Agent orchestration.
From compatibility in the SKILL.md frontmatter.

Context cost

Superconductor loads about 1.6k tokens when it runs, and up to ~4.4k if it reads all its reference files. Until then it costs about 61 tokens; SKILL.md has 653 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~61
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~4.4k

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). 653 words, ~1,593 tokens.

Download SKILL.mdSave it as .claude/skills/superconductor/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: superconductor
description: Operates the super.engineering/Superconductor `sc` CLI for app-managed agents, teams, sessions, layouts, worktrees, and review threads. Use when a workflow explicitly calls for SC orchestration or app-managed UI/session behavior.
compatibility: Requires the super.engineering/Superconductor app and the `sc` CLI. Some operations require Experimental Agent orchestration.

Superconductor CLI

Use live sc instructions and capability output as authoritative. Keep SC syntax and lifecycle policy here; role skills should reference this skill rather than reproduce commands.

Boundaries

Use SC only for the requested orchestration or app-managed outcome.
Require explicit human intent for worktree/branch creation or deletion, target-branch changes, force termination, destructive cleanup, closing/rearranging existing sessions, and unrelated review-thread mutations.
Never create a worktree merely for delegation or launch replacement agents for follow-ups.
Prefer stable labels or stable target IDs and --active keep.
Dispatch and idle state are not completion; always wait, read, and verify.

Live Preflight

Before the first mutation, run the matching guide:

Area	Command
Agents, teams, delegation	`sc instructions orchestration`
Tabs, panes, views	`sc instructions layout`
Worktrees or branches	`sc instructions worktree`
In-app review threads	`sc instructions review`

For orchestration, inspect current capabilities and targets:

bash

command -v sc
sc layout capabilities --output json
sc layout views --worktree "$PWD" --output json
sc agents list --worktree "$PWD" --output json
sc chat providers --json

Verify the launch shape, provider, UI mode, model, reasoning level, and structured-read support before specifying them. If unavailable, report the exact limitation instead of silently substituting another mechanism.

Read references/orchestration.md before launching or controlling sessions. Read references/worktrees-and-reviews.md before requested worktree or review-thread operations.

Individual Pi Worker

Delegated Pi sessions default to terminal mode. Long prompts should use a temporary JSONL launch input built with jq; it is command input, not durable workflow state, and must be removed after launch.

bash

sc layout run tabs \
  --provider pi --ui terminal \
  --label worker-TODO-001 \
  --prompt 'Complete prompt with task and absolute handover paths.' \
  --worktree "$PWD" --active keep --output json

Capture the returned label/stable target. Then collect that same target:

bash

sc agent wait --to label:worker-TODO-001 --idle --timeout-ms 120000 \
  --worktree "$PWD" --output json
sc agent read --to label:worker-TODO-001 --last 40 \
  --worktree "$PWD" --output json

Check reads for target/provider errors, incomplete output, and the evidence required by the prompt. Verify source-writing results independently with Git and tests. Run shared-checkout source writers sequentially.

Use sc agent send for clarification in the existing session. If a turn must be redirected, interrupt then send. Do not infer success from launch, queue admission, or idle state.

Independent Teams

Use sc team run only for genuinely independent fan-out whose roles do not require per-role UI or model overrides:

bash

sc team run \
  --label correctness --provider pi --prompt 'Independent read-only review prompt.' \
  --label regressions --provider pi --prompt 'Independent read-only review prompt.' \
  --worktree "$PWD" --output json

sc team run currently has no per-role --ui, --model, or --reasoning flags. When an ensemble requires distinct Pi models or Pi Chat UI, launch individually labeled sessions with sc layout run tabs, wait/read their stable targets, and fan their reports into the designated lead session. Do not claim those sessions are an SC team run or instruct them to call sc team report.

Every team prompt must include its task, absolute handover paths, read/write limits, and this completion contract:

bash

sc team report --run RUN_ID --role ROLE --status done \
  --summary 'Concise evidence-based report.' --worktree "$PWD" --output json

Use --result-file only when a detailed report exceeds the summary limit; do not use it for the session-file workflow. In a synchronous workflow, capture the returned stable role targets, wait for them, then collect the durable reports with sc team status. Once every role is Reported, use those report summaries directly; call sc agent read only for a missing, failed, or malformed report.

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

Do not pass --notify self when the coordinator waits synchronously. That option inserts the team synthesis into the creator's editor as a follow-up prompt and may require the user to submit it. Use it only for an explicitly asynchronous workflow, end the coordinator turn after launch, and explain that behavior to the user. Never combine it with manual wait/status collection. Team launch provides parallelism, not sequencing.

Session-File Handover

For /plan, /todos, /execute, and /review:

A coordinator session file is required: PI_SESSION_FILE in Pi, or $HOME/.claude/projects/<project slug>/$CLAUDE_CODE_SESSION_ID.jsonl in Claude Code (slug = the project directory path with / and . mapped to -).
Durable handover files are exactly ${SESSION_FILE%.jsonl}.plan.md, ${SESSION_FILE%.jsonl}.todos.md, and ${SESSION_FILE%.jsonl}.review.md.
/review may use the session JSONL and Git state without plan or todos files; include either handover when it exists.
The coordinator alone writes these files.
Delegated prompts receive the resolved absolute paths and read them directly.
Do not create sidecar directories, repository run stores, membership records, coordination-state mirrors, or custom JSONL state.

Managed Terminal Title

In a managed Pi terminal:

bash

sc tab title "$TITLE" --to "id:terminal:$SUPERCONDUCTOR_TERMINAL_ID" --json

Verify response.new_title. Do not omit the stable target.

Cleanup

Do not stop agents, close tabs/views, delete groups, or remove other managed state unless the human requested cleanup. Inspect exact targets and current help before any such operation.

Files

SKILL.md and 2 other files (references) in skills/superconductor of HazAT/pi-config.

SKILL.md
references/orchestration.md
references/worktrees-and-reviews.md

Open the folder on GitHubat commit 655acd4

Compare with similar skills

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

Superconductor compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Superconductor this skillHazAT/pi-config	451	—	~1.6k	Automated safety check: Pass	MIT	1 mo ago
Finishing a Development Branchobra/superpowers	297k	5 repos	~1.9k	Automated safety check: Pass	MIT	today
Migrate Core Code to Submodulestinyhumansai/openhuman	42k	—	~2.6k	Automated safety check: Pass	GPL-3.0	today
Finishing A Development Branchfarm-fe/farm	5.6k	34 repos	~1.8k	Automated safety check: Pass	MIT	17 days ago
Git Worktree Cleanuplobehub/lobehub	83k	—	~2.8k	Automated safety check: Pass	Custom licence	today
Keep Codex Fastvibeforge1111/keep-codex-fast	1.6k	—	~3.1k	Automated safety check: Pass	MIT	5 mo ago

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.
297k 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 2 days ago
DevelopmentAuto-check passed

Questions about Superconductor

What does Superconductor do?

Operates the super.engineering/Superconductor sc CLI for app-managed agents, teams, sessions, layouts, worktrees, and review threads. Superconductor is an agent skill from HazAT/pi-config.engineering/Superconductor sc CLI for app-managed agents, teams, sessions, layouts, worktrees, and review threads.

When should I use Superconductor?

Superconductor fits situations like: A workflow explicitly calls for SC orchestration; app-managed UI/session behavior.

How do I install Superconductor in Claude Code?

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

How do I install Superconductor in Codex?

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

Can I use Superconductor 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 superconductor -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/superconductor, .gemini/skills/superconductor, .github/skills/superconductor and .opencode/skills/superconductor in your project.

What does Superconductor need to run?

SKILL.md names no scripts, command-line tools or credentials: Superconductor is instructions for the agent only. Compatibility (from SKILL.md): Requires the super.engineering/Superconductor app and the `sc` CLI. Some operations require Experimental Agent orchestration..

Does Superconductor 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 Superconductor 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 Superconductor use?

Superconductor 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 Superconductor use?

About 1.6k tokens (SKILL.md is roughly 6.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 2.8k tokens, read only when the agent opens those files.

What are the alternatives to Superconductor?

Skills that share tags, products or a category with Superconductor: Finishing a Development Branch (obra/superpowers, 297k 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 Superconductor?

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.

Install Superconductor

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Compatibility

Context cost

Safety

SKILL.md

Superconductor CLI

Boundaries

Live Preflight

Individual Pi Worker

Independent Teams

Session-File Handover

Managed Terminal Title

Cleanup

Files

Compare with similar skills

Similar skills

More from HazAT/pi-config

Related

Questions about Superconductor