Menu
Safely deprecate a file following the deprecation protocol.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
End-of-session shutdown sequence. Saves session log, updates MEMORY.md, updates CLAUDE.md, and stages a git commit.
First-time project setup. Checks prerequisites (Zotero MCP), asks for paper count, generates folder structure, and configures all templates.
Peripheral vision audit — find what the author has become blind to in their results. Run in a FRESH TERMINAL.
Structured debate between two perspectives on a research design decision.
Find gaps in the literature based on existing Obsidian notes. Searches for high-quality articles the author may have missed.
Scaffold a new paper directory with the full structure, CLAUDE.md, and empty templates.
| name | deprecate |
| description | Safely deprecate a file following the deprecation protocol. |
| argument-hint | [filepath] [reason] |
_deprecated/ directory in the same folder if it doesn't exist_deprecated/YYYY-MM-DD_filename.ext_deprecation-log.md in the same directory:
## YYYY-MM-DD · filename.ext
- **Reason**: [provided reason]
- **Deprecated to**: _deprecated/YYYY-MM-DD_filename.ext
- **Session**: [current session log path]
- **Breaking changes**: [any downstream effects]
Before deprecating, check:
data/raw/? → REFUSE (Tier 1: immutable)code/replication/? → REFUSE (Tier 1: immutable)correspondence/? → REFUSE (Tier 1: immutable)session-logs/? → REFUSE (Tier 1: immutable)data/raw/restricted/? → REFUSE (Tier 1: immutable + sensitive)If any check fails, explain why the file cannot be deprecated and suggest alternatives.