Install Superpowers for OpenCode

VerifiedCaution

Install and configure the Superpowers workflow system for OpenCode, including plugin setup and project-level templates.

Sby Skills Guide Bot
DevelopmentBeginner
8/1/2026
Claude CodeCodex
#opencode#plugin-install#workflow-setup#tdd#configuration

Recommended for

Automated summary

This skill documents how to install, configure, or uninstall the Superpowers workflow system for OpenCode as a plugin, with optional project-level templates.

Strengths

  • Installation boils down to a single `plugin` entry in `opencode.json`, easy to apply and verify
  • Also covers uninstall steps and cleanup of any added project files
  • Ships concrete templates (PROJECT_CONFIG.yaml, AGENTS.md) for project-level enforcement
  • Includes a simple verification prompt (“Tell me about your superpowers”)

Limitations

  • Does not explain what the individual Superpowers skills actually contain or how they behave
  • Assumes OpenCode is already set up and requires a local path to the repo for copying templates
  • No guidance on errors, plugin conflicts, or version pinning
When to use it

Use it when an OpenCode user wants to enable Superpowers or add project-scoped configuration and reminders.

When not to use it

Avoid it if you need guidance on day-to-day use of Superpowers skills or you are not running OpenCode.

Security analysis

Caution
Quality score82/100

The skill does not contain destructive, exfiltrating, obfuscated, or safety-disabling instructions. However, its main action is installing and running third-party code via a git-based OpenCode plugin, which is a legitimate but supply-chain-sensitive operation, so it warrants caution rather than a fully safe rating.

Findings
  • •Installs and executes a third-party OpenCode plugin from an external GitHub git URL; users should verify the upstream repository and author before installation.
  • •Includes shell copy commands with placeholder paths; these are not destructive but assume the user knows where the upstream templates are located.
How this analysis is made

Examples

Install the plugin
Install the Superpowers workflow plugin in my global opencode.json and tell me how to verify it worked.
Project-level setup
Add Superpowers project-level templates to this repo: create PROJECT_CONFIG.yaml for my stack and an AGENTS.md reminder.
Remove the plugin
Uninstall Superpowers from my OpenCode config and clean up the project files it added.

name: install-superpowers-for-opencode description: Use when installing, migrating, or configuring the Superpowers workflow for OpenCode, or when project-level workflow templates are needed alongside the plugin.

Install Superpowers for OpenCode

This skill installs the Superpowers workflow system for OpenCode. Superpowers enforces best practices such as TDD, systematic debugging, structured planning, and subagent-driven development.

Install

Add this plugin to opencode.json (global or project-level):

{
  "plugin": ["superpowers@git+https://github.com/awdemos/opencode-superpowers.git"]
}

Restart OpenCode. The plugin registers the Superpowers skills and injects a lean per-session bootstrap.

Verify by asking: "Tell me about your superpowers."

Optional: Project-Level Templates

To add a project config and a per-project reminder in addition to the plugin:

  1. Copy the config template and set your stack:

    cp /path/to/opencode-superpowers/templates/PROJECT_CONFIG.yaml your-project/PROJECT_CONFIG.yaml
    
  2. Copy the reminder into your project root:

    cp /path/to/opencode-superpowers/prompts/AGENTS.md.template your-project/AGENTS.md
    

    Then replace PROJECT_NAME with your project name.

Uninstall

Remove the plugin line from opencode.json and restart OpenCode. Also remove any project-level AGENTS.md files you added.

For AI Assistants

When this skill is invoked, install via the plugin. After installation, guide the user to invoke Superpowers skills via OpenCode's skill tool, and copy templates/PROJECT_CONFIG.yaml and prompts/AGENTS.md.template if they want project-level enforcement.


Skill Version: 3.0 | OpenCode plugin-first, compressed

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/install-superpowers-for-opencode-ms9wnz45/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/install-superpowers-for-opencode-ms9wnz45' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/install-superpowers-for-opencode-ms9wnz45/download' --output '.skill-downloads/install-superpowers-for-opencode-ms9wnz45/SKILL.md.part' && mv '.skill-downloads/install-superpowers-for-opencode-ms9wnz45/SKILL.md.part' '.skill-downloads/install-superpowers-for-opencode-ms9wnz45/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code
test -f '.skill-downloads/install-superpowers-for-opencode-ms9wnz45/SKILL.md' && test -s '.skill-downloads/install-superpowers-for-opencode-ms9wnz45/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/install-superpowers-for-opencode' && cp -R '.skill-downloads/install-superpowers-for-opencode-ms9wnz45' '.claude/skills/install-superpowers-for-opencode'

Codex
test -f '.skill-downloads/install-superpowers-for-opencode-ms9wnz45/SKILL.md' && test -s '.skill-downloads/install-superpowers-for-opencode-ms9wnz45/SKILL.md' && mkdir -p '.agents/skills' && test ! -e '.agents/skills/install-superpowers-for-opencode' && cp -R '.skill-downloads/install-superpowers-for-opencode-ms9wnz45' '.agents/skills/install-superpowers-for-opencode'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation
openskills install './.skill-downloads/install-superpowers-for-opencode-ms9wnz45'

openskills read 'install-superpowers-for-opencode-ms9wnz45'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/install-superpowers-for-opencode-ms9wnz45/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills