Agent skill
access-locked-out
Customer cannot log in, access course materials, or restore their account despite having purchased content.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/access-locked-out
SKILL.md
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%)
- "email let me know" — 84 (9.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%)
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
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?