Agent skill · Workflow & Productivity

secure-a-lost-phone

Do the right things fast when your phone is lost or stolen — lock it, protect your accounts and money, and decide on wipe vs. locate — in the correct order. Use when asked my phone was stolen, I lost my phone what do I do, someone took my phone, or secure my lost phone. Produces an ordered action checklist (locate/lock, protect SIM and banking, change key passwords, wipe decision), the accounts to prioritize because the phone unlocks them, reporting steps, and prevention setup for next time.

mohitagw158561,255★ · 1 repos on radarProfile →
claude-codecursorMIT
Install
npx skills add mohitagw15856/pm-claude-skills --skill secure-a-lost-phone --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/secure-a-lost-phone/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,255
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Secure a Lost Phone A lost phone isn't just a lost device — it's a key to your email, banking, 2FA, and payments. The first 30 minutes matter. This gives the correct order: locate and lock it, stop the SIM and card access, change the passwords that matter, and decide when to remotely wipe — so a bad day doesn't become account takeover and fraud. ## What This Skill Produces - **The ordered checklist** — locate/lock via the find-my service, then protect the high-risk stuff, in priority sequence - **SIM & payment protection** — contact your carrier to suspend the SIM (stops SMS-2FA hijack) and your bank to protect cards/wallet - **Account priorities** — change passwords on email and key accounts the phone can unlock or reset - **The wipe decision** — locate-and-lock vs. remote-wipe, and the tradeoffs (recovery vs. data exposure) - **Reporting** — police report (for theft/insurance) and carrier notification - **Prevention setup** — what to enable now so next time is a shrug, not a crisis ## Required Inputs Ask for these if not provided: - **Lost or stolen** — and any sense of where (changes locate vs. wipe) - **Phone type** — iPhone/Android (determines the find-my/lock tools) - **Wha

What's inside
Steps it walks through
  1. What This Skill Produces
  2. Required Inputs
  3. Framework: Lock, Cut Access, Decide To Wipe
  4. Output Format
  5. Lost/stolen phone: [iPhone/Android] · [lost/stolen] · has [banking/2FA]?
  6. Quality Checks
  7. Anti-Patterns
  8. Example Trigger Phrases
More from pm-claude-skills
All skills →
About this skill
What does the secure-a-lost-phone skill do?

Do the right things fast when your phone is lost or stolen — lock it, protect your accounts and money, and decide on wipe vs. locate — in the correct order. Use when asked my phone was stolen, I lost my phone what do I do, someone took my phone, or secure my lost phone. Produces an ordered action checklist (locate/lock, protect SIM and banking, change key passwords, wipe decision), the accounts to prioritize because the phone unlocks them, reporting steps, and prevention setup for next time.

How do I install it?

Run `npx skills add mohitagw15856/pm-claude-skills --skill secure-a-lost-phone --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going