EveryIncSkillce-product-pulse
EveryInc/compound-engineering-plugin/skills/ce-product-pulse/SKILL.md
Generate time-windowed product pulse reports from configured signals.
Steady36 mentions in 2 weeks
4 projects use a version of this
Claude skills and agent skills
Skills real projects publish on GitHub, most starred first. Each one says what it will make an agent do before you copy it.
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.
Worked for most · soon
EveryIncSkillEveryIncSkillce-promote
EveryInc/compound-engineering-plugin/skills/ce-promote/SKILL.md
Draft launch or promotion copy for a shipped feature.
Steady36 mentions in 2 weeks
4 projects use a version of this
EveryIncSkillce-proof
EveryInc/compound-engineering-plugin/skills/ce-proof/SKILL.md
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.
Steady36 mentions in 2 weeks
4 projects use a version of this
EveryIncSkillce-prototype
EveryInc/compound-engineering-plugin/skills/ce-prototype/SKILL.md
Build a throwaway prototype to answer how something should work, feel, or read. Use when committing the wrong answer would be expensive to unravel and a cheap sketch cannot settle it. Not a rough visual probe during brainstorming, not for deciding what to build, not polishing a feature that already works, not implementing the real thing.
Steady36 mentions in 2 weeks
4 projects use a version of this
EveryIncSkillce-resolve-pr-feedback
EveryInc/compound-engineering-plugin/skills/ce-resolve-pr-feedback/SKILL.md
Judge PR feedback centrally, apply valid fixes, and complete review conversations with publication verified. Use when addressing feedback already left on a PR, preparing local fixes for a caller to publish, or completing a saved feedback batch. Use ce-code-review for reviewing code before feedback exists.
Steady36 mentions in 2 weeks
5 projects use a version of this
EveryIncSkillce-retune
EveryInc/compound-engineering-plugin/skills/ce-retune/SKILL.md
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.
Steady36 mentions in 2 weeks
3 projects use a version of this
EveryIncSkillce-riffrec-feedback-analysis
EveryInc/compound-engineering-plugin/skills/ce-riffrec-feedback-analysis/SKILL.md
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.
Steady36 mentions in 2 weeks
4 projects use a version of this
EveryIncSkillce-setup
EveryInc/compound-engineering-plugin/skills/ce-setup/SKILL.md
Check Compound Engineering health and repo-local config, scaffold a Compound Pack with `pack:<id>`, or draft or refresh coding standards and review docs with `standards`.
EveryIncSkillce-simplify-code
EveryInc/compound-engineering-plugin/skills/ce-simplify-code/SKILL.md
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.
Steady36 mentions in 2 weeks
4 projects use a version of this
EveryIncSkillce-strategy
EveryInc/compound-engineering-plugin/skills/ce-strategy/SKILL.md
Create or update STRATEGY.md. Use when starting a product, adding a strategy doc, or changing direction or roadmap.
EveryIncSkillce-sweep
EveryInc/compound-engineering-plugin/skills/ce-sweep/SKILL.md
Sweep configured feedback sources (Slack, GitHub Issues; email experimental) for new items: acknowledge at source, analyze recordings, verify fixes merged to main, and emit an `lfg`-ready plan. First run sets up sources; supports mode:non-interactive for scheduled runs.
Steady36 mentions in 2 weeks
3 projects use a version of this
EveryIncReads credentialsSkillce-test-browser
EveryInc/compound-engineering-plugin/skills/ce-test-browser/SKILL.md
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.
Steady36 mentions in 2 weeks
5 projects use a version of this
EveryIncSkillce-test-xcode
EveryInc/compound-engineering-plugin/skills/ce-test-xcode/SKILL.md
Test iOS apps in a simulator with XcodeBuildMCP. Use when iOS changes need simulator evidence before handoff.
Steady36 mentions in 2 weeks
4 projects use a version of this
EveryIncSkillce-work
EveryInc/compound-engineering-plugin/skills/ce-work/SKILL.md
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.
Steady36 mentions in 2 weeks
7 projects use a version of this
EveryIncSkillce-worktree
EveryInc/compound-engineering-plugin/skills/ce-worktree/SKILL.md
Set up isolated git worktrees — create a new branch for fresh work, or attach a worktree to an existing branch, PR, or commit. Use when starting isolated work or isolating an existing ref.
Steady36 mentions in 2 weeks
5 projects use a version of this
EveryIncSkilllfg
EveryInc/compound-engineering-plugin/skills/lfg/SKILL.md
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.
EveryIncSkillwtf
EveryInc/compound-engineering-plugin/skills/wtf/SKILL.md
Explain the last message, or a supplied file, link, or passage, in plain language a person follows on the first read. Use when the user invokes wtf because they did not follow something. Use ce-explain to investigate how or why code works, and ce-noslop to rewrite prose.
Steady36 mentions in 2 weeks
16 projects use a version of this
EveryIncSkillce-babysit-pr
EveryInc/compounding-engineering-plugin/skills/ce-babysit-pr/SKILL.md
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.
EveryIncSkillce-bakeoff
EveryInc/compounding-engineering-plugin/skills/ce-bakeoff/SKILL.md
Develop independent competing solutions to a defined brief, compare them, and synthesize a winning approach. Use when choosing well requires developing alternatives beyond their current form. Use ce-pov to judge developed material and ce-ideate to discover opportunities.
Steady36 mentions in 2 weeks
3 projects use a version of this
EveryIncSkillce-brainstorm
EveryInc/compounding-engineering-plugin/skills/ce-brainstorm/SKILL.md
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.
Steady36 mentions in 2 weeks
6 projects use a version of this
About skills
What is a Claude skill?
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.