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.
Best use case
access-locked-out is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using access-locked-out should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/access-locked-out/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How access-locked-out Compares
| Feature / Agent | access-locked-out | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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.
Related Skills
accessing-github-repos
GitHub repository access in containerized environments using REST API and credential detection. Use when git clone fails, or when accessing private repos/writing files via API.
accessible-web-dev
Build WCAG 2.1 AA compliant web applications for University of Sheffield. Covers semantic HTML, ARIA patterns, form accessibility, keyboard navigation, color contrast, alt text, captions, and automated testing. Use when creating websites, web apps, forms, interactive components, or auditing accessibility for WCAG compliance, screen readers, keyboard access, or inclusive design.
accessibility-wcag
Build accessible web applications following WCAG 2.1/2.2 guidelines with proper semantic HTML, ARIA attributes, keyboard navigation, screen reader support, and inclusive design. Use when implementing ARIA labels and roles, ensuring keyboard navigation, supporting screen readers, providing text alternatives for images, managing focus, creating accessible forms, building inclusive UI components, testing with accessibility tools, meeting WCAG compliance levels, or designing for users with disabilities.
accessibility-standards
Implement WCAG 2.1 accessibility standards for Vue 3 apps. Use when adding ARIA labels, keyboard navigation, screen reader support, or checking color contrast. Mentions "accessibility", "ARIA", "keyboard nav", "screen reader", or "color contrast".
accessibility-review
Reviews UI for accessibility issues against WCAG 2.1/2.2 AA. Triggers on "is this accessible?", "check accessibility", or contrast/a11y review requests.
accessibility-report
Generate accessibility compliance reports including VPAT and ACR documents
accessibility-readability
Ensure textbook content is accessible, readable, and understandable for learners of all skill levels. Use when reviewing content for clarity, adding explanations for beginners, or improving content accessibility.
accessibility-patterns
Build inclusive web experiences following WCAG guidelines. Covers semantic HTML, ARIA, keyboard navigation, color contrast, and testing strategies. Triggers on accessibility, a11y, WCAG, screen readers, or inclusive design requests.
accessibility-mobile
React Native accessibility patterns for iOS and Android. Use when implementing a11y features.
accessibility
Audit and improve web accessibility following WCAG 2.1 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible". Do NOT use for SEO (use seo), performance (use core-web-vitals), or comprehensive site audits covering multiple areas (use web-quality-audit).
accessibility-games
Game accessibility skill for colorblind modes and control remapping.
accessibility-excellence
Master web accessibility (A11y) to ensure your product is usable by everyone, including people with disabilities. Covers WCAG standards, semantic HTML, keyboard navigation, screen readers, color contrast, and inclusive design practices. Accessibility is not a feature—it's a fundamental requirement.