dotfiles

Create, move, and rename folders and notes in Apple Notes with AppleScript, including HTML-formatted bodies and nested folders. Use when adding, writing, filing, or triaging content in Apple Notes from the command line. Make sure to use this skill whenever a request mentions creating a note, a Notes folder, processing the Notes inbox, moving or retitling an existing note, saving something "in my Notes", or scripting Notes with osascript, even if AppleScript is never named — the apple-notes MCP server is read-only and cannot write.

Implement the PARA Method (Projects, Areas, Resources, Archives) on a local file system outside `~/Documents` and `~/Brain`. Use when setting up PARA from scratch, auditing or cleaning up an existing PARA tree, classifying folders into Projects/Areas/Resources/Archives, or reorganizing a messy folder by actionability. Make sure to use this skill whenever a request mentions PARA, "Second Brain file organization", or asks which folders should be projects vs areas vs resources, even if the user only asks where one folder belongs. For `~/Documents`, use `johnny-decimal` instead.

Turn a manual, repeated procedure into a do-nothing script (Dan Slimmon's gradual automation technique): one function per step, each printing its instructions and waiting for the operator, automated one step at a time. Use when documenting or automating a runbook, checklist, release process, onboarding, incident procedure, or any multi-step manual chore. Make sure to use this skill whenever a request mentions a runbook, checklist, "steps I always do by hand", gradual or partial automation, or asks to script a procedure whose steps cannot all be automated yet, even if the words "do-nothing script" are never used.

Apply this dotfiles repository's configuration and installation conventions. Use when changing dotfiles, symlinks, platform-specific configuration, or tool installation. Make sure to use this skill whenever editing the Makefile or a configuration managed from this repository, even if the request only mentions a single application.

Organize files in ~/Documents with the Johnny Decimal and PARA hybrid system. Use when naming, filing, moving, or locating numbered personal documents. Make sure to use this skill whenever a request concerns Johnny Decimal categories, PARA mapping, or document filenames under ~/Documents, even if the user only asks where a document belongs.

Maintain this repository's Neovim and LazyVim configuration. Use when editing Lua files under nvim/, adding plugins, changing options, or updating keymaps. Make sure to use this skill whenever a request affects LazyVim plugin specifications or Neovim behavior, even if Neovim is not named explicitly.

Create and maintain portable Bash scripts in this repository. Use when adding or editing standalone scripts, shebangs, error handling, or executable tooling. Make sure to use this skill whenever a change touches scripts/ or introduces shell automation, even if the request calls it a helper or hook.

Manage Things 3 tasks, projects, and areas through the thangs CLI. Use when listing Things lists, creating or editing tasks, completing or canceling tasks, managing projects or areas, filtering by project, area, or tag, or inspecting thangs options. Make sure to use this skill whenever the user asks about their todos, Today list, deadlines, or Things data, even if they do not explicitly mention Things 3 or thangs.

Manage .agents/skills: create new skills with proper scaffolding, run doctor checks on existing skills for quality and portability, fix non-conforming skills after a doctor run, detect inter-skill inconsistencies with cross-check, and keep the README index synchronized. Use when creating a new skill, improving an existing skill, modifying a skill's description or frontmatter, fixing doctor findings, detecting trigger overlaps or rule contradictions between skills, organizing the skills directory, or ensuring multi-agent compatibility. Make sure to use this skill whenever authoring a new skill, reviewing skill quality, cross-checking skills for conflicts, restructuring skills, modifying any SKILL.md file (even a single field like description or metadata), applying fixes from doctor, or migrating to the agentskills.io standard, even if you're just tweaking one line in an existing skill — references/conventions.md must be read first.