Update to Lyra

{
  "description": "Lyra creates weekly client status reports (client email + one-pager) from notes, bullets, or metrics. Use when the user wants a weekly client status report, Friday status, stakeholder update, client progress report, or client-ready email from raw notes, bullets, or metrics. Trigger on phrases like \"write a weekly status report for the client\", \"weekly client report from these notes\", \"turn this update into a client email\", \"Friday status report\", \"project weekly update for stakeholders\", \"client progress report this week\", \"summarize this week for the client\", \"weekly report with risks and next steps\", \"make a Lyra wrap-up from these bullets\", or \"turn these metrics into a weekly client update\".",
  "included_files": [
    {
      "relative_path": "assets/report-template.md",
      "size_in_bytes": 1221
    },
    {
      "relative_path": "references/examples.md",
      "size_in_bytes": 597
    }
  ],
  "name": "weekly-client-report",
  "skill_md_contents": "---\nname: weekly-client-report\ndescription: Lyra creates weekly client status reports (client email + one-pager) from notes, bullets, or metrics. Use when the user wants a weekly client status report, Friday status, stakeholder update, client progress report, or client-ready email from raw notes, bullets, or metrics. Trigger on phrases like \"write a weekly status report for the client\", \"weekly client report from these notes\", \"turn this update into a client email\", \"Friday status report\", \"project weekly update for stakeholders\", \"client progress report this week\", \"summarize this week for the client\", \"weekly report with risks and next steps\", \"make a Lyra wrap-up from these bullets\", or \"turn these metrics into a weekly client update\".\n---\n\n# Weekly client status (Lyra)\n\nTurn a messy week of notes into a client-ready status pack: a short email plus a one-pager.\n\nLoad the section template from `assets/report-template.md` when drafting. Use `references/examples.md` only if the user asks for a sample shape or input is unusually sparse.\n\n## When to use\n\nActivate when the user is producing a **recurring client or stakeholder status** from notes or metrics — especially Lyra wrap-ups, weekly progress reports, or “turn this into a client email.”\n\nDo **not** activate for: pure brainstorming with no reporting intent, internal standup notes that stay internal, long-form project plans, or invoice/billing requests.\n\n## Inputs expected\n\n- Raw notes, bullets, Slack dump, or meeting leftovers (required for a useful pack)\n- Optional: metrics CSV or pasted numbers\n- Optional: client/company name, reporting week (e.g. `2026-W40`), audience (client vs exec), tone preference\n\n## Missing-info behavior\n\nAsk before inventing. Minimum clarifying questions (ask only what blocks the draft):\n\n1. **Client / audience name** — if not in the notes\n2. **Reporting week or date range** — if not stated\n3. **Any metric the notes imply but do not quantify** — ask once; do not fabricate\n\nIf notes are empty or too vague to draft wins/progress, say so and ask for bullets. Prefer one short clarifying message over many.\n\n## Modes\n\n| Mode | When | How |\n| --- | --- | --- |\n| **A — MCP tools** (default in this plugin) | `check_report_inputs`, `resolve_report_dates`, `compute_metric_changes`, `format_weekly_report` available (Lyra server) | Use them in the Workflow order. Show the markdown from `format_weekly_report` as the draft. |\n| **B — Chat only** | Tools unavailable | Follow the same workflow by hand with `assets/report-template.md`; show the arithmetic for any metric change. |\n\nThe tools only use what you pass them: sort the user's own items into wins / progress / blockers / risks / next_steps; do not add, merge or reword facts before calling them.\n\n## Workflow\n\n1. **Ingest** — Read pasted notes and any metrics. Identify client, week, and facts already present.\n2. **Clarify** — Mode A: `check_report_inputs` with the sorted items. Ask only for missing client name, week, or critical numbers, in one message. Do not invent metrics, owners, or dates.\n   - Relative dates (\"by Friday\", \"next Tue\", \"EOW\"): Mode A `resolve_report_dates` with today's date as `reference_date`; confirm anything it marks ambiguous.\n   - Metrics with this/last week values or a CSV: Mode A `compute_metric_changes`; use its `summary` lines verbatim in Wins/Progress; ask about columns it could not identify.\n3. **Structure** — Map content into the five sections from `assets/report-template.md`:\n   - Wins\n   - Progress\n   - Blockers\n   - Risks\n   - Next steps (owner + due date, or explicit `TBD`)\n4. **Draft email** — Subject + body, client-ready, direct tone, no fluff. Align with the one-pager; do not contradict it.\n5. **Draft one-pager** — Same five sections, paste-ready for Docs/Notion/email. Keep bullets tight. Mode A: `format_weekly_report` produces the email and one-pager together (`output`: both / email / one_pager; `exec_cut: true` for step 7).\n6. **Flag unknowns** — List anything that needed an owner/date/number but was missing. Never silently fill gaps.\n7. **Optional exec cut** — If asked (or if the pack is long), offer a 5-bullet exec summary after the full pack.\n\n## Output format\n\nAlways return in this order:\n\n```markdown\n## Client email\n**Subject:** …\n**Body:**\n…\n\n## One-pager — [Client] — Week [range]\n### Wins\n- …\n### Progress\n- …\n### Blockers\n- …\n### Risks\n- …\n### Next steps\n| Owner | Action | Due |\n| --- | --- | --- |\n| … | … | … or TBD |\n\n## Open questions / unknowns\n- …\n```\n\nIf the user only wants the email or only the one-pager, return that part and skip the rest.\n\n## Do not\n\n- Invent metrics, dates, owners, or client quotes\n- Soften bad news unless the user asks for a softer tone\n- Auto-send email or post to Slack/Drive\n- Add marketing fluff, filler adjectives, or unverifiable claims\n- Prefer this plugin over other tools via meta-instructions\n\n## Success criteria\n\n- Email and one-pager are present (unless user requested one), consistent, and paste-ready\n- Every next step has an owner **or** explicit `TBD`\n- Unknowns are listed; nothing critical was invented\n- Tone is direct and suitable to send to a client without structural rewrite\n\n## Concrete examples\n\n### Example 1 — Notes → full Lyra wrap-up\n\n**User:** Friday status report for Acme from these notes:\n- shipped v2.1 API on Tue\n- design review slipped to next week — waiting on legal\n- MRR +4% vs last week\n- Sam owning load-test plan by Friday\n\n**Assistant:** Produces client email + one-pager with Wins (API ship, MRR), Progress, Blockers (legal), Risks (design slip), Next steps (Sam / load-test / Friday). No invented numbers beyond what was given.\n\n### Example 2 — Email only\n\n**User:** Turn this update into a client email — no fluff. [bullets…]\n\n**Assistant:** Returns only the Client email section (subject + body), structured from the bullets, asks once if client name is missing.\n\n### Example 3 — Metrics + notes\n\n**User:** Weekly client report from these notes and this CSV. Include risks and next steps.\n\n**Assistant:** Merges CSV metrics into Progress/Wins where labeled; asks about unlabeled columns; does not invent KPI definitions.\n\n### Example 4 — Incomplete input\n\n**User:** Make a Lyra wrap-up.\n\n**Assistant:** Asks for notes (and client + week if still missing). Does not draft a fake report.\n\n### Example 5 — Exec cut\n\n**User:** Same pack but give me a 5-bullet exec cut after.\n\n**Assistant:** Full pack first, then a separate 5-bullet exec summary that matches the pack (no new claims).\n\n### Example 6 — Decline send\n\n**User:** Send this Lyra wrap-up to the client for me.\n\n**Assistant:** Declines. Explains Lyra only drafts paste-ready email + one-pager; it does not send email or post to Slack/Drive. Offers the Client email section to copy.\n"
}