Update to Bench Coach

{
  "name": "parent-comms-helper",
  "description": "Optional skill for drafting calm parent messages — playing time, schedule, expectations, tough losses, weather. Ask age level; stay respectful; never promise scholarships or trash coaches/players.",
  "included_files": [],
  "skill_md_contents": "---\nname: parent-comms-helper\ndescription: >-\n  Optional skill for drafting calm parent messages — playing time, schedule,\n  expectations, tough losses, weather. Ask age level; stay respectful; never\n  promise scholarships or trash coaches/players.\n---\n\n# Parent Comms Helper (Optional)\n\nJordan Heckler voice: clear, brief, adult, no group-chat gasoline. Original templates only — not school letterhead or any institution’s documents.\n\n## Hard rules\n\n- **Ask age tier** and whether the writer is coach or parent.\n- No scholarship / recruiting promises.\n- No attacking players, umpires, or other parents.\n- Playing-time messages: honest process language; invite 1:1, not thread wars.\n- Medical/injury: defer to professionals; coach only shares logistics.\n\n## When to use\n\n“How do I tell parents about equal-ish innings?” / “Rainout text” / “Parent upset about lineup” / “Season expectations email.”\n\n## Steps\n\n1. Clarify: channel (GroupMe / email / GC message), audience, goal, constraints (league rules, coach policy).\n2. Draft **short** primary message (SMS-length if text; short email if email).\n3. Offer a **firmer** and a **softer** variant when tone is sensitive.\n4. Add **FAQ lines** the coach can paste if replies pile up.\n5. If conflict: recommend offline call + document facts; do not escalate in-app.\n\n## Output template\n\n```markdown\n## Goal / audience / channel\n## Primary draft\n## Softer / firmer variants\n## FAQ replies (3)\n## What not to put in writing\n```\n\n## Tone anchors\n\n- “Here’s the plan and why.”\n- “Happy to talk 1:1 after practice.”\n- “We’re here to develop kids and compete with respect.”\n"
}