Update to Seekrly

{
  "description": "Review the user's job search in Seekrly - what's due today or this week, upcoming interviews, follow-ups to send, stale applications and overall progress. Use for \"what should I do today\", \"weekly review\", \"how's my job search going\", \"what's coming up\" or \"who haven't I heard back from\".",
  "included_files": [],
  "name": "seekrly-pipeline-review",
  "skill_md_contents": "---\nname: seekrly-pipeline-review\ndescription: Review the user's job search in Seekrly - what's due today or this week, upcoming interviews, follow-ups to send, stale applications and overall progress. Use for \"what should I do today\", \"weekly review\", \"how's my job search going\", \"what's coming up\" or \"who haven't I heard back from\".\n---\n\n# Review the job-search pipeline\n\nFollow the ground rules in the `seekrly` skill. This skill only reads data; it\nchanges nothing unless the user then asks for an action.\n\n## Gather (in parallel where you can)\n\n- **Upcoming interviews**: `list_interviews` with `upcoming: true` (and `to` = end of\n  the period for \"this week\").\n- **Follow-ups due**: `list_follow_ups` with `status: \"Pending\"` and `dueTo` = today\n  (or the end of the period). Overdue ones are Pending with a past date.\n- **Needs a nudge**: `list_follow_ups` with `nudgeDue: true` - sent follow-ups nobody\n  has replied to. Offer to draft the next message or `snooze_follow_up_nudge`.\n- **Failed sends**: `list_follow_ups` with `status: \"Failed\"` - emails that\n  didn't go out (`sendError` says why). Surface these first.\n- **Active pipeline**: `list_applications` per relevant status - `Applied`,\n  `Interviewing`, `Negotiating`, `Offer` - or without a filter for everything\n  (newest activity first). Page with `offset` if `total` is larger.\n- **Stale applications**: `Applied` with an old `appliedDate` and no recent\n  `updatedAt` (e.g. 14+ days) - candidates for a follow-up or `No Response`.\n\nIf an area isn't shared (permission error), skip it and mention it once at the end.\n\n## Present\n\nLead with what needs action, most urgent first. A good shape:\n\n1. **Today / overdue** - failed sends, interviews today, follow-ups due or overdue.\n2. **This week** - upcoming interviews (date, time in words, company, round, link).\n3. **Waiting to hear back** - applied, no movement for a while; suggest a follow-up.\n4. **Pipeline at a glance** - counts by stage (e.g. \"12 applied · 3 interviewing ·\n   1 offer\").\n5. **Suggested next steps** - 2-4 concrete actions you can do for them (\"draft a\n   follow-up to Priya at Stripe\", \"prep for Thursday's system design round\").\n\nKeep it scannable: short bullets, dates in words, no raw ids or ISO timestamps.\nDon't pad with generic job-search advice.\n\n## Acting on it\n\nWhen the user picks an action, hand off to the matching skill: follow-ups and\nemails → `seekrly-outreach`, interviews → `seekrly-interview-prep`, status changes\n→ `seekrly-track-job`.\n"
}