mcpField
A
account-recovery-identity-review

account-recovery-identity-review

github.com/sylphxaiSecurity144 installsUpdated today
Repository

About account-recovery-identity-review

account-recovery-identity-review is a security skill for turning account recovery and identity-verification questions into an operational plan. It defines recovery paths, evidence requirements, safeguards, owners, and monitoring outputs while addressing account-takeover risk.

Key features

  1. 01Classify account recovery paths
  2. 02Define proof requirements and risk gates
  3. 03Specify rate limits and notifications
  4. 04Plan session invalidation and audit logs
  5. 05Create state machines and risk tables
  6. 06Set support and abuse-monitoring policies

Use cases

  1. 01Design an MFA reset process
  2. 02Review support-assisted account recovery
  3. 03Plan recovery after passkey or device loss
  4. 04Set safeguards for admin account restoration

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/sylphxai/skills --skill account-recovery-identity-review

After installing, type/account-recovery-identity-reviewin Claude Code to confirm it loaded.

Bundled filesagents/openai.yamlreferences/account-recovery-identity-patterns.md

Details

From the project README

Account Recovery Identity Review

Use this skill to convert a account recovery, identity proof, MFA reset, support escalation, anti-takeover risk, and user access restoration question into a concrete artifact with owners, gates, metrics, and recovery paths.

Workflow

  1. Identify account type, authentication factors, recovery factor, asset sensitivity, abuse history, support role, and lockout cost.
  2. Read references/account-recovery-identity-patterns.md.
  3. Classify the recovery path: password reset, MFA reset, passkey loss, SSO fallback, email/phone change, device loss, admin recovery, or support-assisted proof.
  4. Define proof requirements, friction ladder, rate limits, notifications, session invalidation, audit logs, and escalation boundaries.
  5. Produce recovery state machine, risk decision table, event schema, support policy, and abuse-monitoring checklist.

When not to use

  • Do not use for generic advice the base model already handles without this skill's specific artifact contract.

Guardrails

  • Do not let support override authentication without evidence, audit, and privilege boundaries.
  • Do not expose whether an email, phone, tenant, or account exists through recovery copy or timing.
  • Do not remove all factors at once for high-value accounts without cooldown, notification, or admin review.
  • Do not punish legitimate lockout users with permanent loss when safer step-up or appeal paths are possible.

Output format

Recovery context:
Account type / factor lost / asset sensitivity:

Recovery plan:
| Area | Decision | Evidence | Risk | Owner |
| --- | --- | --- | --- | --- |

Proof and controls:
- <item> -> <policy, metric, edge case, support note>

Escalation and abuse response:
- <trigger> -> <action, communication, owner>

Comments

Markdown supported