Switch between existing customer engagements and triage competing needs. Use when context switching causes confusion; requires engagement records and preserves one client per write.
Installs into .claude/skills of the current project.
Are you the author of Switch Clients?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/suboss87-switch-clients)
---
name: switch-clients
description: Switch between existing customer engagements and triage competing needs. Use when context switching causes confusion; requires engagement records and preserves one client per write.
---
# switch-clients
<!-- Generated by bin/generate-skills.js; edit the canonical references and catalog. -->
## Purpose
A refreshed client binding and cross-client triage.
Before investigating or acting:
1. Read [the task context contract](references/task-context.md).
2. Read [the method](references/switch-clients.md).
Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.
## Principles
- This task operates on existing engagement records. Use the local CLI and permitted sanitized packets; do not invent a portfolio or initialize records merely to complete the task. Report missing records or access as a limitation.
- If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
- The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
- Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.
