Update to Billabex

{
  "description": "Review tasks created when the autonomous Billabex agent is blocked, explain the missing decision or information, and help the user respond or cancel a task. Use for blocked accounts, pending questions, requested approvals, or task follow-up.",
  "included_files": [],
  "name": "triage-account-tasks",
  "skill_md_contents": "---\nname: triage-account-tasks\ndescription: Review tasks created when the autonomous Billabex agent is blocked, explain the missing decision or information, and help the user respond or cancel a task. Use for blocked accounts, pending questions, requested approvals, or task follow-up.\n---\n\n# Triage Account Tasks\n\n1. Resolve the organization if needed, find the customer with `list-accounts`, then use `list-account-tasks` and `get-account-task` to inspect tasks created because the agent needs user input.\n2. Summarize what is blocking the autonomous payment follow-up, what is requested, why it matters, and the related account or balance context.\n3. Prioritize tasks by urgency and financial exposure. Propose the minimum response needed to unblock the agent.\n4. Keep the review read-only. Use `add-account-task-text-interaction` only when the user explicitly provides or approves the exact free-form response.\n5. After explicit user approval, record the decision with `answer-account-task`: pass `accountTaskId` and `answer`, whose `kind` matches the decision the task awaits (`eligibility`, `contact-change`, `first-outreach`, `contact`, `next-action`, `payment-arrangement`, `email-draft`, `recipients`, `resume` or `unknown`) and whose `value` is the approved decision. Read its input schema for the shape of each `value`. Never invent a decision or use a tool absent from the connected server. The tool only confirms that the response was recorded: read `get-account-task` to report the task's new state.\n6. Use `cancel-account-task` only after an explicit request. Never bypass its confirmation.\n\nRespond in the language of the user's latest request. Copy proper names exactly. Never expose technical identifiers. Use natural business vocabulary and avoid internal terminology.\n"
}