ChiefOSby ConversintStart free
Menu
← Back to the library
Meetings and learning

Meeting followup

Coordinate Conversint's daily operating queue across CRM, Gmail, Calendar, active project ledgers, customer files, Drive Watch review items, and GTM workflows. Use /operator when Patrick or Daniel asks what needs attention today, wants a sales/follow-up queue, deal strategy, account monitoring, meeting prep, post-call routing, active customer or pre-sales context, stale CRM/project hygiene, reviewed draft creation, a weekly retro, or to reconcile recent Drive, Conversint email, and ChiefOS commit evidence into clear CRM, project, and customer-knowledge updates. This skill orchestrates existing chiefOS skills; it does not replace /crm, /customer-knowledge, /gmail, /calendar, /project-manager, /prep-cold-outreach, /prep-lead, or /marketing-learning-loop.

Works with the context you provideVersion 2.0.2Historical revision

# /operator - Conversint operating queue

Use this skill as the coordinator above the existing chiefOS skills. Its job is to decide what deserves attention, assemble the evidence, and route the next action to the right skill or human review gate.

Shared cross-skill ownership boundaries live in `./references/dependencies/conversint-current/references/skill-operating-standards.md`. Keep this skill as an operating surface; update the shared reference when a durable routing convention changes.

Default posture: **read first, recommend clearly, write only when the user explicitly asks for a write-mode action.**

`reconcile` is the narrow exception: it is an explicitly requested, evidence-backed write mode. It may apply clear CRM, Project Manager, and customer-knowledge updates through their owning skills, but it does not send mail, create customer-facing artifacts, alter structural org context, upload customer source material to Drive without separate authorization, or infer a business decision from a weak signal.

Mode selection

Pick the mode from the first positional argument, or infer it from the user's request:

| User intent | Mode | Then load | |---|---|---| | "What should I do today?", morning queue, daily operating queue, "operator today" | `today` | `./references/today.md` | | Sales pipeline, prospects, pre-sales opportunities, CRM opportunities, stale opps, scan-to-outreach queue | `sales` | `./references/sales.md` | | Prep today's calls or one customer/prospect meeting | `brief` | `./references/brief.md` | | Create reviewed Gmail drafts, call scripts, or follow-up drafts from approved queue items | `draft` | `./references/draft.md` | | Weekly learning, what worked, signal/message tuning, operating retro | `retro` | `./references/retro.md` | | Apply approved CRM or project-manager updates from an operator queue | `capture` | `./references/capture.md` | | Reconcile last-24-hour Drive, sent/received work email, and ChiefOS commit evidence into CRM, project, and durable customer context | `reconcile` | `./references/reconcile.md` |

If the user gives no mode, use `today`.

Operating model

`/operator` composes existing systems:

- CRM Google Sheet via `/crm` and `lib/crm.py`: sales pipeline state. - Gmail via `/gmail`: relationship evidence and drafts. - Calendar via `/calendar`: meetings and no-shows. - Project ledgers via `/project-manager`: delivery and internal operating work. - Customer knowledge bases and source ledgers via `/customer-knowledge`: durable customer facts and provenance. - Customer folders under `customers/`: artifacts and source context. - `/value-signal-scan`, `/prep-cold-outreach`, and `/prep-lead`: prospecting and sales-prep lanes. - `/drive-watch`: Drive-ingested review queues and org-context drift items. - `/marketing-learning-loop`: durable marketing and GTM lessons after review.

Treat `/operator` output as an operating surface, not a second CRM, task system, or customer deliverable.

For any item that came from a customer/stakeholder request or may be satisfied by repo-tracked changes, use repo-root `./references/dependencies/conversint-current/references/request-traceability.md` to route the request trail and eventual task-to-commit evidence to the owning skill. `/operator` should surface missing traceability; it should not create an operator-only paper trail.

Ownership boundaries

`/operator` is a coordinator. It should summarize, prioritize, and route; it should not become another implementation of sibling skills.

| Area | Owner | `/operator` role | |---|---|---| | Sales lifecycle, opportunity stages, next actions, relationship activity | `/crm` | Read CRM state, identify stale or important records, propose `/crm log` or `/crm capture` updates | | Durable customer facts, source provenance, conflicts, and open questions | `/customer-knowledge` | Read current customer context, identify clear new evidence, and route `capture` or `refresh` through the owning skill; never edit its artifacts directly | | Post-Won delivery work, internal operating tasks, blockers, review waits | `/project-manager` | Read reports/summaries, promote important waits into the daily queue, propose `/project-manager capture` or `status` updates | | Drive polling, meeting-note archival, org-bundle drift review, Drive Watch audit state | `/drive-watch` | Read `/drive-watch report` output or pending-review pointers, surface review work, route actual review to `/drive-watch review` | | Gmail search, compose, draft, send, labels | `/gmail` | Use narrow Gmail reads for evidence, route draft/send actions through `/gmail`; never send from `/operator` | | Calendar agenda, event creation, RSVPs | `/calendar` | Read agenda for briefs; route any event/RSVP changes through `/calendar` | | Prospect research and cold outreach drafting | `/value-signal-scan`, `/prep-cold-outreach`, `/prep-lead` | Decide which lane should run next; do not duplicate deep prep or contact discovery | | Facebook/Instagram demand tests, Meta launch readiness, ad reporting, iteration | `/fb-ads` | Surface setup blockers and learning-test next actions; route campaign production, launch readiness, reporting, and iteration to `/fb-ads`; never publish or spend | | Website delivery, website feedback, customer-site implementation | `/website-refresh`, `/website-feedback`, `/project-manager` | Surface active website blockers and review waits; route raw feedback and review loops through `/website-feedback` | | Customer skill-build review findings | `/skill-dev-feedback` | Surface open feedback ledgers or review waits; route item-level feedback capture/status/report to `/skill-dev-feedback` | | Admin, legal, accounting, contracts, tax, invoicing | `/project-manager`, `/legal-research`, `/accounting-research` | Surface operating blockers such as Stripe/tax setup; route research or durable tasks to the owning skill | | Marketing measurement, campaign learning, ROI proof | `/analytics-tracking`, `/marketing-learning-loop`, `/marketing-roi` | Surface tracking/learning/ROI gaps once a campaign or website change is live; route analysis to the owning skill |

If an item needs durable state, the next action should name the owning skill. Example: "Capture this via `/project-manager capture`" or "Log this via `/crm log`." Do not create an operator-only backlog.

Always load first

For every run, read:

  • `./references/dependencies/conversint-current/references/active-projects.md`
  • `./references/dependencies/conversint-current/references/org/current-state.md`
  • `./references/dependencies/conversint-current/references/org/constraints.md`
  • `./references/dependencies/conversint-current/references/org/anti-patterns.md`

When the run touches sales, CRM, active delivery, Gmail, Calendar, or project updates, also read the relevant skill instructions before acting:

  • `./references/dependencies/conversint-source/.claude/skills/crm/SKILL.md`
  • `./references/dependencies/conversint-source/.claude/skills/customer-knowledge/SKILL.md`
  • `./references/dependencies/conversint-source/.claude/skills/gmail/SKILL.md`
  • `./references/dependencies/conversint-source/.claude/skills/calendar/SKILL.md`
  • `./references/dependencies/conversint-source/.claude/skills/project-manager/SKILL.md`
  • `./references/dependencies/conversint-source/.claude/skills/drive-watch/SKILL.md`
  • `./references/dependencies/conversint-source/.claude/skills/fb-ads/SKILL.md`
  • `./references/dependencies/conversint-source/.claude/skills/skill-dev-feedback/SKILL.md`
  • `./references/dependencies/conversint-source/.claude/skills/website-feedback/SKILL.md`
  • `./references/dependencies/conversint-source/.claude/skills/prep-cold-outreach/SKILL.md`
  • `./references/dependencies/conversint-source/.claude/skills/prep-lead/SKILL.md`

Do not load every sibling skill reflexively. Load the one that owns the action you are about to recommend or execute.

Hard gates

- Do not send email, schedule-send email, post to social, call anyone, RSVP, or send calendar updates. In `reconcile`, a new or changed dated project task may use Project Manager's existing reminder helper; do not create Calendar events directly or perform a historical reminder sweep. - Do not write CRM, customer-knowledge, or project-manager updates unless the user asked for `capture`, `reconcile`, or otherwise explicitly approved the exact update batch. - Do not run client-facing deliverable skills unattended. `/prep-lead`, `/scope-engagement`, `/research-usecase`, `/screen-vendors`, and `/evaluate-vendors` require their own skill-specific choices and gates. - Do not put project work into Patrick's personal `/todos`. - Do not turn generated queue items into durable project tasks unless the user approves capture through `/project-manager`. - Do not use banned terms in buyer-facing draft text. - Fetch `https://conversint.ai/services` live before mapping a prospect pain to a Conversint service.

Priority rules

Rank work by:

  1. Client/prospect commitments due today or overdue.
  2. Meetings happening today that need context.
  3. Sales opportunities with stale next actions or recent buying signals.
  4. Active project blockers and review waits.
  5. Drafts ready for human review.
  6. Hygiene issues that will cause rot if ignored.
  7. Longer-horizon learning or process improvements.

For ads specifically, treat Meta setup blockers, budget approvals, launch readiness, and campaign-learning reviews as operator-visible items. The owning skill remains `/fb-ads`.

For website delivery, treat preview review waits, Vercel feedback groups, deployment blockers, domain/DNS access, and rollback-plan gaps as operator-visible items. Implementation remains with the website/Vercel skills and durable task state remains with `/project-manager`.

Respect the founder capacity rail in `./references/dependencies/conversint-current/references/org/constraints.md`. A useful queue is short enough to act on.

Output style

Be concrete and source-backed. Each recommendation should answer:

  • what to do;
  • why now;
  • who owns it;
  • what source supports it;
  • which skill or manual action should handle it next.

When uncertain, label the uncertainty instead of filling gaps.

Next

Load the reference file for the selected mode and follow it.