Skip to content
Skills Library
Education · Writing

student-comms

/student-comms

Write student communications - welcome sequences, check-ins, re-engagement, feedback requests. Use when user says "welcome email for students", "student onboarding", "check in with students", "re-engage inactive students", or "student communication".

Licence
MIT
Last repository change
22.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 22.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Write student communications - welcome sequences, check-ins, re-engagement, feedback requests. Use when user says "welcome email for students", "student onboarding", "check in with students", "re-engage inactive students", or "student communication".

Triggers from the description

welcome email for studentsstudent onboardingcheck in with studentsre-engage inactive studentsstudent communication
Original author description

Write student communications - welcome sequences, check-ins, re-engagement, feedback requests. Use when user says "welcome email for students", "student onboarding", "check in with students", "re-engage inactive students", or "student communication".

How it works

  1. Setup Required
  2. Before You Start
  3. Inputs
  4. Communication Types
  5. Steps
  6. Output
  7. Rules
Original SKILL.md headings · 76 lines, 432 words
SKILL.md preview
---
name: student-comms
description: Write student communications - welcome sequences, check-ins, re-engagement, feedback requests. Use when user says "welcome email for students", "student onboarding", "check in with students", "re-engage inactive students", or "student communication".
department: community
pack: education
---

# Student Communications

Write any type of student communication — onboarding, check-ins, progress nudges, re-engagement, feedback requests, congratulations, and testimonial requests.

Kernel preamble §4 applies: `references/kernel-preamble.md`.

## Setup Required

Kernel preamble §1 applies: `references/kernel-preamble.md`.

## Before You Start

1. Read the resolved `voice` context — communications must sound like the owner/teacher
2. Read the resolved `brand` context — communication style
3. Read the resolved `icp` context — who the students are
4. Read the resolved `offers` context — what programs they're enrolled in
5. Check the relevant employee's `memory.md` for student context

## Inputs

The user provides:
- **Communication type** — see types below
- **Context** — which program, how many students, situation
- **Specific student** (optional) — name, situation, history

## Communication Types

| Type | Purpose | Tone |
|------|---------|------|
| **Welcome / Onboarding** | First impression after enrollment | Warm, exciting, action-oriented |
| **Check-in** | How's it going? Do they need help? | Caring, specific, low-pressure |
| **Progress Nudge** | They haven't engaged recently | Encouraging, not guilt-tripping |
| **Re-engagement** | Inactive for 2+ weeks | Direct value reminder, fresh start offer |
| **Feedback Request** | Ask for course/program feedback | Specific questions, easy to answer |
| **Congratulations** | Completed a milestone | Celebratory, what's next |
| **Testimonial Request** | Ask for a testimonial/review | Grateful, specific prompts, low friction |

## Steps

### Step 1: Identify the Situation
- Which program or course is this for?
- Where are the students in their journey?
- What's the goal of this communication?

### Step 2: Write the Communication

For each email/message:
- **Subject line** — 3 options
- **Opening** — personal, specific, acknowledges their situation
- **Body** — the purpose of the email (short — 150-250 words)
- **CTA** — one clear next step
- **Sign-off** — matches the owner's style

### Step 3: Sequence (if applicable)

If writing a multi-email sequence (e.g., onboarding):
- Map the student journey: Day 1, Day 3, Day 7
- Each email has ONE job — don't overload
- Build from welcome → orientation → first win → deeper engagement

## Output

Save to `outputs/YYYY-MM/comms/[type]-[context]/`:
- Individual email files or a sequence document

If an email platform is connected via MCP, offer to create drafts.

## Rules

- Every communication should feel personal, not automated
- Never guilt-trip inactive students — lead with value
- Match the owner's teaching voice exactly
- One CTA per email — don't ask them to do 3 things
- Testimonial requests: make it easy — provide specific prompts, not open-ended asks

Versions

The database has no other skills named student-comms.

Database snapshot: 13.11.2026 · package version 6b2794497c14 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90academy-students-program
    Use when a law student, law school administrator, or campus ambassador asks about HAQQ's Students Program — free Justinian access for verified law students, the campus ambassador program, student competitions, and thesis support. Delivers program terms, eligibility, application…
  • 90client-comms
    Write client communications - intake, follow-ups, check-ins, proposals, project updates. Use when user says "write a follow-up for [client]", "client intake email", "check in with [client]", "draft a proposal", or "project update email".
  • 100community-engagement-playbook
    Builds the student community system for a paid course - platform choice by where students already are, an introduce-yourself onboarding ritual, a weekly cadence of office hours, wins threads, and accountability checks, a hard creator-time budget, and scheduled…
  • 100gap-analysis-from-student-work
    Analyse student work against criteria to identify specific gaps between current performance and learning objectives. Use when reviewing submissions, planning feedback, or diagnosing learning needs.
  • 90student-feedback-writer
    Write structured, honest, and constructive feedback for student work including master's theses, project reports, seminar presentations, and assignments. Calibrated for academic supervision — separates what is good from what needs work, and gives actionable direction without…
  • 100student-mentor
    During-semester student support for university professors. 5-agent team covering feedback on student work (Hattie & Timperley structured, single or batch), struggling-student intervention plans, recommendation letters with bias-aware language checks, difficult student…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.