Update to AB

{
  "description": "Generate the user's daily standup from AB Projects (ActionBridge) — what's in progress, what's due today, and what's blocked, formatted to share in chat. Use when the user says \"standup\", \"daily report\", \"what's on my plate today\", or asks for their day's tasks across projects.",
  "included_files": [],
  "name": "ab-standup-reporter",
  "skill_md_contents": "---\r\nname: ab-standup-reporter\r\ndescription: Generate the user's daily standup from AB Projects (ActionBridge) — what's in progress, what's due today, and what's blocked, formatted to share in chat. Use when the user says \"standup\", \"daily report\", \"what's on my plate today\", or asks for their day's tasks across projects.\r\n---\r\n\r\n# Daily standup from AB Projects\r\n\r\nProduce a short, share-ready standup for the user. Data first, then format.\r\n\r\n## Gather\r\n\r\n1. `ab_get_schedule` (no `project_id`) — overdue, due-today, and this-week tasks across all the user's projects.\r\n2. `ab_get_my_tasks` — all active assigned tasks; use it to spot in-progress work that has no due date (the schedule won't show those).\r\n3. If any task looks blocked or stalled and detail matters, `ab_get_task` on just that task to check dependencies (\"Blocked: yes\") and recent comments. Don't fetch every task — only the ones you'll call out.\r\n\r\n## Compose\r\n\r\nDefault format (adapt to the user's stated style if they have one):\r\n\r\n```\r\n**Standup — {today's date}**\r\n✅ Recently done / in motion: {1-3 items with [taskId]}\r\n🎯 Today: {due-today tasks + the one or two most important in-progress items}\r\n⚠️ Blockers: {overdue tasks and dependency-blocked tasks, each with what it's waiting on; write \"none\" if clear}\r\n```\r\n\r\n- Keep it under ~10 lines; per item: `[taskId] title — one clause of context`.\r\n- Overdue items always appear, oldest first, marked with how many days overdue.\r\n- If the schedule comes back \"No tasks due this week. You're clear!\", say so positively and list at most the top 2 in-progress items.\r\n\r\n## After presenting\r\n\r\nOffer exactly one follow-up: post it somewhere or act on a blocker (e.g. \"want me to bump the due date on [id]?\" → hand off to ab-project-manager conventions: update with a `note`). Don't write anything to AB unless asked — standup generation itself is read-only.\r\n"
}