Small, automatable steps of white-collar work — the kind of admin and knowledge tasks an AI skill could take off your plate. Browse by domain, filter by role, see how automatable each one is today.
Scrolling 2,820 tasks to find the one that fits your week is a chore. So don't. Copy the prompt, paste it into Claude Code (or whatever agent you run), and it'll pull this whole catalog, ask you a few questions about your actual work, and come back with one skill worth building. The atlas is the inspiration, not the menu. the raw tasks.yaml →
You're going to help me find one concrete task in my work that's worth handing to an AI skill, and shape it into a proposal I could actually build. First, fetch this file. It's a catalog of ~2,800 small, automatable knowledge-work tasks, each tagged with domain, roles, inputs/outputs, tools, how automatable it is, and how much human oversight it needs: https://stuff.barts.space/skill-atlas/tasks.yaml It's ~2MB, so download and skim or sample it rather than reading every line. Use it as inspiration for the shape of a good automatable task, not as a fixed menu. The right answer for me might not be in there at all. Then interview me. Ask one question at a time, and use each answer to steer the next question. Start broad, then get specific. Worth digging into: - My role, and what a normal week actually looks like - Which tasks are repetitive, boring, or eat time I'd rather spend elsewhere - The tools and systems I live in day to day - Where the same kind of work comes back again and again (daily/weekly/monthly) - What I'd happily hand off, and what has to stay under my control Keep going until you have a clear picture. Don't rush to an answer after one or two questions. When you understand my work well enough, propose ONE skill. Keep it concrete and well-scoped (one task, not "automate my job"). Cover: - The task, in one or two plain sentences - Why it fits me specifically (tie it back to what I told you) - The inputs it needs and the outputs it produces - How automatable it really is, and where a human should stay in the loop - Roughly how it'd be triggered (what I'd type, or what kicks it off) If a task from the atlas fits, borrow from it. If something better came out of our conversation, go with that instead. Then stop and ask if I like the proposal. If I do, offer to draft the skill for me.