tteschon/work-skills

Authors and maintains the agent skills in this repository - a SKILL.md that triggers correctly and passes all three validators, plus the plugin manifests and marketplace entries that scripts/validate.py enforces. Use this skill when the user wants to write a new skill, add one to any existing plugin such as work-skills or fun-skills, scaffold a new plugin in any category, rename or restructure an existing skill, split a long SKILL.md into references, or fix a failing skills validation or CI run. Also use it when the user mentions SKILL.md, the agent skills format, Agent Plugins, marketplace.json, .codex-plugin, .claude-plugin, or skills.sh packaging, and when they ask how skills in this repo are laid out. Do not use it to invoke an existing skill - only to author, package, or repair one.

Sets up Python projects with the modern uv toolchain - uv for packages and environments, ruff for lint and format, pytest for tests, ty for type checking, and pre-commit to run them on every commit. Use this skill when the user starts a new Python project, package, CLI, library, or service; when they want to add testing, linting, formatting, or type checking to an existing Python directory; when they ask to turn a script or legacy project into a proper package; or when they mention uv, ruff, pytest, pre-commit, pyproject.toml, or src layout. Also use it when the user asks for a Python project without naming any tooling, or reaches for pip, venv, requirements.txt, poetry, or setup.py - the setup should still go through uv. Do not use it to add a runtime dependency to an already-configured project.

Reviews the health of an Obsidian note-per-task base and reports what has drifted - one-time tasks with no due date, recurring tasks that have silently stopped recurring, and finished one-time tasks waiting to be swept out. Use this skill when the user wants a periodic look at the task system as a whole rather than a change to one task - groom my tasks, review my task backlog, audit my tasks, what is stale, what has gone unscheduled, is my task list healthy, why does this task never show up in my Today view, clear out my finished tasks, sweep the done ones. Also use it when the user mentions task hygiene. This skill owns the sweep - it deletes finished one-time tasks to the vault trash, naming every note and taking a confirmation first. Adding a task, completing one, rolling a recurring chore forward, and asking what to work on next all belong to obsidian-tasks; general vault work belongs to obsidian-vault.

Creates and manages task notes in an Obsidian vault - one note per task, identified by a type property set to task and collected by a Bases file, carrying a done checkbox, due, priority, category, and an RRULE frequency. Use this skill when the user wants to add a task, mark one done, change its priority or due date, roll a recurring chore forward after doing it, or ask what to work on next - what are my top tasks, what is overdue, what should I do this weekend, add mowing the lawn to my tasks, I just changed the oil. Also use it when the user mentions their task base, a task repo, a task note's done state or frequency, or a backlog of home, yard, or vehicle chores. Do not use it for checkbox tasks inline in note bodies - what the obsidian tasks command lists - do not use it to review the whole base or to sweep out finished tasks - groom my tasks, what is stale - which is obsidian-task-grooming; and do not use it for general vault reading, searching, or note editing - obsidian-vault covers those.

Reads, searches, and edits an Obsidian vault through the obsidian command line interface - notes, daily notes, frontmatter properties, tags, backlinks, and templates. Use this skill when the user wants to find something in their notes, read or summarize a note, capture a thought into today's daily note, create or append to a note, retag or move files, or trace what links to what. Also use it when the user mentions Obsidian, their vault, a daily note, a wikilink, or the obsidian CLI - and when they say things like "add this to my notes", "what did I write about X", or "put that in today's note" without naming the tool. Do not use it for Markdown files outside a vault, or to edit this repository's own docs - the ordinary file tools are better for those. For a vault where each task is its own note with a done checkbox, due, priority, and frequency frontmatter, use obsidian-tasks instead.