EveryInc

Commit, push, and open a PR with an adaptive, value-first description that scales in depth with the change. Use when the user says "commit and PR", "ship this", "create a PR", or "open a pull request". Also handles description-only flows ("write a PR description", "rewrite the PR body", "describe this PR") without committing or pushing.

Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit format otherwise.

Structured code review using tiered persona agents, confidence-gated findings, and a merge/dedup pipeline. Use when reviewing code changes before creating a PR.

Document a recently solved problem to compound your team's knowledge

Create structured plans for multi-step tasks -- software features, research workflows, events, study plans, or any goal that benefits from breakdown. Also deepens existing plans with interactive sub-agent review. Use when the user says 'plan this', 'create a plan', 'how should we build', 'break this down', or when a brainstorm doc is ready for planning. Use 'deepen the plan' or 'deepening pass' for the deepening flow. For exploratory requests, prefer ce-brainstorm first.

Capture a visual demo reel (GIF, terminal recording, screenshots) for PR descriptions. Use when shipping UI changes, CLI features, or any work with observable behavior that benefits from visual proof. Also use when asked to add a demo, record a GIF, screenshot a feature, show what changed visually, create a demo reel, capture evidence, add proof to a PR, or create a before/after comparison.

[BETA] Dogfood the active branch end-to-end as a QA engineer. Diffs the branch against main, builds an exhaustive browser test matrix of every change (full user journeys, not just features), drives the app with agent-browser, then auto-fixes issues, adds regression tests, and commits each fix until the matrix is green. Use when you want a hands-off 'test everything we just built and make it actually work' pass before shipping.

Explore requirements and approaches through collaborative dialogue, then write a right-sized requirements document. Use when the user says "let's brainstorm", "what should we build", or "help me think through X", presents a vague or ambitious feature request, or seems unsure about scope or direction -- even without explicitly asking to brainstorm.

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.

Investigate growth, activation, retention, conversion, funnel bottlenecks, and product-value realization for apps and websites using analytics, database or warehouse, billing, release, and support data. Use when asked why users do not activate, return, convert, collaborate, or retain; to measure build impact; to explain churn-like behavior; or to find concrete growth levers from product data.

Perform write operations on Intercom conversations and Help Center articles via REST API. Use when you need to reply, add notes, assign, close, snooze, or reopen conversations, or create/update Help Center articles. Trigger when: user says 'reply to intercom', 'close conversation', 'add note', 'update help article', 'assign conversation', or any Intercom write operation.

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