OpenParable
Skip to content
← Back to skills

Cohort Schedule Inquiry

Productivity
cohort-schedule-inquiry

Cohort Schedule Inquiry is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Share cohort schedule information. Use when a customer asks about dates, timing, or when the next cohort starts.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/cohort-schedule-inquiry/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cohort-schedule-inquiry, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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.