Superpowers Sync Upstream logo

Superpowers Sync Upstream

Community
christopherarter
superpowers-sync-upstream

Sync this port with upstream obra/superpowers or Reasonix main-v2: detect drift, re-port, bench-gate

Overview

Publisherchristopherarter
Repositorysuperpowers-reasonix
Skill namesuperpowers-sync-upstream
Stars
101
Forks
7
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by christopherarter on GitHub. Read the source before you install it.

Installation

Install the Superpowers Sync Upstream AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/christopherarter/superpowers-reasonix/tree/main/skills/superpowers-sync-upstream
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/christopherarter/superpowers-reasonix.git /tmp/superpowers-reasonix
mkdir -p .claude/skills
cp -r /tmp/superpowers-reasonix/skills/superpowers-sync-upstream .claude/skills/superpowers-sync-upstream
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Superpowers Sync Upstream in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Superpowers Sync Upstream on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Superpowers Sync Upstream is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Sync Upstream

Re-aligns this port with its two upstreams and re-pins UPSTREAM.json. Run when asked to sync or update from upstream, or after the upstream-drift CI issue fires.

1. Detect

Read UPSTREAM.json for the pinned commits and watched paths, then see what moved:

Do not run .github/scripts/check-upstream-drift.mjs for a read-only check: it can create or update the tracking issue. Inspect the pinned SHAs with git ls-remote or gh api repos/<owner>/<repo>/commits/<branch>, then compare the two endpoints with Git. Use the issue-writing script only when updating the tracker is intended.

For full diffs, shallow-fetch and compare from the pins:

Fetch both the pinned commit and current default-branch head into a temporary blobless clone, then run git diff --no-renames <pin> <head> -- skills/. A GitHub compare API response with 300 files may be truncated; do not treat it as complete.

For Reasonix, diff the pin against main-v2 over internal/tool internal/hook internal/skill internal/frontmatter internal/command. Inspect actual tool registration and implementation together; a declared identity alone does not prove a callable tool exists.

Network blocked? web_fetch the GitHub compare page: <repo>/compare/<pinned>...<branch>, and label incomplete file lists. This step is read-only; dispatch it to a task subagent when appropriate and keep only the drift report to save context.

2. Classify content drift

For each changed obra skill, decide edited, new, or removed.

  • New skill: port it only if no native Reasonix tool already covers it (task, review, wait, explore). Otherwise add it to UPSTREAM.json retired with a one-line reason.
  • Removed upstream skill: consider retiring the port equivalent.

3. Re-port

Load superpowers-writing-skills. For each edited or to-be-ported skill, apply the Adaptations rules: snake_case tool names (read_file, edit_file, bash), description rewritten as a forceful imperative within the 130-char index budget, references/* auto-fold, native-tool substitution, path renames (docs/reasonix/...). Preserve the disciplines verbatim: Iron Laws, red-flag tables, RED-GREEN-REFACTOR. Keep bodies lean enough for the flash model.

4. Classify harness drift

Map each changed contract file to the port surface it touches:

  • internal/tool: tool names in every skill body and bench/reasonix.toml
  • internal/hook: AGENTS.md notes and any hook docs
  • internal/frontmatter: all skill frontmatter
  • internal/skill, internal/command: layout, loading, and /name assumptions

Update the affected skills, AGENTS.md, and bench config. If the change invalidated the local reasonix binary, rebuild it before trusting bench.

5. Bench-gate

  • node --test bench/structural.test.mjs (structure of every SKILL.md)
  • node bench/bench.mjs (invocation; prior cases must still pass)
  • exec-fidelity for any re-ported discipline skill, vs bench/BASELINE.json

Any structural failure or exec score below baseline blocks acceptance. Fix the skill body; do not lower the baseline.

6. Finalize

Bump UPSTREAM.json commits and dates to the synced HEADs, write a short report (changed, ported, retired, bench result), and commit. Close the open upstream-drift issue only after the synchronized changes reach main (for example, via the PR's closing keyword).

Frequently asked questions

What does the Superpowers Sync Upstream AI skill do?

Sync this port with upstream obra/superpowers or Reasonix main-v2: detect drift, re-port, bench-gate

Why use Superpowers Sync Upstream on TypingMind?

Because you install it once and use it with any model. Superpowers Sync Upstream is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Superpowers Sync Upstream in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/christopherarter/superpowers-reasonix/tree/main/skills/superpowers-sync-upstream. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Superpowers Sync Upstream?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Superpowers Sync Upstream?

As many as you like. As long as a model supports skills, you can use Superpowers Sync Upstream with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Superpowers Sync Upstream AI skill free?

Yes. It is published on GitHub by christopherarter under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇