Plan data-center fabric upgrades (ISSU, SMU, or cold) with traffic shift and abort criteria. Use when a spine, leaf, or border-leaf train is moving and you need a sequenced window.
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add gesh75/claude-skill-lint --skill dc-fabric-upgrade --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Dc Fabric Upgrade?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/gesh75-dc-fabric-upgrade)More formats (shields.io, HTML) on the badges page.
---
name: dc-fabric-upgrade
description: Plan data-center fabric upgrades (ISSU, SMU, or cold) with traffic shift and abort criteria. Use when a spine, leaf, or border-leaf train is moving and you need a sequenced window.
argument-hint: "[role] [from] [to]"
allowed-tools: Read Grep
license: MIT
---
# DC fabric upgrade
Do not use for campus stack upgrades or firewall HA failover. Not for optics swaps without a train change.
## Procedure
1. Read the release notes for the target train: EVPN, BFD, and VXLAN caveats. Lab the SMU on a spare leaf.
2. Shift: one spine at a time, then border, then a canary leaf pair, then the rest. Never two spines.
3. Abort criteria written before the window: BGP session count, EVPN route count, packet loss > 0.1% for 30s.
4. Optics and FEC stay pinned. Do not "also replace QSFP" in the same window.
5. Verify per device: control-plane, forwarding, then the next device.
```text
window Sat 01:00-05:00
01:00 drain spine-1 confirm ECMP N-1
01:40 ISSU spine-1
02:10 un-drain watch 15m
abort if evpn type-2 delta > 1%
```
## Anti-patterns
- Never upgrade both spines because "ISSU is hitless".
- Do not mix a code upgrade with a cabling change.
## Safety
Abort is a first-class step. A failed canary stops the fleet.
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!
Ultra-compressed communication mode. Cuts token usage ~75% by speaking like caveman while keeping full technical accuracy. Supports intensity levels: lite, full (default), ultra, wenyan-lite, wenyan-full, wenyan-ultra. Use when user says "caveman mode", "talk like caveman", "use caveman", "less tokens", "be brief", or invokes /caveman. Also auto-triggers when token efficiency is requested.
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', ...
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
**Complete production-ready guide for Google Gemini embeddings API** This skill provides comprehensive coverage of the `gemini-embedding-001` model for generating text embeddings, including SDK usage, REST API patterns, batch processing, RAG integration with Cloudflare Vectorize, and advanced use cases like semantic search and document clustering. ---
Recovers prior coding-agent session context by running `catchup <agent> --since-compact`, which extracts a clean summary of a previous Codex, Claude Code, Antigravity, OpenCode, or Pi Agent session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", or asks to recover/summarize a previous session before continuing. Do NOT use for the current conversation, git history, or any non-agent log.
