agentleFS
aka-kikaaka-kika/akakika-skills/skills/launch-review/emergency-switch-app/SKILL.md

emergency-switch-app

Skill11 starsChanged 3 months agoMITView on GitHub

Use when designing a user-initiated macOS emergency switch that helps the user save context before stopping, switching tasks, or leaving the computer — capture must be transparent, local-first, and easy to delete.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this skill when designing a user-initiated macOS emergency switch that helps the user save context before stopping, switching tasks, or …

    line 12
  2. Distinctive:

    Never silently collect screen, keyboard, messages, or private app content.

    line 50
  3. Distinctive:

    Ask before using any system permission.

    line 51

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Emergency Switch App

Design a user-initiated macOS emergency switch that helps the user save context before stopping, switching tasks, or leaving the computer. Capture must be user-initiated, transparent, local-first, and easy to delete — never silent monitoring.

When to use

Use this skill when designing a user-initiated macOS emergency switch that helps the user save context before stopping, switching tasks, or leaving the computer.

Core rule

Emergency capture must be user-initiated, transparent, local-first, and easy to delete.

Use for

  • Quick context note
  • Stop-and-save workflow
  • “What was I doing?” recovery
  • Interruption recovery
  • Local daily work summary

Trigger options

Menu bar button
Global shortcut chosen by user
Command palette command
Manual quick capture button

Capture fields

Manual note
Timestamp
Selected project
Current task if app knows it
User-selected files if provided
Optional active app/window title only with clear permission

Privacy rules

  • Never silently collect screen, keyboard, messages, or private app content.
  • Ask before using any system permission.
  • Show exactly what will be saved.
  • Store locally by default.
  • Let user edit/delete captured notes.

Output

What I was doing
Why I stopped
Next step when I return
Related project/task

Checklist

[ ] Capture is user-initiated
[ ] User sees what is captured
[ ] Permissions are explained
[ ] Data stays local unless user exports
[ ] Delete/edit exists

Prompt template

Drop this into any coding agent (Claude Code, Codex, Cursor, …) to apply the skill:

Use the emergency-switch-app skill to design a privacy-first emergency context capture flow. It must be user-initiated, transparent, editable, deletable, and local-first. Do not add silent monitoring.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.