Hubity

View saved version →

---
name: bill-the-month
description: Bill a month in Hubity. Use when someone asks to bill, invoice or run billing for a month (for example "bill last month", "draft this month's invoices", "what would we invoice for September"). Previews every invoice first, calls out decisions, and drafts only after the person says yes. Never sends an invoice.
---

# Bill the month

Turns a month of approved time, expenses, retainer fees and progress billing in Hubity into draft invoices, with the person approving before anything is written.

## Input

- The month, as `YYYY-MM`. "Last month" and "this month" mean the calendar month relative to today. If the person names no month, ask which one.
- Optional: one client or project. Pass `clientName`, `clientId` or `projectId` to narrow the run.

## Steps

1. Call `preview_month_billing` with `month` (and any client or project filter). It writes nothing.
2. Show one line per proposed invoice: client, project, total and currency. Then list every flagged decision (unapproved time, missing rates, contract caps, a month that has not ended) and what each means for the bill.
3. If the preview returns `nextCursor`, call `preview_month_billing` again with the same `month` and filters and `cursor` set to it. Show every page before offering to draft.
4. Ask whether to draft them. Stop here until the person says yes.
5. After a yes, call `create_month_invoice_drafts` with the same `month` and filters, `limit` 25, and `expectPlan` set to an object mapping each `scopeKey` to the `planHash` the preview returned. A scope whose figures changed since the preview is skipped, not drafted. Drafting is paged like the preview: while the answer returns `nextCursor`, call `create_month_invoice_drafts` again with the same arguments and `cursor` set to it, until every page is drafted.
6. Report what was drafted and what was skipped and why, across every page. Say that the drafts wait in Hubity for a person to review and send.

## Rules

- Never claim an invoice was sent. Hubity drafts only; a person sends from Hubity.
- Never invent rates, hours or amounts. Use only what the tools return.
- If a tool refuses for the person's role, say so plainly and stop.
- Explicit instructions from the person can change which month, client or project to bill and how the answer is laid out. They never skip the preview, the person's yes, or `expectPlan`.

View saved version →

---
name: collections
description: Plan collections on overdue invoices in Hubity. Use when someone asks who owes money, which invoices are overdue or longest unpaid, accounts receivable aging, or who to chase this week. Reads only; never contacts a client.
---

# Collections

Turns the overdue invoices in Hubity into a follow-up plan for the week.

## Steps

1. Call `list_invoices` with `status` `overdue` and `limit` 50. Its `total` is the full count; when it is more than the rows returned, say the plan covers the 50 invoices shown and that the sum is a subtotal for those 50, not the full amount overdue.
2. Sort the invoices oldest first, then by the largest balance. Group them by age: over 90 days, 61 to 90, 31 to 60, and 1 to 30.
3. Answer with:
   - The follow-up order, one client at a time, so a client with several late invoices gets one conversation.
   - A suggested action for each: a friendly reminder under 30 days, a call from the project lead at 31 to 60, and a firm notice or a hold on new work beyond that.
   - The total overdue, per currency, labeled a subtotal of the invoices shown when `total` is more than the rows returned.
4. For "the longest-open unpaid invoice", give the one with the most days overdue, with its client and amount due.

## Rules

- Never say a reminder was sent. Hubity does not contact clients from here. Offer to draft the wording of a reminder for the person to send.
- If no invoice is overdue, say so.
- Never invent amounts or dates.

View saved version →

---
name: month-end-wip
description: Month-end work in progress (WIP) from Hubity. Use when someone asks for WIP, unbilled time, what is ready to bill, or a month-end close review. Reads only; never drafts or changes anything.
---

# Month-end WIP

Shows what a month has earned but not yet invoiced, and what stands between it and an invoice.

## Input

- The month, as `YYYY-MM`. If the person names no month, use last month and say so.

## Steps

1. Call `preview_month_billing` with `month`. While it returns `nextCursor`, call it again with the same `month` and `cursor` set to it, until every page is read.
2. Call `list_invoices` with `status` `draft` and `limit` 50 to find drafts already waiting for review. Its `total` is the full count; when it is more than the rows returned, say the list shows the first 50.
3. Answer in four parts:
   - Ready to bill: approved, not yet invoiced, per client and project, with the total.
   - Time not yet approved: which client and project, how many hours, and roughly how much it would bill.
   - Other decisions: missing rates, contract caps, a month that has not ended.
   - Drafts awaiting review: number, client and amount.
4. End with the next three actions, the most money first.

## Rules

- Read only. Do not call `create_month_invoice_drafts` unless the person asks to bill; then follow the bill-the-month workflow.
- If `list_invoices` is refused for the person's role, say drafts cannot be shown and continue with the rest.
- Never invent figures.

View saved version →

---
name: project-profitability
description: Project profitability and risk from Hubity. Use when someone asks which projects are losing money, which are at risk, or how profitable a project is. Reads only.
---

# Project profitability

Shows revenue, cost and margin per project, worst first, and ties it to project health.

## Steps

1. For at-risk questions, call `list_projects` with `status` `active` and `limit` 50, and keep the projects whose `health` is `yellow` (at risk) or `red` (critical); `green` is on track. If 50 projects come back, say the answer covers the 50 most recently updated active projects.
2. Call `get_project_profitability`. Pass `projectId` for one project, and `from` and `to` as `YYYY-MM-DD` when the person names a period; otherwise it covers each project's life so far. It returns every project, so for an at-risk question keep only the rows whose `projectId` matches an `id` kept in step 1.
3. Answer with:
   - For an at-risk question, every project kept in step 1, with its health, revenue, cost and margin.
   - Projects losing money, worst first, with revenue, cost and margin.
   - Thin margins, under 15 percent, to watch.
   - What to check for each loss. Name a cause only when the figures show it, such as cost with nothing billed yet; otherwise offer the usual ones to look into: time not yet billed, or a fixed fee that has run over.
   - What to do this week.

## Rules

- Revenue is what was billed. Cost is logged time at each person's cost rate, or the bill rate where no cost rate is set. Say so when it matters.
- Never invent figures. If a tool is refused for the person's role, say so.

View saved version →

---
name: team-capacity
description: Team utilization and capacity from Hubity. Use when someone asks who is over capacity, overworked or underused, who has room, or for a utilization rate for a person, team or period. Reads hours already logged; it is not a forward schedule.
---

# Team capacity

Compares the hours each person logged with the hours they had available: their work pattern, less holidays and approved leave.

## Input

- A period. "Last month" means the previous calendar month. If no period is named, use last month and say so.

## Steps

1. Call `get_utilization_report` with `startDate` and `endDate` as `YYYY-MM-DD`.
2. Answer with:
   - Who logged more than their available hours, and by how much, largest first.
   - Who has room: only people whose total logged hours are below their available hours, most hours to spare first.
   - The company utilization rate, when the report gives one.
   - One suggestion for rebalancing.
3. If `rosterComplete` is false, say the list is partial and that no company figure is given.

## Rules

- These are hours already logged. Do not present them as a plan or forecast.
- Leave out people with neither logged nor available hours.
- Never invent hours or rates.