pack-switch

Switches the active Lintel pack and audits the change for the next session.

Updated May 27, 2026
One-click install
npx skills add https://github.com/jokerman89/lintel --skill pack-switch-jokerman89
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pack-switch
Source: https://github.com/jokerman89/lintel/tree/main/skills/pack-switch
Command: npx skills add https://github.com/jokerman89/lintel --skill pack-switch-jokerman89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams working across multiple customer or compliance contexts need a controlled way to change which pack drives voice, compliance, persona, and roles, without manually editing state files or losing track of what changed. ## Core Features & Use Cases - Validated pack switching: Confirms the target pack passes validation before writing it to the active-pack state file, refusing invalid targets. - Change preview and audit: Shows a field-level diff between the current and target pack (voice tier, compliance mode, default workflow) and appends a JSONL audit record of every switch. - Extension pack awareness: Detects extension packs and surfaces their namespace, workflow, and shipped skills, agents, and hooks. - Use Case: An operator finishes work for one customer and runs the switch to a different company pack; the skill confirms the change, logs it, and the next session loads the new identity automatically. ## Quick Start Ask the agent to switch the active pack to a named pack, for example by saying switch the active pack to acme-corp.

Frequently Asked Questions about pack-switch

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

FAQPage Schema
How do I switch the active pack in Lintel?▼

Run the pack-switch skill with the target pack name. It validates the pack, shows a diff of changed fields, asks for confirmation, then writes the new active pack and logs the switch to the audit file.

When does a pack switch take effect?▼

The switch takes effect at the next session. The current session keeps its cached pack per the pack-resolver semantics, so mid-cycle work is not disrupted by the change.

Can I override the pack for just one workflow without switching?▼

Yes. Use the --mode or --pack flags for a one-off override instead of switching the active pack. Pack-switch is intended for durable context changes, not single workflow runs.

Why does pack-switch refuse to change to my pack?▼

The switch is refused when the target pack fails validation through the pack-resolver library. Run the pack-list command to see which packs are valid, then fix the target pack's manifest before retrying.

Does switching to an extension pack load its skills and agents?▼

Not by itself. An extension pack must also be installed as a plugin for its skills, agents, and hooks to load. Pack-switch activates its identity and makes Lintel aware of it for the next session.