update-powerpacks

Updates the Powerpacks checkout to the newest published release and reinstalls skills.

1|1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/powerset-co/powerpacks --skill update-powerpacks-powerset-co
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: update-powerpacks
Source: https://github.com/powerset-co/powerpacks/tree/main/packs/powerset/skills/update-powerpacks
Command: npx skills add https://github.com/powerset-co/powerpacks --skill update-powerpacks-powerset-co

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Keeping an installed Powerpacks checkout current normally requires manual Git operations, stash handling, and reinstall steps that are easy to get wrong. This Skill replaces all of that with a single harness-specific command that force-updates to the newest published release while preserving local .powerpacks state. ## Core Features & Use Cases - One-command update: Runs a single updater script per harness (Codex, Claude Code, or Pi) with no Git inspection, stash repair, or post-update setup required. - Release channels: Defaults to the newest stable release, with opt-in prefixes for release candidates (POWERPACKS_CHANNEL=rc), unreleased edge builds, or an exact pinned version via POWERPACKS_REF. - Credential refresh: Refreshes the provisioned POWERSET_API_KEY and enables the cross-encoder for searches unless explicitly disabled in .env; signed-out users keep their existing settings. - Use Case: Your installed Powerpacks skills are behind the latest release. Invoke $update-powerpacks and the agent runs the correct updater for your harness, then reports the script's final key/value output lines. ## Quick Start Use the update-powerpacks skill to update my Powerpacks installation to the newest published release.

Frequently Asked Questions about update-powerpacks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update Powerpacks to the latest version?▼

Invoke $update-powerpacks and the agent runs one updater script for your harness: Codex, Claude Code, or Pi. The script force-updates the checkout to the newest published release and reinstalls skills while preserving your .powerpacks directory.

How do I install a release candidate or edge build of Powerpacks?▼

Prefix the update command with POWERPACKS_CHANNEL=rc for the newest release candidate or POWERPACKS_CHANNEL=edge for the unreleased tip of the default branch. The chosen channel sticks for every later update.

Can I pin Powerpacks to one exact version?▼

Yes, set POWERPACKS_REF to a specific release tag such as powerpacks-v0.18.0 before running the update command. This installs exactly that version instead of the newest published release.

Does updating Powerpacks affect my API key or local settings?▼

The updater refreshes the provisioned POWERSET_API_KEY and enables the cross-encoder for searches unless .env sets POWERPACKS_CROSS_ENCODER_BETA=0. Signed-out or unprovisioned users keep their existing settings, and the update reports this.

Should I check Git status or run setup after updating Powerpacks?▼

No. The skill explicitly forbids inspecting Git state, running other Git commands, popping the stash, or running setup, doctor, imports, or state repair afterward. You only run the single updater command and report its final key/value lines.