.claude/skills/context-monitor/SKILL.md
# Context Monitor Skill **Name:** context-monitor **Triggers:** `/context`, auto (every 10 messages) **Version:** 1.0.0 --- ## Purpose Monitors conversation context usage and prevents context overflow. --- ## Commands ### `/context` Shows current context status **Output:** ``` 📊 Context Status Tokens used: ~85,000 / 200,000 (42%) Status: 🟢 Normal Messages: 42 Last CLAUDE.md read: 15 messages ago (⚠️ re-read recommended) Recommendations: - Continue normally - Re-read CLAUDE.md within
npx skillsauth add CleanExpo/CCW-CRM .claude/skills/context-monitorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Name: context-monitor
Triggers: /context, auto (every 10 messages)
Version: 1.0.0
Monitors conversation context usage and prevents context overflow.
/contextShows current context status
Output:
📊 Context Status
Tokens used: ~85,000 / 200,000 (42%)
Status: 🟢 Normal
Messages: 42
Last CLAUDE.md read: 15 messages ago (⚠️ re-read recommended)
Recommendations:
- Continue normally
- Re-read CLAUDE.md within next 5 messages
/context compactTriggers context compaction (summarize and continue)
/context clearResets context (use sparingly)
Every 10 messages:
Every 5 messages:
# Check status
/context
# Trigger compaction
/context compact
content-media
Autonomously uploads CCW HeyGen demo videos to YouTube as Unlisted, collects video IDs, and patches DemoVideoBanner.tsx + video-registry.json. One-time OAuth setup required. Handles resume, retries, and ID propagation.
data-ai
Clear the freeze boundary set by /freeze, allowing edits to all directories again. Use when you want to widen edit scope without ending the session. Use when asked to "unfreeze", "unlock edits", "remove freeze", or "allow all edits". (gstack)
tools
# Spec Interview Skill **Name:** spec-interview **Triggers:** `/spec-interview`, when requirements unclear **Version:** 1.0.0 --- ## Purpose Interviews user to gather complete requirements before planning. --- ## Interview Questions When requirements are unclear, ask: ### 1. Feature Clarity **Question:** "What is this feature supposed to do?" **Why:** Need clear objective ### 2. User Impact **Question:** "Who will use this and why?" **Why:** Understand user needs ### 3. Success Criteri
development
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. Use when asked to "ship", "deploy", "push to main", "create a PR", "merge and push", or "get it deployed". Proactively invoke this skill (do NOT push/PR directly) when the user says code is ready, asks about deploying, wants to push code up, or asks to create a PR. (gstack)