Update context-mode from GitHub and fix hooks/settings. Pulls latest, builds, installs, updates npm global, configures hooks. Trigger: /context-mode:ctx-upgrade
Scanned 6/1/2026
Install to Claude Code
npx -y skills add opencue/cuecards --skill ctx-upgrade --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Ctx Upgrade?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/opencue-ctx-upgrade)More formats (shields.io, HTML) on the badges page.
---
name: ctx-upgrade
description: |
Update context-mode from GitHub and fix hooks/settings.
Pulls latest, builds, installs, updates npm global, configures hooks.
Trigger: /context-mode:ctx-upgrade
user-invocable: true
---
# Context Mode Upgrade
Pull latest from GitHub and reinstall the plugin.
## Instructions
1. Call the `ctx_upgrade` MCP tool directly. It returns a shell command to execute.
2. Run the returned command using your shell execution tool (Bash, shell_execute, etc.).
3. Display results as a markdown checklist:
```
## context-mode upgrade
- [x] Pulled latest from GitHub
- [x] Built and installed v1.0.39
- [x] Hooks configured
- [x] Doctor: all checks PASS
```
Use `[x]` for success, `[ ]` for failure. Show actual version numbers.
4. Tell the user to **restart their session** to pick up the new version.
5. **Fallback** (only if MCP tool call fails): Derive the **plugin root** from this skill's base directory (go up 2 levels — remove `/skills/ctx-upgrade`), then run with Bash:
```
CLI="<PLUGIN_ROOT>/cli.bundle.mjs"; [ ! -f "$CLI" ] && CLI="<PLUGIN_ROOT>/build/cli.js"; node "$CLI" upgrade
```
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...