project-portfoliolisted

Use this skill when the user is thinking about their work across many projects at once, over time, rather than the single repo or file in front of them. Trigger it when they ask where things stand across everything they're juggling, what to focus on or do next, or for a weekly/periodic review of what's in flight or gone stale; when they want to start keeping track of ongoing efforts scattered across folders (side projects, a job hunt, open pull requests, writing, personal goals) so they stop losing the thread; when they check whether anything changed since they last synced or need to respond to; when they report progress on a weeks-or-months-long effort; or when they wrap up a session and say to log, save, or remember where they left off. This is a persistent, cross-session tracker for long-lived work — not for planning a single task, one-repo status, or one-off questions about the current codebase.
mc856/project-portfolio · ★ 1 · Data & Documents · score 72

Install: claude install-skill mc856/project-portfolio

# Project Portfolio A file-based memory layer for long-term projects. Coding agents naturally scope to one folder and one session; the things people actually pursue — a job search, several side projects, contributions across repositories — span many folders and many months. This skill closes that gap with plain markdown files the user owns: one file per project, plus a global watchlist that makes syncing cheap and follow-ups automatic. ## Data home All state lives in `~/project-portfolio/` (resolve the user's home directory for the current environment; in sandboxes it may be mounted elsewhere). - One file per project, named with a short slug: `job-hunt.md`, `blog-rewrite.md`, `acme-widgets.md`. - `_watchlist.md` holds global sync state and triggers (see below). - Create the directory and files on first use. Keep this directory outside any git repository by default — the data belongs to the user alone. If the user wants it versioned or synced across machines, let them opt in. When the user starts tracking a new project, create its file by **routing to a template and bootstrapping from evidence** — see "Creating a project file" below. ## Creating a project file **Route to a template.** Infer the domain from what the user says and — when the project has a folder — its actual contents (README, recent commits, open TODOs). Match against the table at the end of this file; no clear match means `templates/project.md`, the generic shape. Templates are starting shapes, not schem