fix: overhaul Claude Code plugin for correctness and spec compliance (#225 )

- Fix critical bugs: coder-agent name (CoderAgent→coder-agent), manifest
  path in session-start.sh, /oac:setup ghost command replaced with /install-context
- Fix hooks.json: add timeout/async, add description, restore matcher
- Fix session-start.sh: dual-format output (Claude Code + Cursor/OpenCode),
  remove invalid JSON escapes for $ and backtick
- Fix agent spec compliance: disallowedTools on read-only agents, WebFetch
  on external-scout, haiku model on context-scout, example blocks on 3 agents
- Fix skill descriptions: triggering conditions only (no workflow summaries)
  per superpowers empirical testing — prevents Claude shortcutting skill content
- Add Red Flags + Rationalization tables to 4 discipline skills
- Add install-context skill + command replacing oac-setup/oac-plan/oac-add-context
- Add cleanup-tmp.sh (was missing, broke /oac:cleanup)
- Add TypeScript installer (install-context.ts/js) with profile-based download
- Update plugin.json: keywords, homepage for marketplace discoverability
- Update README: correct skill count, fix structure diagram, remove stale refs
- Remove obsolete files: FIRST-TIME-SETUP.md, INSTALL.md, QUICK-START.md,
  download-context.sh, verify-context.sh, load-config.sh, context-manager skill,
  oac-setup/oac-plan/oac-add-context commands

2026-02-19 20:16:17 +00:00

2.3 KiB

Raw Blame History

name	description	disable-model-invocation
install-context	Install context files from registry. Use when user mentions "install context", "download context", or context is missing.	true

Install Context

Overview

Guide user through installing context files from OpenAgents Control registry with profile selection.

Announce at start: "I'm using the install-context skill to set up your context files."

The Process

Step 1: Check Current Installation

cat ${CLAUDE_PLUGIN_ROOT}/.context-manifest.json 2>/dev/null

If exists: Show current profile and ask if they want to change/reinstall.

If missing: Proceed to Step 2.

Step 2: Ask Which Profile

Present options, ask user to choose:

Available profiles:

essential   - Core patterns only (~4 components, 30s)
standard    - Typical use (~12 components, 2min) [RECOMMENDED]
extended    - Advanced features (~30 components, 5min)
specialized - Domain-specific (~50 components, 10min)
all         - Everything (~191 components, 20min)

Which profile? [standard]

Wait for response.

Step 3: Run Installer

cd ${CLAUDE_PLUGIN_ROOT}/scripts
bun run install-context.ts --profile={selected_profile}

If bun is not available, fallback to: node install-context.js --profile={selected_profile}

If user provided --force or --dry-run: Pass those flags.

Show output to user.

Step 4: Verify

cat ${CLAUDE_PLUGIN_ROOT}/.context-manifest.json
ls ${CLAUDE_PLUGIN_ROOT}/context/

Report: "✓ Installed {count} components. Context ready."

CLI Options

If user provides options, skip interactive prompts:

/install-context --profile=essential
/install-context --force
/install-context --dry-run
/install-context --categories=core-standards,openagents-repo

Error Handling

Git not installed:

✗ Git required. Install: brew install git

Network failure:

✗ Can't reach GitHub. Check connection and retry.

Already installed (without --force):

⚠ Already installed. Use --force to reinstall.

Remember

Keep it simple - just install and verify
Don't over-explain profiles
Show progress from installer
Verify manifest exists
Done

using-oac - Uses installed context
context-discovery - Discovers from installed context

2.3 KiB Raw Blame History