everyinc
- 209 skills
- 0 followers
- 26k repo stars
- last month last updated
- ▌ Ce Compound 3 · everyinc bundleDocument 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.
- ▌ Ce Brainstorm 3 · everyinc bundleExplore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm, scope what to build, or needs collaborative product framing before planning. Also use when they must scope work in territory they do not know, or ask for a blindspot pass. Not for executing already-specified work — implementation, debugging, or code review with no product scope left to decide. Not for a verdict on whether to adopt or switch to a named external technology, library, or platform; that is ce-pov.
- ▌ Ce Compound Refresh 3 · everyinc bundleRefresh 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.
- ▌ Ce Work 3 · everyinc bundleExecute 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.
- ▌ Ce Ideate 3 · everyinc bundleGenerate 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).
- ▌ Ce Plan 2 · everyinc bundleCreate 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.
- ▌ Lfg 2 · everyinc bundleTake 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.
- ▌ Ce Pov 2 · everyinc bundleJudge a supplied subject against the project's evidence and constraints. Use when assessing an external-adoption question, a holistic take on a document, or a supplied approach set. Use for an oracle panel to consult other models and reconcile their opinions. Use ce-explain for understanding and ce-doc-review for findings review.
- ▌ Ce Work 2 · everyinc bundleExecute 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.
- ▌ Ce Debug 2 · everyinc bundleDiagnosis loop for bugs and failing behavior. Use when asked to debug or fix failing or slow behavior.
- ▌ Ce Proof 2 · everyinc bundlePublish, 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 Setup 2 · everyinc bundleCheck Compound Engineering health and repo-local config, or scaffold a Compound Pack with `pack:<id>`.
- ▌ Ce Sweep 2 · everyinc bundleSweep 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.
- ▌ Ce Commit 2 · everyincCreate 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 Ideate 2 · everyinc bundleGenerate 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).
- ▌ Ce Noslop 2 · everyinc bundleRewrite, 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.
- ▌ Ce Bakeoff 2 · everyinc bundleDevelop 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.
- ▌ Ce Dogfood 2 · everyinc bundleHands-off, diff-scoped browser QA of the active branch: maps user flows, drives a real browser, autonomously fixes small breakages with regression tests and commits, judges experience against product personas, and writes a durable dogfood report. Manual invocation only.
- ▌ Ce Explain 2 · everyinc bundleExplain how and why something has its current shape, or what happened over a window of work, grounded in evidence. Use when the user asks for an explanation. Use ce-pov for a judgment or recommendation.
- ▌ Ce Handoff 2 · everyinc bundleCreate 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.
- ▌
- ▌ Ce Compound 2 · everyinc bundleDocument 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.
- ▌ Ce Optimize 2 · everyinc bundleOptimize 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.
- ▌ Ce Strategy 2 · everyinc bundleCreate or update STRATEGY.md. Use when starting a product, adding a strategy doc, or changing direction or roadmap.
- ▌ Ce Prototype 2 · everyinc bundleBuild 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.
- ▌ Ce Babysit Pr 2 · everyinc bundleBabysits 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.
- ▌ Ce Brainstorm 2 · everyinc bundleExplore 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.
- ▌ Ce Doc Review 2 · everyinc bundleReview requirements, plans, or specs with role-specific lenses. Use when the user wants to improve an existing planning document.
- ▌ Ce Test Xcode 2 · everyinc bundleTest iOS apps in a simulator with XcodeBuildMCP. Use when iOS changes need simulator evidence before handoff.
- ▌ Ce Code Review 2 · everyinc bundleReview 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.
- ▌ Ce Test Browser 2 · everyinc bundleRun browser tests for pages affected by the current branch or PR. Use when asked to run or check browser tests for the current change.
- ▌ Ce Product Pulse 2 · everyinc bundleGenerate time-windowed product pulse reports from configured signals.
- ▌ Ce Simplify Code 2 · everyinc bundleSimplify settled, recently changed code for clarity, reuse, quality, and efficiency while preserving behavior. Use after implementation and before review; use ce-debug for bugs.
- ▌ Ce Commit Push Pr 2 · everyinc bundleCommit, push, and open a PR. Use when asked to ship/open a PR, or for PR-description-only flows like writing, rewriting, or describing a PR body.
- ▌ Ce Compound Refresh 2 · everyinc bundleRefresh 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.
- ▌ Ce Resolve Pr Feedback 2 · everyinc bundleResolve PR review feedback. Use when addressing feedback already left on a PR. Not for reviewing the code before feedback exists; that is ce-code-review.
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌
- ▌ Gdoc Comment Extractor · everyinc bundleExtract all comments, suggestions, and tracked changes from a Google Doc and save them as a CSV. Use when the user shares a Google Docs URL and wants to pull out comments, edits, suggestions, or tracked changes. Also triggers on "extract comments", "pull comments from doc", "get suggestions from google doc", "export doc comments", "doc feedback", or "what did the editor say".
- ▌ Hands On Deck · everyinc bundleUse this skill any time a .pptx file is involved in any way — as input, output, or both. This includes reading, analyzing, or extracting content from presentations; editing text, images, styles, or layout of existing decks; creating new slides, shapes, tables, or pictures; reordering, duplicating, or merging slides across decks; and verifying decks visually. Trigger whenever the user mentions a deck, slides, a presentation, or a .pptx filename.
- ▌ Teach · everyinc bundleConstraint-driven teaching at three depths: a 5-Minute Gist (the whole picture in one read), an Expert Briefing (dense one-sitting mental model), or a Full Curriculum (interactive, section-by-section). Use whenever the user wants to learn or understand anything: "teach me X", "explain X", "give me the gist of X", "what's the deal with X", "crash course on X", "briefing on X", "how does X actually work", "help me understand X", "5 min version of X", or when they're prepping for a meeting or conversation on an unfamiliar topic. Even casual asks like "make X make sense", "what's a linter?", or "why is X the way it is" should trigger this. First establish which depth fits, then teach in that mode.
- ▌ Product Launch Video · everyincBuild polished product launch videos in Remotion from brief → storyboard → render → multi-agent review → iterate. Designed for 15-30s social clips for product launches, feature demos, and before/after transformations. Triggers on: product video, launch video, demo video, remotion video, make a video for launch.
- ▌
- ▌ Tend · everyincArm this Claude session as Tend's Claude lane — open the feed in the in-app preview, register presence, and start the wake monitor so queued work activates this thread. Use when Dan says "/tend", "arm tend", "watch the feed", or opens Tend in the preview and wants Claude to take action.
- ▌ Meeting Prep · everyincPrepare a briefing from Monologue notes for an upcoming meeting, including prior context, decisions, unresolved questions, and relevant commitments.
- ▌ Weekly Review · everyincReview a week of Monologue notes to identify themes, decisions, commitments, unresolved items, and useful next steps.
- ▌ Meeting Follow Up · everyincTurn recent Monologue meeting notes into a clear follow-up containing decisions, action items, owners, dates, open questions, and a draft message.
- ▌ Monologue Context · everyincSearch and synthesize the user's private Monologue voice notes when they ask about something they recorded, discussed, decided, or want recalled.
- ▌
- ▌
- ▌
- ▌ Tasks · everyincUse the local `tasks` CLI to read/write `tasks.json` — the offline-demo replacement for Linear. Covers reading issues, posting/editing comments, transitioning issue state, attaching local PRs, and creating follow-up issues. Use when working a ticket through Symphony in offline mode.
- ▌ Commit · everyincCreate well-formed git commits from current changes. Use when staging and committing work-in-progress on the issue branch.
- ▌ Kw Plan · everyincResearch past work and structure a knowledge work plan. Use when starting strategy docs, campaign plans, content briefs, research synthesis, or operational playbooks.
- ▌ Kw Work · everyincExecute a knowledge work plan. Break it into tasks, do the work, and track what happened. Use after planning to actually produce the deliverables.
- ▌ Kw Review · everyincMulti-reviewer quality check for knowledge work. Runs strategic alignment and data accuracy reviewers on plans, briefs, and strategy docs.
- ▌ Kw Compound · everyincExtract and save learnings from a completed knowledge work session. Saves to docs/knowledge/ so future plans automatically find them.
- ▌ Kw Brainstorm · everyincBrain dump and compile knowledge before structuring a plan. Use when starting any non-trivial knowledge work — after a meeting, when tackling a new problem, or when you need to pull together what you know before planning.
- ▌ Kw Confidence · everyincGut-check what you know and don't know before proceeding. Use at any point to assess confidence, surface gaps, and decide whether to proceed or dig deeper.
- ▌ Voice Inbox · everyinc bundleProcess recent Monologue voice notes into a private, sourced inbox of decisions, tasks, ideas, questions, and people follow-ups. Use when a user wants to review recent recordings, clear a voice-note backlog, find commitments, or organize captured thoughts across work and personal contexts.
- ▌ Monologue Notes · everyinc bundleUse when you need to read Monologue notes through the public API, search and list a user's notes, fetch a specific note, paginate through all notes, or pull transcripts and summaries through the Monologue CLI.
- ▌ Topic Synthesis · everyinc bundleSynthesize what a user has said about a topic across multiple Monologue notes, including the central thesis, examples, evolution, contradictions, gaps, and a dated source trail. Use when the user asks to find a theme across recordings, compare their thinking over time, or assemble multi-note context for writing or decisions.
- ▌ Clean Transcript · everyinc bundleClean a supplied transcript, transcript file, or verified Monologue note without changing its meaning. Use when a user wants to remove filler, stutters, repeated phrases, or abandoned false starts; improve punctuation and paragraphing; preserve speaker labels; or prepare a readable transcript while retaining uncertainty, technical details, numbers, and quotations.
- ▌ Weekly Work Update · everyinc bundleDraft an evidence-backed weekly work update from Monologue voice notes. Use when a user wants to review a week, summarize project progress and decisions, identify next steps, blockers, or owners, or prepare a status update from multiple recordings.
- ▌ Morning Note To Work Session · everyinc bundleTurn a recent Monologue morning note into a focused, evidence-backed work-session brief. Use when the user asks what to work on today, wants to start from a morning voice note, or wants decisions, questions, today's tasks, later ideas, and a recommended first task extracted from recent notes.
- ▌ Customer Call To Product Work · everyinc bundleTurn a verified Monologue customer-call recording into evidence-backed product work, such as a bug report, issue draft, investigation brief, or implementation plan. Use when the user asks to connect customer feedback or a support call to a repository, issue tracker, diagnosis, or product change.
- ▌ Mom · everyincReads your writing from a loving, supportive, but not-quite-getting-it perspective. Surfaces where you've lost the general reader.
- ▌ Eli5 · everyincChecks writing for clarity and accessibility. Flags jargon without explanation, hand-wavy process descriptions, and skipped steps. Ensures content is specific enough for experts AND clear enough for newcomers. Use when reviewing technical or process-heavy writing.
- ▌ Panel · everyincConvene a panel of reviewers to analyze a draft from multiple perspectives, then synthesize their feedback into consensus findings, productive tensions, and prioritized recommendations.
- ▌ Debate · everyincRun a multi-round deliberation between reviewers. Unlike /panel (which synthesizes), /debate has reviewers respond to each other's arguments across rounds until tensions resolve or reach acknowledged stalemate.
- ▌ Sorkin · everyincChecks pacing and momentum. Is there enough forward motion? Are you walking and talking or standing still?
- ▌ Asshole · everyincReads your writing through the meanest, least-charitable lens. Challenges every claim, questions every assumption, pokes holes in the logic. Use for later drafts when you want hard feedback.
- ▌ Sedaris · everyincFinds the funny. Looks for moments that could be mined for humor, absurdity, or self-deprecation.
- ▌ Dev Edit · everyincReview a draft for big-picture issues—argument, structure, stakes, and payoff. Invoke with /dev-edit after drafting or with any draft the user provides.
- ▌ Vonnegut · everyincApplies Vonnegut's 8 rules for writing. Start close to the end, give characters wants, be a sadist, etc.
- ▌ Hemingway · everyincCuts ruthlessly. Flags every adjective, adverb, and unnecessary word. Demands you kill your darlings.
- ▌ Hitchcock · everyincReviews for suspense and tension. Where's the bomb under the table? What does the reader know that someone doesn't?
- ▌ Line Edit · everyincDeep, rigorous pass for sentence- and word-level issues. Delivers a clean draft with a summary of changes. Invoke with /line-edit after dev-edit or with any draft.
- ▌ Guardrails · everyinc bundleScan any Every draft for recurring editorial-review failures: clarity and evidence gaps, argument problems, mechanics red flags, second-order AI tells, and, for Working Overtime only, column-specific voice tics and structural throat-clearing. Use when reviewing or polishing Every writing before submission. Reports findings with line-level diagnoses and suggested fixes. Pairs with ai-check and every-style.
- ▌ Ce Plan · everyinc bundleCreate 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.
- ▌ Ce Skill Work · everyinc bundleApplies this repository's skill-authoring standard as a procedure. Use for any change to, or judgment about, a file under skills/** — a SKILL.md, a reference, a persona prompt, a bundled script's instructions: creating a skill, editing one, reviewing a skill change, or acting on review feedback (human or bot) about one. Not for src/, tests/, or scripts/ code.
- ▌ Cw Mom · everyincReads your writing from a loving, supportive, but not-quite-getting-it perspective. Surfaces where you've lost the general reader.
- ▌ Cw Bluf · everyinc bundleDiagnose whether the most important idea in an article, essay, post, memo, section, paragraph, or sentence appears where it best serves the reader. Use for BLUF checks, buried or misplaced ledes, slow or misleading openings, intro drift, competing main ideas, and requests to get to the point or find the real opening. Compare what the opening foregrounds with what the artifact actually delivers, judge whether any delay is earned, and recommend the smallest structural move. Diagnose by default; rewrite only when asked.
- ▌ Cw Hook · everyincGenerate 3 hook options tailored to your content. Invoke with /cw-hook or /cw-hook [topic/context].
- ▌ Cw Save · everyincCapture a confirmed writing preference, editorial lesson, recurring failure pattern, or workflow improvement in the right durable context file. Use when the user asks to save, remember, codify, or turn a repeated correction into a rule.
- ▌ Cw Draft · everyincTurn an outline, notes, source material, or partial prose into a complete draft while preserving the writer's voice, thesis ownership, and source provenance. Use when the user asks to draft a piece or section.
- ▌ Cw Panel · everyincConvene a panel of reviewers to analyze a draft from multiple perspectives, then synthesize their feedback into consensus findings, productive tensions, and prioritized recommendations.
- ▌ Cw Debate · everyincRun a multi-round deliberation between reviewers. Unlike /cw-panel (which synthesizes), /cw-debate has reviewers respond to each other's arguments across rounds until tensions resolve or reach acknowledged stalemate.
- ▌ Cw Reader · everyincReview copy as an intended reader encountering it for the first time, with no access to the writer's unstated context. Identify confusing language, missing setup, assumed knowledge, broken expectations, trust-eroding or off-putting moments, and points where the reader may stop. Use for cold reads, fresh-eyes reviews, first-time-reader perspectives, reader-journey checks, or feedback on what feels confusing, missing, alienating, or hard to follow.
- ▌ Cw Scribe · everyincRoute open-ended writing work through the smallest useful Compound Writing workflow. Use when the user wants to start, continue, finish, or improve a piece and has not named a more specific skill.
- ▌ Cw Sorkin · everyincChecks pacing and momentum. Is there enough forward motion? Are you walking and talking or standing still?
- ▌ Cw Thesis · everyincGenerate 3 thesis options tailored to your content. Invoke with /cw-thesis or /cw-thesis [topic/context].
- ▌ Cw Tracks · everyincFinds where the writing shows its tracks—scaffolding, throat-clearing, process narration, and arrival sequences that should be erased now that the destination is clear.
- ▌ Cw Analogy · everyincGenerate analogy options to explain a concept. Invoke with /cw-analogy or /cw-analogy [concept to explain].
- ▌ Cw Asshole · everyincReads your writing through the meanest, least-charitable lens. Challenges every claim, questions every assumption, pokes holes in the logic. Use for later drafts when you want hard feedback.