account-recovery-plan
FeaturedGet back into a locked or hacked account the right way — the official recovery routes, what proof you'll need, and how to re-secure it so it doesn't happen again. Use when asked I'm locked out of my account, my account got hacked, help me recover my [email/social/bank] account, or I lost access to 2FA. Produces the official recovery path for the account type, the identity proof to prepare, a re-securing checklist for after you're back in, and warnings about fake 'recovery' services and support scams.
Install
Quality Score: 96/100
Skill Content
Details
- Author
- mohitagw15856
- Repository
- mohitagw15856/pm-claude-skills
- Created
- 7 months ago
- Last Updated
- yesterday
- Language
- HTML
- License
- MIT
Integrates with
Bundled in these plugins
Similar Skills
Semantically similar based on skill content — not just same category
account-recovery
Assess account recovery — alternative authentication, recovery proof, takeover handling, and enterprise operations. Use when the user asks to review password reset, recovery flows, account takeover handling, or SSO recovery. Do not use to design the recovery flow.
account-recovery-review
End-to-end account recovery: lost credentials/MFA, locks, compromise, ownership proof, post-recovery hardening.
auditing-account-recovery-and-reset-trust
Audit password reset and account recovery flows for the trust that lets an attacker take over an account: a reset token that is guessable, long-lived, reusable, or not bound to the account it was issued for, a recovery path that verifies a weaker factor than login and bypasses multi-factor, a reset link whose host comes from an attacker-controllable header so the token leaks, and a recovery that trusts an unverified email or phone change to redirect the reset. Covers the recovery surface of authentication systems, where resetting a credential or recovering access is the alternate door into an account. Use when an application offers password reset or account recovery and that flow is a path to authentication. The attacker-driven recovery request is the source, the account it takes over is the sink, and the weak token, bypassed factor, or leaked reset link that grants it is the bug.