wellcaffeinated
- 11 skills
- 0 followers
- 6 hours ago last updated
- ▌ Notes Daily · wellcaffeinatedDaily-note processing — works through unprocessed daily notes, extracts anything in the prose worth capturing permanently, files it to the right home, and marks each note processed. Use when processing journal backlog, after a stretch of daily note capture, or when the user asks to "process my daily notes" / "catch up on my journal". Read-only unless the user approves proposed actions.
- ▌ Notes Setup · wellcaffeinated bundleOne-time onboarding — orients a user to their Obsidian vault and designs a structure around how they actually want to work, then writes it into the vault (VAULT.md, _Meta/ docs, templates, optional Bases). Use when setting up a new vault for these skills, or when a user says "set up my notebook" / "help me organize Obsidian from scratch".
- ▌ Notes Catchup · wellcaffeinatedWeekly briefing — checks daily notes and project activity to surface what's been neglected, flag what needs attention, and give an opinionated heads-up on what might fall through the cracks. Use when starting the week, returning after time away, or when the user asks "what have I been working on" / "what needs attention" / "what have I neglected". Read-only unless the user asks otherwise.
- ▌ Notes Connect · wellcaffeinatedGiven a note or topic, searches the vault for related notes that aren't yet linked and surfaces potential connections. Use when exploring what connects to a note, when the user asks "what's related to X", or when building a "See Also" section. Read-only unless the user asks to add links.
- ▌ Notes Reflect · wellcaffeinatedPeriodic review of the vault — synthesises recent daily notes, surfaces themes, summarises project activity, and identifies open questions. Use when doing a weekly or monthly review, or when the user asks "what did I work on this week" / "what themes came up" / "reflect on my notes". Read-only unless the user asks to create or modify notes.
- ▌ Notes Organize · wellcaffeinatedInbox processing — reads _Inbox and proposes where each item should be filed or acted on. Use when the inbox has accumulated items, after a capture session, or when the user says "process my inbox" / "clear my inbox". Read-only unless the user approves proposed actions.
- ▌ Notes Surprise · wellcaffeinatedSerendipity engine — pulls random notes from across the vault, finds unexpected connections and patterns, and surfaces ideas the user wouldn't have looked for. Use when the user wants random exploration, asks for a "random note", or says "surprise me" / "show me something interesting". Read-only unless the user asks to create or modify notes.
- ▌ Notes Workflow · wellcaffeinated bundleFoundation skill for all vault operations — verifies the vault connection, reads conventions, and provides CLI patterns. Use when working with the vault directly (creating notes, managing bookmarks, projects, areas) or when invoked by another notebook skill before proceeding.
- ▌ TS Coding Style · wellcaffeinatedTypeScript/JavaScript coding conventions. Apply this skill whenever you're writing, reviewing, or discussing TypeScript or JavaScript code — even if the user hasn't explicitly asked for a style review. Covers naming, function design, guard clauses, dispatch tables, iteration, immutability, modules, logging, and TypeScript-specific patterns (satisfies vs as, enum vs const enum, type vs interface, unknown over any).
- ▌ Youtube Transcript · wellcaffeinated bundleFetches YouTube transcripts as markdown using a bundled script. Use this skill whenever a YouTube transcript is needed — whether the user asks for one directly, pastes a YouTube URL and wants its content, or a transcript would help with the current task (summarising, note-taking, vault ingestion, RAG, etc.).
- ▌ Skill Creation · wellcaffeinated bundleWriting and improving Claude Code agent skills — SKILL.md structure, reference file organization, description trigger phrases, and conventions specific to this marketplace. Use when creating a new skill, refactoring an existing one, reviewing skill quality, or deciding how to split content into reference files.