things-mac

7

openxjarvis

Things 3 task manager integration for macOS

things:url

7

bendrucker

Create, update, and manage Things 3 tasks and projects. Not for reads — use things:jxa to query data. For simple inbox captures, use things:inbox.

things:inbox

7

bendrucker

Quick captures to the Things 3 inbox. Not for reads (things:jxa), scheduled tasks, updates, or projects (things:url).

separation-of-concerns

6

yanko-belov

Use when component does too many things. Use when mixing data fetching, logic, and presentation. Use when code is hard to test.

wordpress-ability-api

6

emdashcodes

This skill should be used when helping users create, edit, or register WordPress Abilities (both server-side PHP and client-side JavaScript), register ability categories, or set up the WordPress Abilities API as a dependency. Use when users say things like "create an ability", "help me build an ability", "set up the Ability API", or "register a category".

productivity-gtd

5

sunnypatneedi

Master the Getting Things Done (GTD) methodology for stress-free productivity. Implement capture, clarify, organize, reflect, and engage workflows with contexts, projects, and weekly reviews.

inner-life-evolve

4

DKistenev

Your agent does the same things the same way forever. inner-life-evolve analyzes patterns, challenges assumptions, and proposes improvements — writing proposals to the task queue for user approval. Never auto-executes. Evolution with a safety net.

structure-app

4

rohunvora

Structure an app around objects when starting a complex app from scratch, existing navigation feels messy, users can't find things, or the IA is getting worse as features are added. Use Object-Oriented UX to design around nouns, not verbs.

interviewing-plans

4

galihcitta

Use when a plan, PRD, or spec has vague requirements, undefined terms, or missing details - conducts structured interview using AskUserQuestion to surface hidden assumptions, challenge ambiguities, and produce implementation-ready specs. Also use proactively when encountering plans that say things like "make it faster" or "improve UX" without concrete definitions.

patent-figure

3

pbc-os

Generate and iteratively refine USPTO-style patent figure drawings from provisional patent application markdown files. Use this skill whenever the user wants to create, generate, draw, or render a patent figure, diagram, or drawing for a provisional patent application. Also use it when the user wants to iterate on or fix an existing patent figure, or when they say things like "generate the figures for my patent", "make a patent drawing", "create FIG. 1", or "fix this arrow in my patent diagram". Requires nano-banana skill (Gemini API).

patterns

2

nklisch

Project code patterns and conventions. Auto-loads when implementing, designing, verifying, or reviewing code. Provides detailed pattern definitions with code examples. Consult this whenever writing new code, reviewing changes, or trying to understand how this project structures things.

dream

2

pjt222

AI unconstrained creative exploration — deliberately dropping structure to let associations form freely. The one skill that inverts the standard procedure format: instead of inputs, steps, and validation, dream opens space for emergence without evaluation. Use before design work, before naming things, before choosing between approaches, or anywhere that premature structure kills the best option.

knowledge-architecture

2

organvm-iv-taxis

Design knowledge systems using ontological principles—organizing by what things ARE rather than arbitrary hierarchies. Use when structuring personal knowledge bases, designing documentation systems, creating cross-domain linking patterns, building the {OS.me} ecosystem, or architecting information that reveals rather than obscures essential nature. Triggers on knowledge management, documentation architecture, information ontology, or systematic organization of complex domains.

dream

2

pjt222

AI unconstrained creative exploration — deliberately dropping structure to let associations form freely. The one skill that inverts the standard procedure format: instead of inputs, steps, and validation, dream opens space for emergence without evaluation. Use before design work, before naming things, before choosing between approaches, or anywhere that premature structure kills the best option.

refactor

1

flitzrrr

Structured refactoring workflow that ensures safety. Verifies tests pass before AND after refactoring, applies minimal diffs, checks for regressions, and updates documentation. Prevents the common problem of refactors that silently break things.

zenml-scoping

1

zenml-io

Scope and decompose ML workflow ideas into realistic ZenML pipeline architectures. Runs an in-depth interview to help users break down ambitious or over-engineered plans into well-composed multi-pipeline setups, identify what belongs in a pipeline vs. what doesn't, define cross-pipeline data flow via the Model Control Plane, and select an MVP to build first. Produces a pipeline_architecture.md specification document. Use this skill whenever a user describes a complex ML workflow, mentions multiple pipelines, talks about end-to-end ML platforms, asks how to structure their ML system in ZenML, or seems to be over-engineering their pipeline design. Also use when the user's pipeline idea sounds like it's trying to do too many things at once, or when they ask about composing pipelines together. Even if the user just says "I want to build an ML pipeline" with a long list of requirements, this skill helps scope it down before the pipeline-authoring skill takes over.

production-resilience-reviewer

1

tomazb

Senior-level production resilience and failure-mode review for any code, function, service, or system design — especially AI-generated code. Use this skill whenever the user asks you to review code for production readiness, resilience, failure modes, operational concerns, or reliability. Also trigger when the user asks about: error handling quality, retry logic, circuit breakers, timeout strategies, graceful degradation, observability, rate limiting, backpressure, dependency failure analysis, SLA impact, cascading failure risk, on-call debuggability, rollout safety, migration risk, rollback strategy, deploy risk, or when they say things like "is this production-ready?", "review this for ops", "what could go wrong?", "will this survive real traffic?", "review like a senior engineer", or "what would break at scale?". Trigger aggressively — if there's code and the user wants a quality review, this skill applies.

debug

1

XDongiang

Debug container agent issues. Use when things aren't working, container fails, authentication problems, or to understand how the container system works. Covers logs, environment variables, mounts, and common issues.

hard-thing-about-hard-things

1

defi-naly

Ben Horowitz's battle-tested advice for leading through crises, making hard decisions, and building companies.

hidden-potential

1

defi-naly

Adam Grant's research on achieving greater things through character skills, not just talent.

de-drama

1

macakuaya

Disco Elysium DRAMA skill: detecting lies and deception in code. Activates during code review and refactoring when functions mislead with their names, comments contradict implementation, or tests pretend to test things they don't.

de-drama

1

macakuaya

Disco Elysium DRAMA skill: detecting lies and deception in code. Activates during code review, refactoring, when functions mislead with their names, comments contradict implementation, or tests pretend to test things they don't.

competitor-research

1

yanchuk

Research competitors by gathering and analyzing community feedback from Reddit, forums, and review sites. Use this skill whenever the user asks to research a competitor, gather community feedback about a product, analyze Reddit discussions, do competitive intelligence, or says things like "research [product]", "what do people say about X", "gather reddit feedback for", "analyze competitor", or "community sentiment about". Also use when the user provides a list of Reddit URLs to analyze.

things-mac

jiangpingT

Things 3 任务管理工具。支持创建、查询、更新、完成待办事项,管理项目和区域。适用于"添加待办"、"查看今日任务"、"标记完成"、"创建项目"等查询。仅支持 macOS,需要 Things 3 应用。

ghost

rana

Hidden dependency and assumption detector. Surfaces things the system depends on that aren't explicit — environment variables, implicit service dependencies, timing assumptions, undocumented contracts. The things that break at 2am.

debug

ziggythebot

Debug container agent issues. Use when things aren't working, container fails, authentication problems, or to understand how the container system works. Covers logs, environment variables, mounts, and common issues.

agent-config-sync

liamdmcgarrigle

MUST be used whenever the user wants to add, install, find, or search for a skill, MCP server, or plugin. Also use when setting up cross-tool agent syncing across Claude Code, OpenCode, Codex, and Cursor. This skill ensures all tools stay identical by installing to Claude Code first and syncing via vsync. Use PROACTIVELY when the user says things like "add an MCP server", "find a skill for X", "install a plugin", "add a tool", "search for skills", "set up MCP", "I need a skill that does X", "add svelte MCP", or any request to add capabilities to the agent. Also triggers on: vsync, cross-tool parity, agent sync, evaluating AI tools, /setup-agent-sync, /find-skill, /add-skill-submodule, /find-mcp, /update-agent-tools.

ghost

rana

Hidden dependency and assumption detector. Surfaces things the system depends on that aren't explicit — environment variables, implicit service dependencies, timing assumptions, undocumented contracts. The things that break at 2am.

things-mac

nweii

Manage Things 3 on macOS via CLI. Read, search, add, or update tasks, projects, and areas. Use for task management, listing inbox/today, and inspecting tags or repeating templates.

build-fixer

awojtas

Iteratively fix build errors and lint warnings until the project compiles cleanly. Use this skill whenever the user mentions build failures, compilation errors, "fix the build", "make it compile", broken builds, CI failures related to compilation, lint errors, linting issues, "run lint", "fix lint warnings", or any variation of "the build is broken" or "fix these errors". Also trigger when the user pastes compiler output, build logs, or says things like "I'm getting errors when I build" or "can you get this to compile". Covers .NET (dotnet build), Node.js (npm/pnpm/yarn build), and other common build systems.

cowboy

socalfinanceinsights

Chief problem solver — investigations, audits, ad hoc multi-agent tasks, routing. Activates on '/cowboy', 'audit this', 'investigate', 'figure out what's wrong', 'check for conflicts', 'what happened here', 'handle this', or when work requires heterogeneous agents doing different things.

apple-reminders

jiangpingT

访问和管理 macOS 苹果提醒事项（Apple Reminders）。适用于"查看提醒"、"查看今日提醒"、"待办提醒"、"创建提醒"、"完成提醒"、"提醒清单"等请求。仅支持 macOS，需要 Apple Reminders 访问权限。注意：这是 Apple 自带的提醒事项，不是 Things 3。依赖：remindctl（brew install steipete/tap/remindctl）。

dobby

zl190

Summon Dobby to work on substantial tasks autonomously in the background. Use when the user wants to delegate a project (research paper, build an app, design a system) to an autonomous agent that works while they do other things. Triggers on "dobby", "summon", "cast", "delegate project", "run in background", "work on this while I".

git-workflow-automator

Orchardxyz

This skill automates the complete git workflow for personal projects. Use this skill when the user has staged changes and wants to create a new branch, generate a conventional commit message, add a changeset, and open a pull request. This skill should be triggered when users say things like "commit these changes", "create a PR", "I want to commit and open a pull request", or indicate they have staged changes ready to commit. The skill also detects when the user is on a protected branch (main, master, admin) and prompts them to create a new feature branch.

error-recovery

Dragoon0x

When things break, guide people forward instead of leaving them stranded. Error message copy, retry patterns, graceful degradation, and recovery flows. Use when building error handling or failed state UIs.

copy-editing

oki3505F

Use this when the user wants to edit, review, or improve existing marketing copy. Also use when the user says things like 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' or 'copy sweep.' This skill provides a systematic approach to editing marketing copy through multiple focused passes.

service-map

vesviet

Quick-reference map of all microservices — locations, ports, dependencies, gRPC clients, event consumers, GitOps config, and where to find things

fixer

petekp

Cold, methodical diagnostician for when you're stuck in agent-assisted app development. Call the fixer when: (1) You're in a loop with a coding agent and things keep getting worse, (2) Your project has accumulated so many agent-generated changes you've lost the thread, (3) Builds are broken and you can't figure out why, (4) You've tried multiple approaches and none are working, (5) You need someone to cut through confusion and give you a clear path forward. Triggers on: "I'm stuck", "nothing is working", "help me fix this", "I'm going in circles", "the agent keeps breaking things", "I've lost track of what's happening", "can you take a look at this mess", or any expression of frustration with agent-assisted development. The fixer does not commiserate — it diagnoses, intervenes, and unblocks.

risk-management

Dragoon0x

Identify, assess, and mitigate product risks before they become fires. Covers risk categorization, mitigation strategies, and communication frameworks. Use when planning complex launches, managing dependencies, or when too many things could go wrong.

design-everyday-things

bilalmirza2001

Fundamental design principles based on Don Norman's "The Design of Everyday Things". Use when you need to: (1) design affordances and signifiers into interfaces, (2) analyze why products are confusing, (3) apply constraints to prevent errors, (4) design clear feedback mechanisms, (5) bridge gulfs of execution and evaluation, (6) create intuitive conceptual models, (7) apply human-centered design, (8) understand why users make errors and design fault-tolerant systems.

codebase-study-guide

petekp

Generate a pedagogically-grounded study guide for learning an unfamiliar codebase. Use when the user wants to onboard onto a codebase, understand a project's architecture, create learning materials for a team, or asks things like "help me learn this codebase", "create an onboarding guide", "I'm new to this project", "how does this system work", "study guide for this repo", or "explain this codebase to me". Produces a structured document that builds understanding from purpose to systems to patterns, using evidence-based learning techniques (elaborative interrogation, concept mapping, threshold concepts, worked examples, progressive disclosure).

code-review

Cygnusfear

This skill should be used when reviewing pull requests, performing comprehensive code review, analyzing code changes before merge, or when the user asks for thorough/ultra-critical code review. Performs EXTREMELY CRITICAL 6-pass analysis identifying runtime failures, code consistency issues, architectural problems, environment compatibility risks, and verification strategies. Posts structured review to the active platform (GitHub PR, Forgejo MR, or tk ticket). Use when user asks to "review PR", "review this code", "review changes", "check this PR", "analyze PR", "post review", or for Phase 3 of devflow. Supports parallel review mode with multiplier (code-review-3, code-review 6X) for consensus-based reviews. This is an ultra-critical reviewer that does not let things slip and desires only perfection.

metrics-measurement

Dragoon0x

Design and maintain a metrics framework that tells you whether your product is healthy. Covers metric selection, hierarchy, and the difference between tracking and understanding. Use when metrics feel arbitrary, the team tracks too many things, or nobody agrees on what success looks like.

caprover-deploy

guim4dev

Deploy apps to CapRover and set up GitHub Actions CI/CD workflows for new or existing projects. Use when the user says things like "deploy X", "trigger a deploy of X", "deploy branch Y to Z", "set up CI/CD for this project", "configure CapRover deploy workflow", "add deploy workflow to my repo", or asks about deployment status. Supports GitHub workflow triggers, CapRover webhook triggers, and direct CLI deploys. Also helps scaffold .github/workflows/deploy.yml, captain-definition, and GitHub secrets for any new project.

launch-checklist

Dragoon0x

Everything that needs to be true before real people see this. Pre-launch audit covering copy, meta tags, error states, mobile, performance, analytics, and the things everyone forgets. Use before any launch or public release.

project-to-ci-template

Orchardxyz

This skill should be used when the user wants to summarize a project and convert it into a CI template project. It analyzes project structure, tech stack, and architecture, then generates comprehensive documentation and GitHub Actions CI/CD workflows for web applications and backend services. Use this when users say things like "summarize this project", "make this a CI template", "create a template from this project", or "document this project with CI/CD setup".

readme-formatting

guillaumeduhan

Generate polished, professional README.md files that follow a proven structure used in production back-office and SaaS APIs. Use this skill whenever the user asks to create, rewrite, improve, or format a README or project documentation in Markdown. Also trigger when the user says things like "document my project", "write a README", "make my README look professional", "format my docs", or uploads a codebase and asks for documentation. Even if the user just says "README" or "docs for this repo", use this skill. Do NOT use for non-README markdown files like blog posts, changelogs, or contribution guides — those have different conventions.

sync-things-tasks

nweii

Syncs tasks between Obsidian vault and Things 3. Adds tasks from notes, extracts action items from projects, reviews existing tasks. Use when managing todos from vault content.