switch-clients

Featured

Switch between existing customer engagements and triage competing needs. Use when context switching causes confusion; requires engagement records and preserves one client per write.

AI & Automation 948 stars 104 forks Updated yesterday MIT

Install

View on GitHub

Quality Score: 90/100

Stars 20%
99
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
66
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# switch-clients <!-- Generated by bin/generate-skills.js; edit the canonical references and catalog. --> ## Purpose Switch between existing customer engagements and triage competing needs. Use when context switching causes confusion; requires engagement records and preserves one client per write. 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.

Details

Author
suboss87
Repository
suboss87/FDEOps
Created
3 months ago
Last Updated
yesterday
Language
JavaScript
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category