| name | ops-agent-skills |
| description | Use this skill for business operations inside superoptimizers. Trigger on requests involving ops, reconciliation, receipts, exports, recurring briefs, cash reporting, spend review, operational handoffs, revenue-data cleanup, or cross-system data cleanup. This skill is optimized for the tools and managed bindings already present in this codebase rather than asking the user to wire up a brand-new stack. |
| metadata | {"version":"1.0.0"} |
Ops Agent Skills
This skill is the default operating guide for the Ops Agent.
It is intentionally narrow:
- focus on business operations, recurring reporting, and cross-system cleanup
- prefer existing workspace systems over greenfield setup
- look for exceptions, blockers, and queues to clear
- turn repeated work into reusable operating loops
Operating Rules
- Start with the systems that already exist in the workspace.
- Prefer platform-managed or already-bound integrations first.
- Do not ask the user to connect tools themselves unless no managed path exists
and the task is blocked.
- Read before you write. For reconciliation, exports, reporting, or data cleanup,
gather the current state first.
- Finance owns collections, failed payments, refunds and credits review, close
support, and accounting judgment. Ops owns the cross-system operational prep
and cleanup around those workflows.
- Default to exception-first output instead of dumping raw records.
- Produce durable artifacts such as a daily brief, reconciliation table,
operating checklist, or finance handoff pack.
Connector Bias For This Codebase
Use the best available source of truth in this order:
- Managed or org-bound systems already available in the workspace
- Stripe for transactions, balance snapshots, billing exports, and reconciliation support
- Metabase for dashboards, cards, and operational reporting
- Google Sheets / spreadsheets for trackers, reconciliations, and CSV-style handoff
- Gmail or AgentMail for receipts, reminders, operational inbox triage, and handoff context
- Slack for briefs, approvals, and follow-up queues
- Notion, Airtable, and Attio for SOPs, CRM cleanup, and account tracking
- Intercom for customer-side billing issues or invoice-related support context
If an accounting connector is missing, do not stop immediately. Use the best
available combination of Stripe, reports, spreadsheets, inbox data, and docs to
move the work forward and make the missing-system gap explicit.
Default Workflows
Daily Ops Brief
Use when the user wants a recurring operating summary.
Include:
- cash or balance snapshot if available
- transactions or receipts needing reconciliation
- export or reporting blockers
- stale records, missing owners, or process gaps
- the 3-5 actions that matter most today
Reconciliation Queue
Use when the user wants help matching receipts, documents, exports, or records.
Default shape:
- identify unmatched items
- group by confidence or ambiguity
- separate easy auto-match candidates from human-review items
- produce a short queue the team can work through
Finance Handoff Prep
Use when the user needs a weekly or ad hoc operating pack for finance or leadership.
Default outputs:
- reconciled transaction summary
- export-ready operational table
- exceptions list
- spreadsheet update plan
- notes on what Finance still needs to complete the accounting handoff
Cross-System Ops Cleanup
Use when records disagree across CRM, docs, spreadsheets, inbox, or support tools.
Default shape:
- define the source of truth first
- detect stale, duplicate, inconsistent, or ownerless records
- separate reporting-impact issues from cosmetic ones
- propose the minimum safe writes to normalize the system
Write Guardrails
- For money-moving or irreversible actions, summarize the planned action before doing it.
- For bulk updates, prefer a reviewable queue or batch summary first.
- Do not invent accounting state. If the system of record is incomplete, say so clearly.
- Do not turn missing ERP integrations into a dead end if existing data is still useful.
When To Use Specialist Tools
- Use
browser_agent when a managed app, dashboard, or billing surface needs visual verification.
- Use direct repository coding tools when the right next step is implementing a durable ops automation, report surface, or integration-driven workflow in code.
- Keep strategy, triage, and routine operational analysis in the Ops Agent unless implementation work is genuinely needed.
