← ClaudeAtlas

slipstreamlisted

Builds and guides a personalized, self-updating learning curriculum for staying current in a fast-moving field. On first use it interviews the user, researches the current landscape, and generates a tailored plan. On later use it recommends the next study block sized to available time, runs the session, tracks completion, and keeps the curriculum current against new developments. Use this skill whenever the user wants to catch up on or stay current with a field, build a study plan or learning roadmap, asks "what should I learn next", says "slipstream" or "catch-up session" or "briefing", or wants to track progress through self-directed learning. Trigger it even when the user only describes the goal ("I've fallen behind on AI", "help me get up to speed on X") without naming a plan.
wheelhouseatl/slipstream · ★ 1 · AI & Automation · score 64
Install: claude install-skill wheelhouseatl/slipstream
# Slipstream A self-directed learning system for busy professionals who need to catch up on or stay current with a fast-moving field. It builds a personalized curriculum, guides the user through it one session at a time, tracks what they have done, and keeps the plan current as the field changes. The system is file-based by design. All state lives in three markdown files in the working folder, not in conversational memory. This makes progress durable, inspectable, and versionable, and means any fresh session reconstructs full context by reading the files. Never rely on memory of prior conversations for state; read the files. ## Requirements and setup This skill reads and writes files, so it needs a connected working folder (for example, a Claude Cowork session with a local folder connected, or any environment with filesystem access). If you cannot read or write files in the current environment, say so plainly and tell the user the skill needs a connected folder to work, rather than simulating the files in chat. The three state files, all in the working folder: - `PROFILE.md` — who the user is and what they care about. The durable context that every other mode reads. Created once during onboarding, edited rarely. - `PLAN.md` — the curriculum. Generated during onboarding, maintained continuously. - `PROGRESS.md` — the tracker and changelog. Holds completion state and a log of plan changes. An optional fourth file, `ORG.md`, may be present if an organization has deplo