everyinc · Agent Skills
36 Skills with substantive, source-verified documentation. Open a card to read the original instructions and review package and installation details.
ce-brainstorm
Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm or scope what to build. Not for executing already-specified work. Use ce-pov for a verdict on adopting a named external technology.
- 1h installs
- 3
- GitHub stars
- 25.2K
- Updated
- Sep 21
ce-polish
Polish a working feature through user-directed live browser feedback. Use when a functional feature needs focused UX refinement before shipping.
- 1h installs
- 3
- GitHub stars
- 25.2K
- Updated
- Sep 21
ce-promote
Draft launch or promotion copy for a shipped feature.
- 1h installs
- 3
- GitHub stars
- 25.2K
- Updated
- Sep 21
ce-work
Execute a plan or concrete work prompt end-to-end. Use when implementing from a plan document, a spec path, or a clear build request; use ce-debug for open-ended bugs. Use when an outer orchestrator needs implementation and local verification only, without the shipping tail.
- 1h installs
- 3
- GitHub stars
- 25.2K
- Updated
- Sep 21
lfg
Take a request all the way to done, hands-off, through the right Compound Engineering skills. A code change ends as an open pull request, pushed without stopping. Use only when the user explicitly asks for autonomous end-to-end work or invokes lfg directly. Use ce-plan, ce-work, ce-debug, or ce-commit-push-pr for work the user reviews step by step.
- 1h installs
- 3
- GitHub stars
- 25.2K
- Updated
- Sep 21
ce-doc-review
Review requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.
- 1h installs
- 2
- GitHub stars
- 25.4K
- Updated
- Oct 2
ce-ideate
Generate and evaluate grounded ideas. Use when the user wants ideas, improvements, or surprising directions before choosing one to develop. Not for refining an idea they already have (ce-brainstorm) or judging one already on the table (ce-pov).
- 1h installs
- 2
- GitHub stars
- 25.2K
- Updated
- Sep 21
ce-riffrec-feedback-analysis
Analyze recorded product feedback into evidence for bugs and requirements. Use when a Riffrec capture or other screen, voice, or notes artifact needs interpretation. Use for Riffrec setup, capture, or sharing help when no recording exists yet.
- 1h installs
- 2
- GitHub stars
- 25.2K
- Updated
- Sep 21
ce-test-browser
Run browser tests for pages affected by the current branch or PR. Use when asked to run or check browser tests for the current change.
- 1h installs
- 2
- GitHub stars
- 25.2K
- Updated
- Sep 21
ce-babysit-pr
Babysits an open GitHub PR until merge-ready, first judging whether an old PR still belongs. Use when asked to watch a PR over time or update an old one — not for one-shot comment resolution or one CI failure. GitHub (incl. Enterprise) only.
- 1h installs
- 1
- GitHub stars
- 26.1K
- Updated
- Nov 18
ce-code-review
Review a named diff or PR for bugs, regressions, tests, and standards. Use when asked to review code or when a shipping skill needs a review receipt. Use when asked to apply this review's findings locally. Use ce-resolve-pr-feedback for feedback already left on a PR.
- 1h installs
- 1
- GitHub stars
- 25.4K
- Updated
- Oct 8
ce-compound
Capture a solved problem's lesson in its cheapest durable form, a test or lint rule, a coding standard, or a repo learning, or refresh existing learnings against the codebase. Use when verified work corrected a wrong belief about how something behaves, such as a failed approach, a real defect a review caught, or a wrong assumption or document, or when auditing stale, overlapping, or drifted learnings. Do not auto-invoke it for work that went as first planned.
- 1h installs
- 1
- GitHub stars
- 26.2K
- Updated
- Nov 18
ce-compound-refresh
Refresh the repo's captured learnings against the current codebase. Use when auditing stale, overlapping, superseded, or drifted learnings; avoid general refactor, debugging, or code review unless the learnings store is explicit.
- 1h installs
- 1
- GitHub stars
- 25.4K
- Updated
- Oct 6
ce-debug
Diagnosis loop for bugs and failing behavior. Use when asked to debug or fix failing or slow behavior.
- 1h installs
- 1
- GitHub stars
- 25.3K
- Updated
- Sep 28
ce-explain
Create a durable visual teaching artifact for something worth learning. Use when the user wants to be taught, wants a deep explainer, wants to understand a substantial change, or wants a work recap built for retention. Not for ordinary Q&A, operational diagnosis, or a concise trade-off that belongs in chat. For learning, not repo docs or verdicts.
- 1h installs
- 1
- GitHub stars
- 24.9K
- Updated
- Sep 6
ce-handoff
Create a session handoff for another agent, or resume, find, and read any user-selected continuity source. Use when work or conversation must continue without access to the current session history.
- 1h installs
- 1
- GitHub stars
- 25.1K
- Updated
- Sep 13
ce-noslop
Rewrite, check, or draft prose so it carries no AI writing tells, reads plainly on the first read, and keeps every source fact. Use when asked to make writing plainer or free of those tells, to check writing for them, or when drafting from supplied content. Use ce-promote for channel-specific marketing copy.
- 1h installs
- 1
- GitHub stars
- 25.4K
- Updated
- Oct 6
ce-optimize
Optimize a named target with a measured loop: attribute a workload's cost, or score variants and keep winners. Use when a working system's metric should move and the winning change is not already known. Use ce-debug when the job is diagnosis; use ce-work when the change is already known.
- 1h installs
- 1
- GitHub stars
- 25.4K
- Updated
- Oct 6
ce-plan
Create structured plans for multi-step work, including software and non-software tasks. Use when asked to plan, break down implementation, plan from requirements, or deepen an existing plan; prefer ce-brainstorm for exploratory framing.
- 1h installs
- 1
- GitHub stars
- 26.2K
- Updated
- Nov 18
ce-product-pulse
Generate time-windowed product pulse reports from configured signals.
- 1h installs
- 1
- GitHub stars
- 25.4K
- Updated
- Oct 2
ce-proof
Publish, read, comment on, or edit markdown in Proof. Use for Proof links, sharing specs/plans/drafts, or publish handoffs from planning workflows; avoid proofread, math, evidence, or proof-of-concept meanings.
- 1h installs
- 1
- GitHub stars
- 25.4K
- Updated
- Oct 6
ce-retune
Retune a skill corpus for a new model, measurement-first: mine the run archive for a baseline, establish a noise floor, audit the corpus adversarially, then cut in measured passes until a pre-registered bar clears. Requires a benchmark harness that can A/B two builds of the corpus; refuses without one.
- 1h installs
- 1
- GitHub stars
- 25.3K
- Updated
- Sep 28
ce-setup
Check Compound Engineering's tools and repo config and fix what it finds, scaffold a Compound Pack with pack: , or draft and refresh coding standards and review docs from pull request history. Use when setting up or diagnosing Compound Engineering, or when creating or updating CODINGSTANDARDS.md or REVIEW.md, including on a schedule.
- 1h installs
- 1
- GitHub stars
- 26.2K
- Updated
- Nov 18
ce-simplify-code
Simplify code for clarity, reuse, quality, and efficiency while preserving behavior, and prune tests and comments that carry no value. Use after implementation and before review, or to audit tests or comments in any part of a repo; use ce-debug for bugs.
- 1h installs
- 1
- GitHub stars
- 26.2K
- Updated
- Nov 18
