skills/context-optimizer/SKILL.md
Optimize token usage and context management. Use when sessions feel slow, context is degraded, or you're running out of budget.
npx skillsauth add rohitg00/pro-workflow context-optimizerInstall 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.
Manage your context window and token budget effectively.
/context to check current usage| Action | Saves | When |
|--------|-------|------|
| /compact | 30-50% context | At task boundaries |
| Disable unused MCPs | ~5% per MCP | When switching domains |
| Use subagents for exploration | Keeps main context clean | Heavy search/read tasks |
| Fresh session via /resume | 100% reset | When starting unrelated work |
Set proactive auto-compaction:
{
"env": {
"CLAUDE_AUTOCOMPACT_PCT_OVERRIDE": "50"
}
}
Keep <10 MCPs enabled, <80 tools total. Each MCP adds overhead to every request.
/mcp # List active servers
# Disable what you're not using
Heavy operations that generate lots of output should go to subagents:
The main session stays clean while subagents handle the volume.
| Phase | Target Usage | Action If Over | |-------|-------------|----------------| | Planning | < 20% | Keep plans concise | | Implementation | < 60% | Compact between files | | Testing | < 80% | Delegate to subagent | | Review | < 90% | Start fresh session |
Switch response style based on context:
Signs:
Fix:
/compact/resumedocumentation
Apply clear-writing standards to any prose the agent produces - READMEs, docs, UI copy, error messages, commit and PR text, release notes. Use when writing or editing documentation, interface copy, or any text a human will read. Says "write the README", "improve this copy", "draft the docs", "word this error".
development
Drive a change through a red-green-refactor loop - failing test first, minimal code to pass, then clean up. Use when implementing a feature or fixing a bug where correctness matters and a test can pin the behavior. Says "TDD", "test first", "red green refactor", "write the test first".
tools
The index of every pro-workflow skill and command, grouped by job, with when to reach for each and whether it is human-run or auto-triggered. Use when you are not sure which skill fits, want the full map, or ask "what can this do", "which skill for X", "list the workflow".
development
Audit an area of the codebase and propose the smallest structural moves that improve it - untangle boundaries, kill duplication, fix seams, break cycles. Produces a prioritized plan and decision records, not a rewrite. Use when a codebase feels tangled, hard to change, or is becoming a ball of mud, or when asked to improve or refactor architecture.