Free to read · no account needed

9 min · skills

Skills vs Custom GPTs vs Projects — which box?

Goal: Pick one box first—Project, Skill, or Custom GPT—and put files, persona, and checklists in the right place.

Best for: Beginners who heard five buzzwords this month.

Pick the lightest tool that fits one job—don't build all three by default.

Why beginners skip this

Mixing the three names feels explanatory—wrong container breaks boundaries and reuse. Diff the table, then choose.

Step 1 — The three boxes in plain words

  • Project = a workspace (files + ongoing context + standing rules).
  • Custom GPT = a reusable ChatGPT assistant with its own instructions and optional files (like a saved specialist).
  • Skill = a reusable playbook for a process; can be called from many chats when the job matches.

Step 2 — Decision table

Pick the box from this table before moving files or persona—do not pile all three.

You need…Start with…
Same PDFs every day + long thread historyProject
A named helper (“Brand voice editor”) inside ChatGPTCustom GPT
Same checklist across many chats/toolsSkill (or Project instructions first)
AI that clicks tools / apps for youAgent + permissions (learn after these three)

Step 3 — Mini exercise

Pick one repeat job, say the purpose in one sentence, then choose a box (Project / Custom GPT / Skill)—or split if you cannot.

My recurring task: _____
Does it need a stack of files? Y/N
Does it need a named persona? Y/N
Is it mainly a checklist/process? Y/N
→ My first box: _____
Example

Filled prompt

My recurring task: Rewrite support macros in our tone
Files? Y (tone guide PDF)
Named persona? Y (“Support tone editor”)
Checklist? Y (forbidden phrases list)
→ First box: Project with the PDF + instructions; later wrap the checklist as a Skill; optional Custom GPT if teammates live in ChatGPT only.

What good output looks like

  • You picked one box to start, not all three at once
  • Files landed in a Project first
  • Skill comes after the checklist is stable
Example

Filled prompt

Job: bilingual client email polish, twice weekly, needs standing glossary file.
Choose skill vs Custom GPT vs Project in a table: setup cost, memory, sharing, when to switch.
Pick one for this month with reason.

What good output looks like

  • Skill purpose is one job for “Skills vs Custom GPTs vs Projects —” — not a company brain
  • Done + golden example present and tested
  • Never-send / never-delete honored
  • Pass/fail: fail-case run once (skills-vs-custom-gpts-vs-projects #1)

Pick one container

One repeat job → one of skill / GPT / Project. Installing all three “to compare” multiplies mess.

Keep it real

Run this guide’s Practice now on work you will actually ship this week—not a fictional scenario. Dated notes beat perfect theory.

Do not bookmark-only

Finish Practice now, then tick this guide on your path. Titles unread are not skills.

Reality check

Open this guide beside a live task. If you cannot name the task, pick one before reading further.

Close the loop

Write one line: next time I start with the three names mashed, I refuse.

Example

Filled prompt

Need bilingual polish + glossary file, twice weekly.
Table: skill vs Custom GPT vs Project. Pick one for this month with reason.

What good output looks like

  • Done + golden example present and tested
  • Never-send / never-delete honored
  • Pass/fail: fail-case run once (skills-vs-custom-gpts-vs-projects #2)
  • Skill purpose is one job for “Skills vs Custom GPTs vs Projects —” — not a company brain

Red flag

Turning on all three boxes for one job; purpose sentence missing—pick one box and write why.

Save this card

Card: purpose in one sentence → pick one box. Write why not the other two before enabling extras.

Before you start

Open the skill card (or blank one-pager). Purpose must be one job for “Pick one box for your next recurring task.” Golden example slot cannot stay empty. Guide: skills-vs-custom-gpts-vs-projects. Keep the real job visible the whole time; a blank box means stop and fetch the artifact first.

How to use this week

This week for one real job compare skill / custom GPT / project fit; pick one before start.

Close the week by quoting aloud the refuse line you actually used once. If you cannot, rerun Practice now and date the pass/fail (Asia/Shanghai).

Pitfalls

PitfallFix
Building all three for one jobPick the lightest that fits
Projects with no instructionsAdd standing rules
Custom GPT with huge unredacted uploadsCurate + redact
Example

Filled prompt

Temptation: skip the habit for skills-vs-custom-gpts-vs-projects to save five minutes.
Job still: Pick one box for your next recurring task
Smallest correct pass: Done visible · checkable artifact · Unknowns [?].
Boundaries: draft only; no silent send; no invented metrics.
Return: artifact + refuse-line said aloud.

What good output looks like

  • Names the shortcut refused (specific to skills-vs-custom-gpts-vs-projects)
  • Still delivers checkable output for “Pick one box for your next recurring task”
  • Unknowns labeled; draft-only
  • Pass/fail: refuse-line dated (skills-vs-custom-gpts-vs-projects #4)

Practice now

Switch cost: estimate minutes to migrate if wrong pick (Asia/Shanghai).

Chooser drill: write loser reasons for the two you did not pick (Asia/Shanghai).

Vs drill: pick skill vs GPT vs project for one job with one reason each loser fails (Asia/Shanghai).

Thin-spot drill: rewrite the Save card with real nouns from your work (repo, doc, inbox). Generic placeholders fail the drill.

Tonight after one sentence of purpose, pick one box—files, persona, checklists in the right place; do not stand up all three this week.

One sentence takeaway

Compare the table; pick one container; no start while names are mashed.

Next

Custom GPTs · Stack

← Back to home · Learn · Tools · Compare · Start