Update to Hubity

{
  "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.",
  "included_files": [],
  "name": "project-profitability",
  "skill_md_contents": "---\nname: project-profitability\ndescription: 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.\n---\n\n# Project profitability\n\nShows revenue, cost and margin per project, worst first, and ties it to project health.\n\n## Steps\n\n1. 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.\n2. 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.\n3. Answer with:\n   - For an at-risk question, every project kept in step 1, with its health, revenue, cost and margin.\n   - Projects losing money, worst first, with revenue, cost and margin.\n   - Thin margins, under 15 percent, to watch.\n   - 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.\n   - What to do this week.\n\n## Rules\n\n- 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.\n- Never invent figures. If a tool is refused for the person's role, say so.\n"
}