EveryInc
@EveryInc Organization
Public Skills
ce-code-review
by EveryInc
"Structured code review for bugs, regressions, tests, and standards. Use before PRs or when asked for review; report-only by default, with explicit local apply available for user-directed fix workflows."
ce-commit
by EveryInc
Create a git commit with a clear, value-communicating message. Use when the user asks to commit/save staged or unstaged changes with a repo-appropriate message.
ce-proof
by EveryInc
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.
ce-prototype
by EveryInc
Build a throwaway prototype to answer how something should work, feel, or read — an interface, a flow, a state model, a visual direction. Use when committing the wrong answer would be expensive to unravel and a cheap sketch cannot settle it, whether the user settles it by driving the artifact or by seeing it at real finish — one question, or the next related question after that. 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.
ce-worktree
by EveryInc
Set up isolated git worktrees — create a new branch for fresh work, or attach a worktree to an existing branch/PR/commit to work on it in isolation. Use when starting isolated work or isolating an existing ref; detects existing isolation first.
ce-promote
by EveryInc
"Draft launch or promotion copy for a shipped feature."
ce-retune
by EveryInc
"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."
ce-resolve-pr-feedback
by EveryInc
Resolve PR review feedback. Use when addressing review comments, resolving review threads, or fixing code-review feedback.
ce-polish
by EveryInc
"Start the dev server, inspect the feature in browser, and iterate on polish."
ce-riffrec-feedback-analysis
by EveryInc
Analyze Riffrec feedback captures from bundles or standalone recordings. Always load for riffrec-*.zip, session.json + events.json + recording.webm + voice.webm bundles, .mp4/.mov/.webm videos, .m4a/.mp3/.wav audio, or capture/share requests.
agent-only-skill
by EveryInc
An agent-only skill not intended for direct user invocation
claude-only-skill
by EveryInc
A skill restricted to Claude Code only
setup
by EveryInc
Configure which review agents run for your project. Auto-detects stack and writes compound-engineering.local.md.
dspy-ruby
by EveryInc
Build type-safe LLM applications with DSPy.rb — Ruby's programmatic prompt framework with signatures, modules, agents, and optimization. Use when implementing predictable AI features, creating LLM signatures and modules, configuring language model providers, building agent systems with tools, optimizing prompts, or testing LLM-powered functionality in Ruby applications.
skill-creator
by EveryInc
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
orchestrating-swarms
by EveryInc
This skill should be used when orchestrating multi-agent swarms using Claude Code's TeammateTool and Task system. It applies when coordinating multiple agents, running parallel code reviews, creating pipeline workflows with dependencies, building self-organizing task queues, or any task benefiting from divide-and-conquer patterns.
disabled-skill
by EveryInc
A skill with model invocation disabled
create-agent-skills
by EveryInc
Expert guidance for creating Claude Code skills and slash commands. Use when working with SKILL.md files, authoring new skills, improving existing skills, creating slash commands, or understanding skill structure and best practices.
file-todos
by EveryInc
This skill should be used when managing the file-based todo tracking system in the todos/ directory. It provides workflows for creating todos, managing status and dependencies, conducting triage, and integrating with slash commands and code review processes.
compound-docs
by EveryInc
Capture solved problems as categorized documentation with YAML frontmatter for fast lookup
resolve_pr_parallel
by EveryInc
Resolve all PR comments using parallel processing. Use when addressing PR review feedback, resolving review threads, or batch-fixing PR comments.
document-review
by EveryInc
This skill should be used to refine brainstorm or plan documents before proceeding to the next workflow step. It applies when a brainstorm or plan document exists and the user wants to improve it.
brainstorming
by EveryInc
This skill should be used before implementing features, building components, or making changes. It guides exploring user intent, approaches, and design decisions before planning. Triggers on "let's brainstorm", "help me think through", "what should we build", "explore approaches", ambiguous feature requests, or when the user's request has multiple valid interpretations that need clarification.
skill-one
by EveryInc
Sample skill