everyinc · Agent Skills

36 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.

everyinc

Community

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.

installs

3

GitHub stars

25.2K

Updated

Sep 21

MIT26 Files

View skill details →

everyinc

Community

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.

installs

3

GitHub stars

25.2K

Updated

Sep 21

MIT38 Files

View skill details →

everyinc

Community

ce-polish

Polish a working feature through user-directed live browser feedback. Use when a functional feature needs focused UX refinement before shipping.

installs

3

GitHub stars

25.2K

Updated

Sep 21

MIT17 Files

View skill details →

everyinc

Community

ce-promote

Draft launch or promotion copy for a shipped feature.

installs

3

GitHub stars

25.2K

Updated

Sep 21

MIT3 Files

View skill details →

everyinc

Community

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.

installs

3

GitHub stars

25.2K

Updated

Sep 21

MIT25 Files

View skill details →

everyinc

Community

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.

installs

3

GitHub stars

25.2K

Updated

Sep 21

MIT11 Files

View skill details →

everyinc

Community

ce-doc-review

Review requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.

installs

2

GitHub stars

25.4K

Updated

Oct 2

MIT26 Files

View skill details →

everyinc

Community

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).

installs

2

GitHub stars

25.2K

Updated

Sep 21

MIT18 Files

View skill details →

everyinc

Community

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.

installs

2

GitHub stars

25.2K

Updated

Sep 21

MIT7 Files

View skill details →

everyinc

Community

ce-simplify-code

Simplify settled, recently changed code for clarity, reuse, quality, and efficiency while preserving behavior. Use after implementation and before review; use ce-debug for bugs.

installs

2

GitHub stars

25.2K

Updated

Sep 21

MIT4 Files

View skill details →

everyinc

Community

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.

installs

2

GitHub stars

25.2K

Updated

Sep 21

MIT5 Files

View skill details →

everyinc

Community

ce-babysit-pr

Babysits an open GitHub PR until merge-ready. Use when asked to watch a PR over time — not for one-shot comment resolution or one CI failure. GitHub (incl. Enterprise) only.

installs

1

GitHub stars

25.4K

Updated

Oct 6

MIT12 Files

View skill details →

everyinc

Community

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.

installs

1

GitHub stars

25.4K

Updated

Oct 8

MIT40 Files

View skill details →

everyinc

Community

ce-compound

Document a solved problem as a durable repo learning. Use when verified work produced non-obvious reasoning absent from its final code, tests, or existing docs; avoid routine fixes whose artifacts already explain the lesson.

installs

1

GitHub stars

25.4K

Updated

Oct 6

MIT28 Files

View skill details →

everyinc

Community

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.

installs

1

GitHub stars

25.4K

Updated

Oct 6

MIT16 Files

View skill details →

everyinc

Community

ce-debug

Diagnosis loop for bugs and failing behavior. Use when asked to debug or fix failing or slow behavior.

installs

1

GitHub stars

25.3K

Updated

Sep 28

MIT9 Files

View skill details →

everyinc

Community

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.

installs

1

GitHub stars

24.9K

Updated

Sep 6

MIT8 Files

View skill details →

everyinc

Community

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.

installs

1

GitHub stars

25.1K

Updated

Sep 13

MIT3 Files

View skill details →

everyinc

Community

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.

installs

1

GitHub stars

25.4K

Updated

Oct 6

MIT3 Files

View skill details →

everyinc

Community

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.

installs

1

GitHub stars

25.4K

Updated

Oct 6

MIT20 Files

View skill details →

everyinc

Community

ce-product-pulse

Generate time-windowed product pulse reports from configured signals.

installs

1

GitHub stars

25.4K

Updated

Oct 2

MIT7 Files

View skill details →

everyinc

Community

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.

installs

1

GitHub stars

25.4K

Updated

Oct 6

MIT3 Files

View skill details →

everyinc

Community

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.

installs

1

GitHub stars

25.3K

Updated

Sep 28

MIT8 Files

View skill details →

everyinc

Community

ce-setup

Check Compound Engineering health and repo-local config, or scaffold a Compound Pack with pack: .

installs

1

GitHub stars

25.4K

Updated

Oct 6

MIT11 Files

View skill details →