Every

View saved version →

---
name: every-ai
description: Manage a connected Every workspace — sales pipeline, people and companies, proposals, invoices, payments, Gmail, calendar, custom fields, scheduled tasks, and recurring billing for a service business. Use for "who owes me money?", lead and deal follow-ups, creating or sending invoices and proposals, moving deals through the pipeline, converting an accepted proposal to an invoice, recording completed payments, drafting or sending email from the user's Gmail, checking or scheduling calendar events, tracking a custom property on a person/company/deal, setting up a recurring reminder or routine, recurring invoice schedules, the daily brief, Every's home and record panels, prospect review, and financial reports. Do not use for connecting or authenticating Every, for a different business than the connected workspace, for charging or collecting money, or for general accounting and tax advice.
metadata:
  short-description: Run your service business in Every
---

# Every

## Overview

Every is an AI business manager for service businesses: one connected workspace for the sales pipeline (deals), the People and Companies the business works with, proposals, invoices, and payments. This skill teaches the reliable way to chain Every's tools — resolve records first, state what will change, confirm anything a client will see, then act and echo the result.

## Prerequisites

- The Every plugin is connected and the user is signed in. If a call fails unauthenticated, tell the user to reconnect Every from the plugin's settings.
- When currency, tax, or timezone matters, call `business_settings` first. Use `get_home` for first-time orientation in a new workspace.
- If a tool returns `signup_incomplete`, or the user asks to finish signing up, call `get_signup_status`, show the suggested organization name, and call `complete_signup` once with only the values the user confirmed. `get_started` and `save_business_info` do not complete signup.

## Required workflow

**Follow these steps in order. Do not skip steps.**

1. **Resolve the records.** Use list/view tools to find the exact records involved — `list_companies` / `list_people` for a named client, `view_proposal` / `view_invoice` for a document number (they accept the number, e.g. PROP-0007 or INV-005). Act only with IDs the tools return — never invent one. If a name matches more than one record, show the candidates and ask. If nothing matches, say so and offer to create it; don't guess a different record.
2. **State the mutation.** Before any write, say exactly what will be created or changed, with amounts and recipients verbatim.
3. **Confirm consequences.** Sending (invoices, proposals, email), deleting, voiding, and recording payments are visible to real clients or change financial records — get the user's explicit yes first, even if the user said not to check with them.
4. **Execute with complete inputs**, then **echo the result**: number, status, total, and link, and suggest the natural next step.

## Write confirmations and approvals (server-enforced)

- **Ordinary writes** (create/update a proposal, invoice, deal, person, company; convert a proposal) may return "This changes your data, so it needs confirming. Re-run this exact call with confirmation=\"…\"". Nothing was changed. When the user has already asked for exactly this change in this conversation (e.g. "draft Acme a proposal", "convert PROP-0007"), re-run the identical call with that phrase and continue. If the user did not ask for it, show the change and ask first.
- **Sends and destructive actions** (`send_invoice`, `send_proposal`, `send_email`, deletes, voids, cancellations, `run_recurring_invoice_now`) are held until the owner approves them in the Every app. Always call `preview_document_send` first for invoices/proposals, show the To/CC it returns, and get the user's explicit yes. If the tool reports the action still needs approval, tell the user to approve it in Every and then retry the same a

Preview of the first 4,000 characters. Read full instructions →