OpenParable
Skip to content
← Back to skills

Course Content Locked

Apps & Automation
course-content-locked

Course Content Locked is an Agent Skill for apps & automation published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Restore access to purchased course content. Use when a customer has paid but content is locked, missing, or inaccessible.

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

Course Content Locked or Unavailable

Response Patterns (from samples)

Common openings:

  • "Hi,"
  • "Hello,"
  • "Hi there,"

Common core lines:

  • "Hi,"
  • "Best,"
  • "Hello,"

Common closings:

  • "Best,"
  • "Thanks for the heads up! Everything should be back up and running smoothly now. Let us know if that's not the case."
  • "Your original purchase price will be removed from the upgrade to the full unrestricted version if you should choose to upgrade."

Phrases That Work (4-gram frequency)

  • "let me know if" — 91 (17.5%)
  • "me know if you" — 77 (14.8%)
  • "to access the course" — 52 (10%)
  • "know if you have" — 50 (9.6%)
  • "thanks for the heads" — 50 (9.6%)
  • "for the heads up" — 50 (9.6%)
  • "at the top of" — 50 (9.6%)
  • "you ll need to" — 49 (9.4%)
  • "if you have any" — 48 (9.2%)
  • "let us know if" — 46 (8.8%)

Tone Guidance (observed)

  • Openings trend toward: "Hi,"
  • 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.