OpenParable
Skip to content
← Back to skills

Workshop Attendance Confirmation

Productivity
workshop-attendance-confirmation

Workshop Attendance Confirmation 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.

Confirmation emails and calendar invitations for workshop or cohort attendance.

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/communication/workshop-attendance-confirmation/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/workshop-attendance-confirmation, 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.

Workshop Attendance and Confirmations

Response Patterns (from samples)

Common openings:

  • "Hey,"
  • "Hey Loren,"
  • "Hey Karen,"

Common core lines:

  • ">"
  • "Best,"
  • "Hey,"

Common closings:

  • "Best,"
  • "unsubscribe12333 Sowden Rd, Ste. B, PMB #97429 Houston, TX 77080-2059"
  • "Let me know If you missed the event. Sorry to hear getting the link to join was not clear."

Phrases That Work (4-gram frequency)

  • "let me know if" — 7 (24.1%)
  • "me know if you" — 5 (17.2%)
  • "you need to know" — 4 (13.8%)
  • "if you have any" — 4 (13.8%)
  • "https egghead zoom us" — 4 (13.8%)
  • "egghead zoom us j" — 4 (13.8%)
  • "did you end up" — 2 (6.9%)
  • "you end up finding" — 2 (6.9%)
  • "end up finding the" — 2 (6.9%)
  • "up finding the invite" — 2 (6.9%)

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