OpenParable
Skip to content
← Back to skills

Workshop Cancellation Notice

Productivity
workshop-cancellation-notice

Workshop Cancellation Notice 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.

Notify about workshop cancellations. Use when a scheduled workshop or session is canceled or rescheduled.

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

Response Patterns (from samples)

Common openings:

  • "Hi there,"

Common core lines:

  • "Hi there,"
  • "The workshop recording should be available next week, we will email you ASAP."
  • "Thanks for your support,"

Common closings:

  • "Taylor"

Phrases That Work (4-gram frequency)

  • "hi oscar the workshop" — 1 (100%)
  • "oscar the workshop recording" — 1 (100%)
  • "the workshop recording should" — 1 (100%)
  • "workshop recording should be" — 1 (100%)
  • "recording should be available" — 1 (100%)
  • "should be available next" — 1 (100%)
  • "be available next week" — 1 (100%)
  • "available next week we" — 1 (100%)
  • "next week we will" — 1 (100%)
  • "week we will email" — 1 (100%)

Tone Guidance (observed)

  • Openings trend toward: "Hi there,"
  • Closings often include: "Taylor"

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.