version unknown

ego-lite-simplify

citrolabs@citrolabs⭐ 22.8k stars· last commit 11d ago· 234 open issues

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.

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

6.7/10
Verified
Oct 11, 2026

// RATINGS

⭐GitHub Stars
⭐⭐⭐⭐⭐ 22.8k on GitHubGitHub ↗

Very popular

🟢ProSkills ScoreAI Verified
6.7/10
📍

Not yet listed on ClawHub or SkillsMP

// README

The fastest browser for AI agents to run web automation

ego (lite) is a browser where you and your AI agents work in parallel. Your agents run their browser tasks in their own Spaces, isolated workspaces inside the same browser, while you keep browsing in yours, so no agent ever takes the browser away from you. And the automation itself finishes faster, on fewer tokens.

Existing tools like browser-use and agent-browser are a bridge to the browser, not a browser of their own: they need a separate one to drive, your browser data rarely carries over intact, the connection is unstable, and you and the agent end up fighting over control of the browser. ego lite is one browser designed from the start for the two of you to share. No extra setup, and the agent can always reach your real logins and tabs through ego-browser.

Demo

https://github.com/user-attachments/assets/ffe7954b-58ee-411e-b35d-ec30c58a08bc

Quick Start

ego lite runs on macOS and Windows, and Linux is on the roadmap.

1. Install

Pick whichever fits your flow.

1.1 Download the app

Click to download, then open it to install. Either way, ego lite adds the ego-browser skill to every agent's skills directory on your machine.

1.2 Add the skill with npx

Install just the ego-browser skill:

npx skills add citrolabs/ego-lite

The first time your agent runs a browser task, it walks you through installing the ego lite app.

1.3 Let your agent set it up

Paste this into your agent:

Set up ego lite for me: https://github.com/citrolabs/ego-lite

Read `skills/ego-browser/references/install.md` and follow the steps to install ego lite.

On first launch, ego lite asks one question, whether to migrate your Chrome data. Say yes and your agent inherits your existing logins, cookies, extensions, and bookmarks.

2. Try your first task

In your agent CLI, type /ego-browser followed by a space, then describe what you want in plain language:

ego-browser follow @ego_agent on x.com for me

The agent picks up the ego-browser skill, opens the page in its own Space, reads a Snapshot (the page turned into structured text), acts on the page, and reports back, all while your own tabs stay untouched.

Your browsing data, cookies, and everything else the browser holds stay on your device. ego lite keeps its data collection deliberately narrow: simple product signals, like whether you've set ego lite as your default browser.

Highlights of ego lite

FeatureWhat it does
Code-based, not CLI-based: faster runs on fewer tokens for complex tasksThe capabilities ego lite exposes to the agent are wrapped as JavaScript functions the agent calls directly. The agent gets to do what it does best: write code, composing a multi-step task into a single output instead of getting stuck in a "call two commands, look at the result, call two more commands" loop. Compared to the conventional CLI approach, complex workflows finish far faster, with higher task success rates, far fewer tool calls per task, and a much lower cost per task.
A dedicated Space for every agentego lite gives each agent its own fully isolated Space. You browse up front, your agent works in the background, and they don't get in each other's way. You can see which Space has an agent running at any moment, and take it over or stop it whenever you want.
Your agents multitask in Spaces, parallel workspaces inside the same browserEach Space gets its own AI agent or its own task, all running at the same time. Claude Code enriching 10 leads in 10 parallel Spaces. Codex scraping 5 competitor sites in 5 more. They don't collide or steal your tabs. Your mouse stays where you left it.
The strongest page Snapshot on the marketThanks to customization inside the browser engine, ego lite produces the highest-quality page snapshots, the view text-only models rely on to "see" and act on a webpage. It reliably handles tough cases like deeply nested iframes, exactly where other approaches consistently break down.
Any agent can drive it through ego-browserego-browser is the connection layer between any agent CLI (Claude Code, Codex, Cursor, or a custom one) and ego lite. It exposes the browser as a set of in-page JavaScript tools: snapshot, fill, click, wait, navigate, capture. The agent writes a JavaScript snippet calling those tools, and ego-browser runs it on the page in one pass.
Experience accumulation that makes your agent faster the more you use it (coming soon)Most of an agent's time on browser tasks goes to trial and error. ego lite's official Skill distill

// HOW IT'S BUILT

// FILES

3 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • .github/dev-skills/ego-lite-simplify/SKILL.md4.8 KBe8a482c9d0d0upstream ↗
    ---
    name: ego-lite-simplify
    description: 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.
    ---
    
    # Simplify ego-lite
    
    Reduce concepts and maintenance surface, not just line count. Prefer a few well-proven deletions over a long list of guesses.
    
    ## Establish the contract
    
    1. Read `AGENTS.md` and the design document that owns the affected behavior.
    2. Inspect `git status` and preserve unrelated user changes.
    3. Decide whether the request is an audit or an authorized implementation. Do not turn a cleanup into a product decision without making the behavior change explicit.
    4. Identify the relevant boundary before judging code:
       - `globalThis.ego` is supplied by the closed-source app; `docs/native-bindings-api.md` documents that external contract.
       - The runtime has direct CLI and embedded SDK startup paths.
       - Public agent APIs must stay aligned across implementation, tests, `help()`, and `package/ego-browser/skill-body/SKILL.md`.
       - Browser state can outlive the short Node.js process.
    
    ## Find strong candidates
    
    Start with production areas carrying the most state, branching, or public surface. Look for:
    
    - Exports, helpers, events, options, fallbacks, packages, or state fields with no production consumer.
    - Tests or documentation that are the only consumers of behavior that is no longer required.
    - Multiple representations of the same page, task-space, session, ref, lifecycle, or output state.
    - Pass-through layers that add vocabulary but no policy, isolation, or test seam.
    - Compatibility code that is unnecessary on an explicitly breaking branch.
    - Generality with no current product use, such as unsupported concurrency modes or unused extension points.
    - Special cases, rollback paths, or validation that exist only to protect a removable surface.
    - Hand-written parsers, queues, retry logic, or utilities that a Node.js built-in or healthy dependency can replace with less total code.
    
    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.
    
    ## Prove each candidate
    
    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:
    
    - **Production:** `package/ego-browser/src`, runtime scripts, build and loader paths, and shipped site learnings.
    - **Contract:** public JSDoc consumed by `help()`, `package/ego-browser/skill-body/SKILL.md`, architecture documents, and native binding behavior.
    - **Non-production:** tests, fixtures, snapshots, comments, and historical or draft documents.
    - **Ambiguous:** examples and development scripts; inspect how they are invoked before deciding.
    
    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.
    
    ## Report before broad removal
    
    For an audit, present each worthwhile candidate with:
    
    - The surface to remove or fold.
    - Call-site and contract evidence.
    - The user-visible behavior change, or “none”.
    - What complexity disappears and what replacement remains.
    - Confidence, risks, and the smallest verification needed.
    
    Call out candidates that require a user decision separately from behavior-preserving cleanups.
    
    ## Implement safely
    
    Follow spec-driven TDD when changing code:
    
    1. Update or add a characterization test when existing behavior must remain.
    2. Update the owning design or API contract before an intentional behavior change.
    3. Remove the implementation and its now-obsolete tests, fixtures, exports, JSDoc, help entries, and skill documentation together.
    4. Keep comments in English and explain only non-obvious constraints.
    5. Prefer deleting a state or transition over adding another abstraction around it.
    
    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.
    
  • .github/dev-skills/ego-lite-simplify/agents/openai.yaml250 B7848c1d0a41bupstream ↗
    interface:
      display_name: "Simplify ego-lite"
      short_description: "Find and remove unnecessary ego-lite complexity"
      default_prompt: "Use $ego-lite-simplify to find evidence-backed ways to reduce this repository’s code and maintenance surface."
    
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/citrolabs-ego-lite-github-dev-skills-ego-lite-simplify.md

// REPO STATS

22.8k stars
234 open issues
Last commit: 11d ago