# Cohort Access Request

> Help with access to cohort materials and recordings. Use when a customer cannot find or access cohort content, workshop materials, or live session recordings.

- Skill: `majiayu000/cohort-access-request` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/cohort-access-request`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/cohort-access-request/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Data & Analytics
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/cohort-access-request

---

# Cohort or Workshop Access

## Response Patterns (from samples)

Common openings:
- "Hey,"
- "Hi,"
- "Hi there,"

Common core lines:
- ">>"
- ">>>"
- ">"

Common closings:
- "Best,"
- "Happy learning!"
- "No recording of the workshop itself will be available, but you'll find that EpicReact.Dev is much better than a simple workshop recording."

## Phrases That Work (4-gram frequency)

- "let me know if" — 26 (21.5%)
- "me know if you" — 18 (14.9%)
- "know if you have" — 12 (9.9%)
- "https click convertkit mail" — 11 (9.1%)
- "click convertkit mail com" — 11 (9.1%)
- "convertkit mail com d0u0eq3vz2a0hoekdowamhzn73444hlh5xp3" — 11 (9.1%)
- "convertkit mail2 com 4zume0z58lbeh5vepv3cxh3d7pv77" — 10 (8.3%)
- "https click convertkit mail2" — 9 (7.4%)
- "click convertkit mail2 com" — 9 (7.4%)
- "have access to the" — 8 (6.6%)

## Tone Guidance (observed)

- Openings trend toward: "Hey,"
- Closings often include: "Best,"

## What NOT To Do

- Don't introduce policy details that are not present in the verified response lines above.
- Don't paraphrase or reframe the customer's question in a way that changes meaning.
- Don't add refund/discount promises unless they appear in the extracted responses for this topic.

## Validation

Draft must:
- [ ] Include at least one of the required phrases from the validation block
- [ ] Stay consistent with the observed response patterns above
- [ ] NOT introduce policy details that are not present in the verified response lines above.
