Claude-skill-registry access-locked-out
Restore access for customers who are locked out of their account or courses. Use when a paying customer cannot log in, access materials, or restore purchases.
install
source · Clone the upstream repo
git clone https://github.com/majiayu000/claude-skill-registry
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/access-locked-out" ~/.claude/skills/majiayu000-claude-skill-registry-access-locked-out && rm -rf "$T"
manifest:
skills/data/access-locked-out/SKILL.mdsource content
Account Access Issues
Response Patterns (from samples)
Common openings:
- "Hi,"
- "Hello,"
- "Hey,"
Common core lines:
- "Best,"
- "Hi,"
- "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."
- "If you have any trouble accessing the course, please let us know!"
Phrases That Work (4-gram frequency)
- "let me know if" — 227 (25.9%)
- "if you have any" — 167 (19%)
- "me know if you" — 165 (18.8%)
- "know if you have" — 128 (14.6%)
- "let us know if" — 79 (9%)
- "at the top of" — 78 (8.9%)
- "to purchase the course" — 77 (8.8%)
- "the top of https" — 75 (8.5%)
- "everything should be back" — 73 (8.3%)
- "used to purchase the" — 73 (8.3%)
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.