Fix skill description budget overflow — shorten major-domo, paper-dynasty, proxmox descriptions

Moved SCOPE restrictions from frontmatter description to markdown body to reduce
character budget consumption. Added description budget best practices to create-skill.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

mcp-needs-auth-cache.json

@@ -0,0 +1 @@
+{"claude.ai Gmail":{"timestamp":1772381125579},"claude.ai Google Calendar":{"timestamp":1772381125634}}

plugins/blocklist.json

@@ -1,5 +1,5 @@
 {
-  "fetchedAt": "2026-03-01T05:51:34.878Z",
+  "fetchedAt": "2026-03-01T16:05:25.240Z",
   "plugins": [
     {
       "plugin": "code-review@claude-plugins-official",

plugins/known_marketplaces.json

@@ -13,6 +13,6 @@
       "repo": "anthropics/claude-code"
     },
     "installLocation": "/home/cal/.claude/plugins/marketplaces/claude-code-plugins",
-    "lastUpdated": "2026-03-01T06:14:11.879Z"
+    "lastUpdated": "2026-03-01T16:05:33.053Z"
   }
 }

skills/create-skill/SKILL.md

@@ -110,11 +110,17 @@ Your description should:
 - Include trigger phrases (e.g., "USE WHEN user says...")
 - Mention key tools/methods used
 - Be concise but complete (1-3 sentences)
+- **Keep under ~200 characters** — descriptions share a ~16,000 character budget across ALL skills (2% of context window). Exceeding the budget causes skills to be silently dropped from discovery.
+
+**IMPORTANT: SCOPE restrictions** (e.g., "Only use in repo-X") go in the **markdown body**, NOT in the `description` field. The description is always loaded into context for routing; the body is only loaded on invocation. Putting SCOPE in the description wastes budget characters on every session.
 
 **Good examples:**
 - "Multi-source comprehensive research using perplexity-researcher, claude-researcher, and gemini-researcher agents. Launches up to 10 parallel research agents for fast results. USE WHEN user says 'do research', 'research X', 'find information about'..."
 - "Chrome DevTools MCP for web application debugging, visual testing, and browser automation. The ONLY acceptable way to debug web apps - NEVER use curl, fetch, or wget."
 
+**Bad example (wastes budget):**
+- "Comprehensive X management - feature A, feature B, feature C, feature D. USE WHEN ... Supports both production and development environments. SCOPE: Only use in repo-X, repo-Y. Do not activate in unrelated projects."
+
 ## Templates Available
 
 - `simple-skill-template.md` - For straightforward capabilities

skills/major-domo/SKILL.md

@@ -1,10 +1,12 @@
 ---
 name: major-domo
-description: Comprehensive Major Domo (SBA fantasy baseball league) management - Discord bot operations, API operations, database management, league operations, analytics, and development workflows. USE WHEN user mentions Major Domo, SBA, league operations, player stats, team rosters, Discord bot management, database migrations, or needs to work with the Strat-o-Matic Baseball Association system. Supports both production and development environments. SCOPE: Only use in major-domo-v2, major-domo-bot, major-domo-database repos. Do not activate in unrelated projects.
+description: Major Domo SBA fantasy baseball management. USE WHEN user mentions Major Domo, SBA, league operations, player stats, team rosters, Discord bot, database migrations, or Strat-o-Matic Baseball Association.
 ---
 
 # Major Domo - SBA Fantasy Baseball League Management
 
+**SCOPE**: Only use in major-domo-v2, major-domo-bot, major-domo-database repos. Do not activate in unrelated projects.
+
 ## When to Activate This Skill
 
 **Discord Bot Operations**:

skills/paper-dynasty/SKILL.md

@@ -1,10 +1,12 @@
 ---
 name: paper-dynasty
-description: Complete Paper Dynasty baseball card game management - API operations, gauntlet cleanup, pack distribution, scouting updates, card generation, team/player queries. USE WHEN user mentions Paper Dynasty, gauntlet teams, player cards, scouting reports, game stats, pack distribution, rewards, or needs database operations. Supports both structured workflows and creative ad-hoc requests. SCOPE: Only use in paper-dynasty, paper-dynasty-database repos. Do not activate in unrelated projects.
+description: Paper Dynasty baseball card game management. USE WHEN user mentions Paper Dynasty, gauntlet teams, player cards, scouting reports, pack distribution, rewards, or card game database operations.
 ---
 
 # Paper Dynasty - Baseball Card Game Management
 
+**SCOPE**: Only use in paper-dynasty, paper-dynasty-database repos. Do not activate in unrelated projects.
+
 ## First Step: Recall MemoryGraph
 
 **Before ANY Paper Dynasty operation:**

skills/proxmox/SKILL.md

@@ -1,10 +1,12 @@
 ---
 name: proxmox
-description: Comprehensive Proxmox VE management - VM lifecycle (start/stop/restart), VM creation/cloning, snapshot management, resource monitoring, LXC containers, storage operations, and backup management. USE WHEN user mentions "proxmox", "vm", "virtual machine", "qemu", "lxc", "container", "hypervisor", or needs VM infrastructure operations. SCOPE: Only use in claude-home or vm-management contexts. Do not activate in unrelated projects.
+description: Proxmox VE management - VM lifecycle, creation/cloning, snapshots, monitoring, LXC containers, storage, and backups. USE WHEN user mentions "proxmox", "vm", "virtual machine", "qemu", "lxc", "container", or "hypervisor".
 ---
 
 # Proxmox - Virtual Infrastructure Management
 
+**SCOPE**: Only use in claude-home or vm-management contexts. Do not activate in unrelated projects.
+
 ## When to Activate This Skill
 
 - "list my VMs", "show virtual machines"