Agent Skillsmohitagw15856/pm-claude-skills › parent-communication

parent-communication

GitHub

用于起草清晰、温暖且专业的家校沟通信息,涵盖进度反馈、问题反馈或会议邀请。该技能生成具体、以合作为导向的建设性消息,避免指责语气,确保包含积极开场、具体事例、共同解决方案及明确下一步行动,维护良好的家校伙伴关系。

skills/parent-communication/SKILL.md mohitagw15856/pm-claude-skills

Trigger Scenarios

需要向家长发送学生进展更新 需要就学术或行为问题与家长沟通 需要邀请家长参加家长会或面谈 需要分享学生的正面表现或好消息

Install

npx skills add mohitagw15856/pm-claude-skills --skill parent-communication -g -y
More Options

Use without installing

npx skills use mohitagw15856/pm-claude-skills@parent-communication

指定 Agent (Claude Code)

npx skills add mohitagw15856/pm-claude-skills --skill parent-communication -a claude-code -g -y

安装 repo 全部 skill

npx skills add mohitagw15856/pm-claude-skills --all -g -y

预览 repo 内 skill

npx skills add mohitagw15856/pm-claude-skills --list

SKILL.md

Frontmatter
{
    "name": "parent-communication",
    "description": "Draft clear, warm, professional messages to parents or guardians — progress notes, concerns, positive news, behaviour issues, or meeting requests. Use when asked to email a parent, write home about a student, raise a concern with a guardian, or share an update. Produces a ready-to-send message that is specific, partnership-oriented, and constructive — never accusatory — with the tone matched to the situation."
}

Parent Communication Skill

Messages home set the tone for the whole relationship. The best ones are specific, lead with care for the child, frame issues as a shared problem to solve, and always include a next step. This skill writes them.

Working from a brief

Given the situation, write the full message anyway using a placeholder-free template (e.g. "Alex" / "your child" rather than "[student name]" only where the teacher must personalise — keep those to an obvious minimum and mark them clearly). Match the tone to the purpose.

Required Inputs

Ask for (if not already provided):

  • Purpose (positive news, progress update, academic concern, behaviour issue, meeting request)
  • Student (name/year) and the specifics (what happened, with examples)
  • Channel & tone (email, app message, note home; formal or warm)
  • Desired outcome (awareness, a meeting, support at home)

Output Format

A ready-to-send message:

  • Subject line (clear, non-alarming even for concerns)
  • Opening — a genuine, specific positive about the child first (especially before a concern)
  • The message — what's happening, with one concrete example; for concerns, factual and non-judgmental
  • Partnership framing — "here's how we can support [child] together"
  • Clear next step — a meeting offer with options, a specific ask, or simply "no action needed, just sharing good news"
  • Warm close

For a sensitive issue, also give:

  • What to avoid saying — the phrasings that sound accusatory or label the child.

Quality Checks

  • Leads with care for the child, not the problem
  • Specific (a real example), not vague labels ("disruptive", "lazy")
  • Frames issues as a shared problem, not blame
  • Ends with a clear, easy next step
  • Tone matches the purpose; subject line won't alarm unnecessarily

Anti-Patterns

  • Labelling the child instead of describing the behaviour
  • Jargon or edu-speak parents won't parse
  • A concern with no path forward or offer of support
  • Over-long; burying the point under throat-clearing

Version History

  • a38bc30 Current 2026-07-05 11:39

Same Skill Collection

exports/openclaw/360-feedback-template/SKILL.md
exports/openclaw/401k-plan-decoder/SKILL.md
exports/openclaw/ab-test-planner/SKILL.md
exports/openclaw/ab-test-readout/SKILL.md
exports/openclaw/accessibility-audit/SKILL.md
exports/openclaw/account-plan/SKILL.md
exports/openclaw/acquirer-red-team/SKILL.md
exports/openclaw/ad-copy/SKILL.md
exports/openclaw/aeo-optimizer/SKILL.md
exports/openclaw/agenda-or-cancel/SKILL.md
exports/openclaw/agent-design-review/SKILL.md
exports/openclaw/agent-observability-spec/SKILL.md
exports/openclaw/agent-spec/SKILL.md
exports/openclaw/ai-ethics-review/SKILL.md
exports/openclaw/ai-eval-plan/SKILL.md
exports/openclaw/ai-feature-prd/SKILL.md
exports/openclaw/ai-product-canvas/SKILL.md
exports/openclaw/air-quality/SKILL.md
exports/openclaw/altitude-shifter/SKILL.md
exports/openclaw/ambiguity-resolver/SKILL.md
exports/openclaw/analyst-relations-brief/SKILL.md
exports/openclaw/announcement-card/SKILL.md
exports/openclaw/api-docs-writer/SKILL.md
exports/openclaw/api-test-plan/SKILL.md
exports/openclaw/api-versioning-strategy/SKILL.md
exports/openclaw/apology-letter/SKILL.md
exports/openclaw/architecture-decision-record/SKILL.md
exports/openclaw/architecture-diagram/SKILL.md
exports/openclaw/archive-strategy/SKILL.md
exports/openclaw/assumption-bounty/SKILL.md
exports/openclaw/assumption-mapper/SKILL.md
exports/openclaw/async-update-format/SKILL.md
exports/openclaw/auto-repair-estimate-decoder/SKILL.md
exports/openclaw/autopilot-charter/SKILL.md
exports/openclaw/benefits-decoder/SKILL.md
exports/openclaw/bid-tender-review/SKILL.md
exports/openclaw/board-deck-narrative/SKILL.md
exports/openclaw/board-minutes/SKILL.md
exports/openclaw/board-pre-read/SKILL.md
exports/openclaw/bom-cost-review/SKILL.md
exports/openclaw/bookkeeping-categorization/SKILL.md
exports/openclaw/boolean-search-builder/SKILL.md
exports/openclaw/brag-doc/SKILL.md
exports/openclaw/brainstorming/SKILL.md
exports/openclaw/brief-builder/SKILL.md
exports/openclaw/briefing-note/SKILL.md
exports/openclaw/budget-builder/SKILL.md
exports/openclaw/budget-variance-analysis/SKILL.md
exports/openclaw/bug-diagnosis/SKILL.md
exports/openclaw/bug-report/SKILL.md

Metadata

Files
0
Version
471c606
Hash
bc1085e4
Indexed
2026-07-05 11:39

- 위키
Copyright © 2011-2026 iteam. Current version is 2.155.2. UTC+08:00, 2026-07-30 18:12
浙ICP备14020137号-1 $방문자$