family-communication

Write clear, warm, family-facing communication for K-12: class newsletters, parent/guardian letters and emails, conference talking points, and progress-report narrative comments. Use this whenever a t

SKILL.md

GitHub

family-communication

Writes family-facing communication that is clear, warm, and privacy-safe.

Privacy first (SECURITY_AND_SAFETY.md). Use placeholder names and never include real student data, grades, behavior details, or health/SpEd information. For a message about an individual child, keep specifics general and mark where the teacher must personalize — the teacher adds real details directly, not through this skill.

1. Follow the pipeline (references/method.md)

Within Generation: Analysis → (light Standards Alignment) → Differentiation → Generation.

  1. Analysis — identify the artifact (references/artifact-types.md), audience (all families vs. one family), purpose, and tone. Log assumptions.
  2. Standards alignment (light) — where it helps families understand learning, translate the relevant standard into plain language (no codes/jargon in the family-facing text).
  3. Accessibility & inclusion — plain language, ~grade 6-8 readability by default (shared/quality/readability-age.md), define any necessary terms, translation-friendly phrasing, respectful strengths-based tone, culturally inclusive.
  4. Generation — draft from the template; keep it concise and skimmable; include a clear call to action / contact line.

2. Validate, then gate

Run the universal + communication checks (references/verification-checklists.md) — the Safety gate (no real PII) and Accessibility gate (readability, tone) are key. Self-score against references/quality-gates.md, then hand to quality-review.

3. Always emit the metadata block

Per references/metadata-schema.md, with human_review_required: true and a note on where the teacher should personalize. Placeholders only.

Artifact types: references/artifact-types.md. Template: assets/templates/newsletter-template.md.