- name
Find and implement evidence-backed simplifications in the ego-lite repository. Use when reviewing the codebase for dead code, duplicated state or APIs, speculative abstractions, unnecessary compatibil
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add citrolabs/ego-lite --skill ego-lite-simplify -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add citrolabs/ego-lite --skill ego-lite-simplify -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add citrolabs/ego-lite --skill ego-lite-simplify -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add citrolabs/ego-lite --skill ego-lite-simplify -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/citrolabs/ego-lite/tree/HEAD/.github/dev-skills/ego-lite-simplifyFrom the publisher
Reduce concepts and maintenance surface, not just line count. Prefer a few well-proven deletions over a long list of guesses.
AGENTS.md and the design document that owns the affected behavior.git status and preserve unrelated user changes.globalThis.ego is supplied by the closed-source app; docs/native-bindings-api.md documents that external contract.help(), and package/ego-browser/skill-body/SKILL.md.Start with production areas carrying the most state, branching, or public surface. Look for:
Do not count moving logic into a wrapper as simplification. Estimate the net result: implementation, tests, docs, public names, state transitions, and special cases removed minus new glue and dependencies added.
Use rg first. Search exact symbols, method forms, event names, configuration keys, error codes, protocol strings, and dynamic registration points. Read the callers rather than relying only on static-analysis output.
Classify evidence as:
package/ego-browser/src, runtime scripts, build and loader paths, and shipped site learnings.help(), package/ego-browser/skill-body/SKILL.md, architecture documents, and native binding behavior.Reject or downgrade a candidate when a real production caller exists, the native contract is uncertain, the change merely relocates complexity, or the deletion requires unrelated churn. A small local cleanup may be implemented directly; a behavior or API decision belongs in the owning design document first.
For an audit, present each worthwhile candidate with:
Call out candidates that require a user decision separately from behavior-preserving cleanups.
Follow spec-driven TDD when changing code:
Run the narrowest relevant checks first. From package/ego-browser/, use npm test for runtime changes, npm run e2e for real task-space/browser behavior, and npm run validate:site-skills for learning changes. Finish with git diff --check and report any verification that could not run.
Never edit generated build output as the source of a simplification. Never remove a defensive path until its trust or lifecycle boundary is understood.
© 2026 Skills Rack.
---name: ego-lite-simplifydescription: Find and implement evidence-backed simplifications in the ego-lite repository. Use when reviewing the codebase…---# .github/dev-skills/ego-lite-simplify/SKILL.mdOverview
Find and implement evidence-backed simplifications in the ego-lite repository. Use when reviewing the codebase for dead code, duplicated state or APIs, speculative abstractions, unnecessary compatibility layers, hand-written infrastructure, excessive tests or documentation, or when the user asks to reduce code size or maintenance complexity without hiding behavior changes.
FAQ
Download .github/dev-skills/ego-lite-simplify/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/citrolabs/ego-lite.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.