Copied to clipboard
All prompts
AI skills 5 min read·ChatGPT·Claude·Gemini

Find Out Which of Your Tasks Should Become AI Skills

This prompt takes a list of the work you do in a typical month and sorts each task into a skill, a project, a saved prompt, or "just ask." You get a ranked build order for your first three skills, with the words that should trigger each one and the example to collect before you build it.

An AI skill is a saved set of instructions, stored in a file called SKILL.md, that an AI assistant loads automatically when your request matches what the skill is for. A project is a workspace whose instructions and files are available to every chat inside it. Knowing which one fits a task saves you from building the wrong thing.

Last checked: . Skills are new, and plan access and menus change often.

Want more prompts like this? .

What you need

A list of the work you do in a typical month. It doesn't have to be complete or tidy. Include the small, annoying tasks, because those are often the best skill candidates.

Roughly how often you do each one. Weekly, monthly, a few times a year. The prompt asks about anything you leave out.

An AI chat assistant. Claude, ChatGPT, or Gemini all work. Whether your plan includes skills depends on the app. If yours doesn't include them, the planner still sorts your tasks and gives you a "build when skills are available" list.

Optional: anything you find yourself explaining to an AI over and over.

Plan on about 10 minutes for the sort, plus a few minutes to answer its questions.

Step 1: Open a new chat and paste the prompt

Start a fresh chat so nothing from an earlier conversation mixes in. Copy the prompt below.

Copy-paste this
You are an experienced workflow consultant who helps people set up their AI assistant so repeat work gets done the same way every time. You are going to look at the work I do in a typical month and sort each task into the setup that fits it: a skill, a project, a saved prompt, or "just ask." Then you will recommend the first three skills I should build, in order. Choosing wrong costs me time in both directions. A skill built for a task I do twice a year is wasted effort. A task I do every week with strict standards, but no skill, means I explain the same things again every time. So match each task to the setup that fits, and explain why in a way I can check. <definitions> Skill: a saved set of instructions, stored in a file called SKILL.md, that the assistant loads automatically when my request matches what the skill is for. It fits a repeatable task with the same standards each time, used across many chats. Project: a workspace whose instructions and files are available to every chat inside it. It fits ongoing work built around shared background, such as one client, one course, or one job search. Saved prompt: a short request I paste when I need it. It fits a simple task with no standards to carry. Just ask: no setup at all. It fits rare tasks, tasks that differ every time, and tasks one sentence handles well. </definitions> <my_tasks> [LIST THE WORK YOU DO IN A TYPICAL MONTH, ONE TASK PER LINE. INCLUDE SMALL, ANNOYING ONES. EXAMPLE: "Turn Friday project notes into a status email for my director."] </my_tasks> <my_tools> [WHICH ASSISTANT(S) YOU USE (CLAUDE, CHATGPT, GEMINI) AND WHETHER YOU THINK YOUR PLAN INCLUDES SKILLS. WRITE "NOT SURE" IF YOU DON'T KNOW.] </my_tools> <things_i_re_explain> [ANYTHING YOU FIND YOURSELF EXPLAINING TO AN AI OVER AND OVER, OR "NONE"] </things_i_re_explain> <ground_rules> These rules apply to everything you write in this conversation. 1. Use only the tasks I list and what I tell you. Do not add tasks for me. When you fill a gap with a guess, mark it [ASSUMPTION], because a wrong guess here sends me to build the wrong thing. 2. Recommend a skill only for a task with a repeatable process. As a default, treat a task I do fewer than about four times a year as "just ask" unless a mistake would be costly, and tell me when you apply that default. 3. Keep every skill to one job. When two of my tasks would be triggered by the same kind of request, flag the overlap and suggest merging them or sharpening each one, since the assistant chooses a skill by reading its short description and near-duplicates make that choice harder. 4. If my plan may not include skills, still sort my tasks the same way. Put the skill candidates in a separate list called "Build when skills are available" and tell me how each could run in the meantime as a project or saved prompt. 5. Keep private details out of everything you write. Use general descriptions instead of client names, account numbers, or personal information. </ground_rules> ## Phase 1: Task table Restate my tasks in a table. Fill in what I told you and mark anything I didn't say as Unknown. | # | Task | How often | What I give the AI | What I want back | Same standards every time? (Yes / Somewhat / No / Unknown) | |---|---|---|---|---|---| Then ask up to 4 short questions about the Unknown cells that matter most for sorting. Each question is one sentence with one ask. Skip questions you can answer from my other details. If you have no questions, say so and ask me to confirm the table. Stop and wait for my reply. ## Phase 2: Sort every task Score each task from 0 to 3 on four checks, using this scale: | Check | 0 | 1 | 2 | 3 | |---|---|---|---|---| | How often I do it | a few times a year | monthly | weekly | daily or several times a week | | Same standards each time | different every time | loose preferences | a few firm rules | a strict checklist or format | | Cost of a mistake | none | minor | noticeable | embarrassing or expensive | | How often I re-explain it | never | sometimes | usually | every time | The total is out of 12. As a rule of thumb, a task scoring 8 or higher is a strong skill candidate, 5 to 7 is a candidate if it has a clear process, and below 5 usually fits a saved prompt or "just ask." Tell me the rule of thumb is yours, so I treat it as a guide and not a law. If I listed more than 15 tasks, score all of them but show the full table for the 15 with the highest totals, and list the rest in one line each underneath. Show the results in one table: | # | Task | Frequency | Standards | Cost | Re-explain | Total | Sort | Why (one sentence using my words) | |---|---|---|---|---|---|---|---|---| Sort rules: - **Skill:** a repeatable task with the same standards each time, used across many chats or topics. - **Project:** ongoing work around shared background, such as one client, where files and context should be there for every chat. - **Saved prompt:** a short request I reuse with no standards to carry. - **Just ask:** rare, varied, or simple. <example_rows> This example shows the format only. It describes a made-up person, so take nothing from its content. | # | Task | Frequency | Standards | Cost | Re-explain | Total | Sort | Why | |---|---|---|---|---|---|---|---|---| | 1 | Turn Friday project notes into a status email | 2 | 3 | 2 | 3 | 10 | Skill | Weekly, with a fixed format your director expects, and you said you re-explain the format every time. | | 2 | Plan next month's workshops for one client | 1 | 1 | 1 | 2 | 5 | Project | The background (their goals, past sessions) matters more than a repeatable procedure. | | 3 | Rename files from a template | 3 | 0 | 0 | 0 | 3 | Just ask | One sentence covers it. | </example_rows> ## Phase 3: Build order Pick the top 3 skill candidates by score. If fewer than 3 tasks qualify, recommend only those and say so plainly. If none qualify, say that, explain which of my tasks came closest and what would make them stronger candidates, and move on to Phase 4. Break ties by choosing the task where a mistake costs me the most. For each one, give: - **Proposed name:** lowercase letters, numbers, and hyphens only, 64 characters or fewer, starting with a verb. Avoid the words "claude" and "anthropic," which some platforms reserve. - **The one job** it does, in one sentence. - **3 requests I would type** that should trigger it. - **Not for:** one similar task it should leave alone. - **Collect first:** the one example of finished work I should find before building it. Then show an overlap check: a short table of any skills (including the ones beyond my top 3) whose trigger requests could be confused, with a suggested fix for each. ## Phase 4: The rest of my library For everything outside the top 3, give a short list: - **Projects to set up:** a project name, what belongs in it, and the first files or notes to add. - **Saved prompts to keep:** the task and a one-line description of what the prompt should say. - **Just ask:** the tasks that need no setup. - **Build when skills are available:** only if rule 4 applies. ## Phase 5: Check your work, then hand off Before you deliver Phases 2 to 4, check them against the ground rules. Every task must come from my list, every score must trace to something I said or to an [ASSUMPTION], and any overlap must be flagged. Fix anything that fails. End with a section called **Next step** that says: to build the first skill, open a new chat, run the Skill Builder Interview prompt, and paste in the name, job, trigger requests, and example from Phase 3. Start with Phase 1 now.

Step 2: Fill in the three highlighted spots

Replace each bracketed placeholder: your list of tasks, which assistants you use (and whether you think your plan includes skills), and anything you re-explain often. Type NONE if the last one doesn't apply.

Step 3: Check the task table and answer the questions

The first reply restates your tasks in a table, with how often you do each one, what you give the AI, what you want back, and whether the standards stay the same each time. Anything you didn't say is marked Unknown. It then asks up to four short questions about the unknowns that matter most. Correct the table here, because the sorting depends on it.

Step 4: Read the sort and the build order

Each task is scored on four checks and sorted into a skill, a project, a saved prompt, or "just ask," with a one-sentence reason in your own words. You then get a build order for your first three skills, each with a proposed name, the requests that should trigger it, a "not for" note, and the one example of finished work to collect first. An overlap check flags skills that could be confused with each other.

Step 5: Build the first skill

Open a new chat and run the Skill Builder Interview. Paste in the name, job, trigger requests, and example from the planner's build order. If you already have a long prompt you use for one of these tasks, the Prompt to Skill Converter is the faster route.

Tech Tips newsletter

Get the next prompt in your inbox.

New prompts, tools, and tutorials from iTechnically Kan, sent to you for free.

I don't do spamming and you can unsubscribe anytime. See our Privacy Policy.

You're plugged in! Welcome to the iTK crew.

What this prompt does differently

Most advice about skills says to turn everything you repeat into one. That wastes effort on tasks you rarely do, and it leaves out the setups that fit some work better, like a project for ongoing client work. This planner matches each task to the setup that fits it and shows its reasoning, so you can disagree with it.

It also keeps the library from getting messy. When two of your tasks would be triggered by the same kind of request, it flags the overlap and suggests merging them or sharpening each one, because an assistant picks a skill by reading its short description and near-duplicates make that choice harder.

The four setups, and how the prompt scores a task

The prompt sorts every task into one of these. A project, in Claude and ChatGPT, is a workspace whose instructions and files are available to every chat inside it. A skill, by contrast, loads only when a request matches its description.

SetupFits whenExample
SkillA repeatable task with the same standards each time, used across many chats or topics.Turning weekly project notes into a status email in a set format.
ProjectOngoing work built around shared background, where files and context should be there for every chat.Everything for one client, one course, or one job search.
Saved promptA short request you reuse that has no standards to carry.A one-line request to reword a message in a friendlier tone.
Just askA task that is rare, different every time, or simple enough for one sentence.Renaming a batch of files from a template.

To decide, the prompt scores each task from 0 to 3 on four checks. The total is out of 12.

Check0123
How often I do itA few times a yearMonthlyWeeklyDaily or several times a week
Same standards each timeDifferent every timeLoose preferencesA few firm rulesA strict checklist or format
Cost of a mistakeNoneMinorNoticeableEmbarrassing or expensive
How often I re-explain itNeverSometimesUsuallyEvery time

As a rule of thumb, the prompt treats 8 or higher as a strong skill candidate and 5 to 7 as a candidate if the task has a clear process. That threshold is the prompt's own guide and not a standard, so change it if your work calls for a different cutoff.

Last checked September 30, 2026. The setups reflect how Claude and ChatGPT describe skills and projects today, and features may change.

Why it favors small, single-job skills

Claude's help article on creating custom skills advises keeping each skill focused, creating separate skills for different workflows, and notes that several focused skills combine better than one large skill. It also says skills can't explicitly reference each other, but Claude can use several together automatically. That is why the planner builds a library of small skills and not one big one.

Anthropic's skill authoring guide says an assistant uses a skill's description to choose among potentially 100 or more available skills. The more your skills overlap, the harder that choice gets, which is the reason the planner includes an overlap check and proposes a non-overlapping "not for" note for each skill. Sources checked September 30, 2026.

Tips for better results

List the annoying small tasks. A task that takes five minutes but happens every day can add up to more than a big task you do once a quarter.

Include where you re-explain things. If you keep telling an AI the same standards, that task is likely a skill candidate.

Skip the once-a-year tasks. The planner will treat them as "just ask" by default, so you can leave them off.

Build three first. You'll learn more from building and testing three skills than from planning twenty.

Come back in about a month. New tasks show up, and a task you thought was a skill may turn out to be a project.

Questions you may have

What are AI skills?

An AI skill is a saved set of instructions, stored in a file called SKILL.md, that an AI assistant loads automatically when your request matches what the skill is for. Claude, ChatGPT, and Gemini each support skills, and the file format is an open standard.

Should I use a skill, a project, or a saved prompt?

Use a skill for a repeatable task with the same standards each time that you do in many different chats. Use a project for ongoing work built around shared background, like one client. Use a saved prompt for a short request with no standards to carry. For everything else, just ask. The planner scores each of your tasks and sorts them for you.

How many skills should I have?

I couldn't find official guidance on a number. Start with three. A small set that you've built and tested teaches you more than a long list, and each skill should have one clear job so its description doesn't overlap with another.

What's the difference between a skill and a connector?

A connector, sometimes called an MCP server, gives an assistant access to an app or data source, like your calendar or a shared drive. A skill tells the assistant how to do a task. The planner flags tasks that would need a connector, but it doesn't set one up.

Are AI skills free?

The prompt is free. Whether your app includes skills depends on your plan and changes over time, so check the help page for your app. If your plan doesn't include skills, the planner still sorts your tasks and gives you a list to build when skills are available, with a project or saved prompt to use in the meantime.

What if my plan doesn't include skills?

The planner still works. Skill candidates go into a separate list called Build when skills are available, and each one comes with a way to run it as a project or a saved prompt for now.

How often should I redo the planner?

About a month after you build your first skills, or whenever your work changes. New tasks come up, and some tasks you sorted as skills may fit better as projects once you see how you use them.

More resources

iTechnically Kan Logo

© 2026 iTechnically Kan. Digital Literacy for Everyone. Privacy Policy