Claude-skill-registry cohort-schedule-inquiry
Share cohort schedule information. Use when a customer asks about dates, timing, or when the next cohort starts.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/cohort-schedule-inquiry" ~/.claude/skills/majiayu000-claude-skill-registry-cohort-schedule-inquiry && rm -rf "$T"
manifest:
skills/data/cohort-schedule-inquiry/SKILL.mdsource content
Cohort Schedule and Timing Inquiry
Response Patterns (from samples)
Common openings:
- "Hey,"
- "Hello,"
- "Hi there,"
Common core lines:
- ">>"
- ">>>"
- ">"
Common closings:
- "Best,"
- ">>"
- "Let me know if you have any additional questions!"
Phrases That Work (4-gram frequency)
- "let me know if" — 12 (14.5%)
- "https www epicai pro" — 11 (13.3%)
- "me know if you" — 11 (13.3%)
- "https click convertkit mail" — 10 (12%)
- "click convertkit mail com" — 10 (12%)
- "know if you have" — 9 (10.8%)
- "convertkit mail com v8u07n3lmosrhvpq9nebghv2edlllf9h03x2" — 7 (8.4%)
- "convertkit mail com 68ulor4726a8h5738pnhohpl5rkkkh9hdqrv" — 7 (8.4%)
- "brandon mcconnell email wrote" — 7 (8.4%)
- "jun 16 2025 at" — 7 (8.4%)
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.