cohort-access-request

📁 skillrecordings/support 📅 1 day ago
0
总安装量
1
周安装量
安装命令
npx skills add https://github.com/skillrecordings/support --skill cohort-access-request

Agent 安装分布

amp 1
cline 1
opencode 1
cursor 1
continue 1
kimi-cli 1

Skill 文档

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.