skills.rest
line7works
line7worksOFFICIAL
Explore all skills by this author →
WebsiteGitHub

sunset

Archive abandoned projects across vault, repo, GitHub, Vercel, database, and Notion layers.

Updated Jun 2, 2026
Search Tags:#automation#github#obsidian#vercel#archive#database backup#project retirement
One-click install
npx skills add https://github.com/line7works/tony-skills --skill sunset-line7works
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sunset
Source: https://github.com/line7works/tony-skills/tree/main/plugins/sun/skills/sunset
Command: npx skills add https://github.com/line7works/tony-skills --skill sunset-line7works

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Retiring a project leaves scattered remnants across many systems — Obsidian vault folders, Claude Code memory stores, scheduled agents, local repos, GitHub, Vercel, databases, and Notion boards — and manually cleaning each layer is error-prone and easy to leave half-done. This Skill performs a full, reversible sunset across every layer at once, with previews and safety checks before anything changes. ## Core Features & Use Cases - Multi-layer archival: Moves vault docs to 90-archive, archives CLI memory stores, cancels scheduled agents and crons, moves the local repo to ~/Developer/_archive, archives the GitHub repo, pauses the Vercel project, backs up and idles the database, and archives the Notion board. - Safety-first execution: Always previews every change in a preflight table, asks for a one-line reason, checks for uncommitted or unpushed git work, and never deletes anything — every step is reversible. - Tombstone and handoff generation: Writes a _sunset.md tombstone recording exactly what changed and how to revive, plus a copy-paste prompt that tells other LLM surfaces the project is archived. - Use Case: When you decide to stop working on a side project, run a full sunset so its vault notes, repo, hosting, database, and automations are all archived in one pass, with a complete record for later revival. ## Quick Start Ask the assistant to sunset a project by name, for example: run /sunset my-project to preview and archive it across all layers.

Frequently Asked Questions about sunset

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I archive a project across GitHub, Vercel, and my local machine at once?▼

Run the sunset skill with the project name. It resolves the project across all layers, previews every change in a table, and on confirmation moves the repo to ~/Developer/_archive, archives the GitHub repo, pauses Vercel, backs up the database, and archives vault and Notion content.

How do I safely retire a project without deleting anything?▼

Use a reversible archival workflow: move files to archive locations, pause services instead of deleting them, and back up databases before idling. The sunset skill never deletes anything — every action is a move, flag, pause, or backup that can be undone.

Can I preview what a project sunset will change before executing?▼

Yes. Run with --dry-run to execute only the resolution and preview phase, which prints the full preflight table of planned actions per layer and stops. Even a normal run always shows the preview and waits for an explicit go before executing.

Does archiving a project back up its database first?▼

Yes. The database is backed up with pg_dump to the archived repo folder before the compute is idled, and the dump is verified non-empty. The database is never dropped or deleted during a sunset.

What happens to scheduled agents and cron jobs when a project is archived?▼

The preflight scan enumerates scheduled routines, crontab entries, and launchd agents tied to the project, and they are cancelled during execution. Each cancellation is recorded in the tombstone so the schedules can be recreated if the project is revived.

How do I revive a project after it has been sunset?▼

The tombstone file documents the full revive recipe: move the vault folder back to 03-projects, flip status fields to active, move the repo back to ~/Developer, unarchive the GitHub repo, unpause Vercel, restore the database and Notion board, and recreate the cancelled schedules.

Related Skills

Explore More Personal & Entrepreneur Skills→
tradingstrategy-aitradingstrategy-ai
823

find-new-curators

Identify missing vault curators from vault databases and propose curator feeder YAML entries.

Official
Advanced
diegoscarabellidiegoscarabelli
9

project-restart

Restore archived project agents and operational context for data engineering workflows.

Community
Intermediate
typeclawtypeclaw
53

typeclaw-cron

Schedule recurring jobs via JSON cron configuration with timezone support.

Official
Intermediate
leefowlerculeefowlercu
6

deleting-op-secrets

Delete or archive 1Password secrets using the op CLI.

Community
Intermediate