EveryInc

Run browser tests for pages affected by the current branch or PR.

Babysits or watches an open GitHub PR until merge-ready, continuously reacting to new review comments and CI failures throughout the PR's life. Use when asked to 'babysit the PR', 'watch the PR', monitor, or keep an eye on a PR over time — not a one-shot request to resolve review comments or debug one CI failure (those are separate skills). GitHub only, including GitHub Enterprise.

Commit, 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.

Diagnosis loop for bugs and failing behavior. Use for errors, stack traces, regressions, failed tests, issue-tracker bugs, stuck investigations after failed fixes, or asks to debug/fix a bug.

Resolve PR review feedback. Use when addressing review comments, resolving review threads, or fixing code-review feedback.

Check Compound Engineering health and repo-local config.

Run the full hands-off engineering pipeline from planning through a green PR.

Explore vague or ambitious ideas into a right-sized requirements-only unified plan. Use when the user wants to brainstorm, think through scope, decide what to build, or needs collaborative product framing before planning. Also use when the user must scope work in territory they say they do not know ("I know nothing about X but need to...") or asks for a blindspot pass — mapping the decision surface before questions begin. Not for executing already-specified work — direct implementation, debugging, or code review where no product scope is left to decide. Not for a decisive verdict on whether to adopt or switch to a specific external technology, library, or platform — brainstorming scopes what to build, not whether to commit to an outside option.

Discover and install vetted Every Skill packages through the Every Skill MCP server.

Submit a skill to the Every Skill registry. Use this skill when you've created a useful skill (prompt, workflow, or agent instruction set) and want to share it with the community. All submissions are reviewed by AI and approved by humans before going live.

This skill should be used when writing social media content for Every (Twitter/X and LinkedIn). It provides the complete Every social style guide including voice, tone, post archetypes, structural patterns, and platform-specific guidance. Triggers on requests to write tweets, X posts, LinkedIn posts, social copy, or when the user asks for Every's social voice.

Transform a team-built, use-case-specific skill into a generalized, onboardable skill that any Plus One bot can adopt. Trigger when the user asks to generalize a skill, make a skill distributable, or prepare a skill for the skill store.

Automatically detects AI writing patterns and produces a sequential checklist for manual editing in Google Docs. Scans for AI tells—generic phrasing, stock openers, formal transitions, correlative constructions, vague authority claims, and other patterns—then outputs the revised text first and technical details second. Auto-triggers when generating, editing, reviewing, or polishing any written content for Every.

Fast first-pass editorial assessment for Every drafts. Use when an editor receives a draft article and needs to quickly determine if it has the essential building blocks (thesis, promise, hook, stakes) and aligns with Every's strategy and voice before proceeding to deeper editing. Returns a tight, skimmable assessment with clear next steps.

Check text against Every's editorial style guide and return a checklist of style violations. Use when someone asks to check, review, or validate text against Every's style guide, or when editing content for Every. Returns only violations—does not auto-fix.

A ready-to-use prompt for automating daily social media content sourcing in Cowork. Scans your Slack channels, surfaces the best content from the last 24 hours, drafts posts for X and LinkedIn, runs everything through a built-in AI-writing detector, and saves drafts for human review. Runs on autopilot as a scheduled task — no auto-publishing, ever.

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

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

Review a draft for big-picture issues—argument, structure, stakes, and payoff. Invoke with /dev-edit after drafting or with any draft the user provides.

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

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

Cuts ruthlessly. Flags every adjective, adverb, and unnecessary word. Demands you kill your darlings.

Reviews for suspense and tension. Where's the bomb under the table? What does the reader know that someone doesn't?

Deep, 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.

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

Extract and save learnings from a completed knowledge work session. Saves to docs/knowledge/ so future plans automatically find them.

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

Research past work and structure a knowledge work plan. Use when starting strategy docs, campaign plans, content briefs, research synthesis, or operational playbooks.

Multi-reviewer quality check for knowledge work. Runs strategic alignment and data accuracy reviewers on plans, briefs, and strategy docs.

Execute a knowledge work plan. Break it into tasks, do the work, and track what happened. Use after planning to actually produce the deliverables.

Land a local PR by resolving conflicts and squash-merging the feature

Merge local `main` into the current branch and resolve merge conflicts

Finalize the local feature branch and create or update a local PR record on

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

Create well-formed git commits from current changes. Use when staging and committing work-in-progress on the issue branch.

Your AI CFO for bootstrapped startups, named after Charlie Munger who embodied the principle that capital discipline is a competitive advantage. Provides financial frameworks for cash management, runway calculations, unit economics (LTV:CAC), capital allocation, hiring ROI, burn rate analysis, working capital optimization, and forecasting. Use for questions like "should we make this hire?", "how much runway do we need?", "what metrics should I track?", "how do I forecast revenue?", or any strategic financial decision at a self-funded company.

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

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

Use 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 with a Monologue Notes API token.

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

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