context-optimize
Skill8 starsChanged 9 months agoMITView on GitHub
Context Optimization - Orchestrate RPI workflow TODO generation with interactive scoping
3 other projects use a version of this.
Adopted by
Most recently taken up by
- Joonghyun-Lee-Frieren/oh-my-antigravitytheir own version, first seen Oct 25, 2026
- Joonghyun-Lee-Frieren/oh-my-gemini-clitheir own version, first seen Oct 8, 2026
- ibahgat/oh-my-iflowtheir own version, first seen Mar 14, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- Joonghyun-Lee-Frieren/oh-my-antigravity★ 214same name
- Joonghyun-Lee-Frieren/oh-my-gemini-cli★ 214same name
- ibahgat/oh-my-iflow★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository7 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- implementSkill
- planSkill
- researchSkill
- validateSkill
- verify-docsSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
When invoked, orchestrate context engineering optimization with interactive scoping:
- Distinctive: line 12
Ask up to 4 multiple choice questions to define scope
- Distinctive: line 18
Check workflow file coverage and accuracy
- Distinctive: line 19
Verify index file completeness
- Distinctive: line 24
Create actionable TODO with research, plan, implement phases
- Distinctive: line 82
After completion, execute the generated TODO list:
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Context Engineering: Optimization Orchestrator
When invoked, orchestrate context engineering optimization with interactive scoping:
Process
- Interactive Scoping (if no --auto flag)
- Ask up to 4 multiple choice questions to define scope
- Questions cover: optimization focus, codebase areas, enhancement types, priority order
- Skip questions if --scope or --auto flag provided
- Context System Audit
- Analyze
.claude/directory structure - Check workflow file coverage and accuracy
- Verify index file completeness
- Identify orphaned or outdated files
- Assess agent and command coverage gaps
- Analyze
- Generate RPI TODO List
- Create actionable TODO with research, plan, implement phases
- Save to
.claude/plans/active/context-optimization_plan.md - Include specific commands for each task
- Redundant File Detection
- Find files not referenced by any index
- Identify duplicate or overlapping content
- Flag outdated files with stale line references
- Report empty placeholder files
- Enhancement Recommendations
- Suggest new specialized agents based on codebase patterns
- Recommend workflow commands for common tasks
- Identify undocumented workflows needing documentation
Scoping Questions (Max 4)
Q1: Optimization Focus
- A) Functionalize the entire context engineering system
- B) Update outdated documentation and line references
- C) Identify and remove redundant context files
- D) Discover enhancement opportunities (new agents/commands)
Q2: Codebase Coverage
- A) Core business logic
- B) API/External integrations
- C) Database/Data layer
- D) All areas equally
Q3: Enhancement Preferences
- A) New specialized agents for specific domains
- B) New workflow commands for common tasks
- C) Improved documentation structure
- D) Better cross-referencing and navigation
Q4: TODO Priority Order
- A) Quick wins first (< 30 min each)
- B) High impact first (regardless of effort)
- C) By workflow area (grouped logically)
- D) By dependency order (foundational first)
Context Budget
- Target: 20% of 200k tokens (40k)
- Output: TODO checklist + recommendations
Output
- TODO checklist saved to
.claude/plans/active/context-optimization_plan.md - Audit findings in
.claude/research/active/context-audit_research.md
Arguments
$ARGUMENTScan include:--auto- Use intelligent defaults, skip questions--scope documentation- Focus on docs only--scope agents- Focus on agent gaps--scope workflows- Focus on workflow coverage--scope cleanup- Focus on redundant file removal
Next Steps
After completion, execute the generated TODO list:
/rpi-research [first-research-task]/rpi-plan [first-plan-task]/rpi-implement [first-impl-task]/validate-all
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.