Getting Started

chatgpt.com Browser Setup

This is the lightweight fallback path for simple browser-based tasks. If you want the real CCOS experience with files, context, and full plugin workflows, use Codex Desktop instead.

You need the CCOS ZIP file to follow this guide. Download it below — this page will verify your active license. If you don’t have one yet, grab a license from the store.

Straight Talk

chatgpt.com is fine for quick tasks. It is not the best way to use CCOS.

Browser ChatGPT is built for conversation-first work. CCOS is strongest on desktop, where your AI can read project files, create new files, keep your context organized, and use the full marketplace and plugin system the way it was designed.

Rob’s straight talk before you continue with the browser setup.

If you are serious about building lessons, pages, context files, or repeatable workflows with CCOS, switch to the Codex Desktop setup instead of spending much time here.

When to use chatgpt.com anyway

  • Use this page if you want a lightweight, one-off browser workflow
  • Use Codex Desktop if you want real CCOS project work across files, folders, and multi-step workflows
  • Unless you are on ChatGPT Business, browser ChatGPT does not officially support skills — most people here are relying on a workaround, not the full system
  1. Unzip the CCOS file and find the skills folder

    Download the CCOS ZIP and fully extract it. For this setup we’re going into the skills folder. Inside you’ll see subfolders for each plugin — and inside each subfolder are the individual skill ZIP files.

    • On Windows: right-click the ZIP and choose “Extract All” — don’t just double-click the ZIP
    • On Mac: double-clicking the ZIP creates an extracted folder next to it
    • You won’t need the plugin-zips or marketplace folders — those are for other setups
    • Keep the skills folder somewhere easy to find
  2. Stop here and make sure this is actually the right setup

    Before you keep going, make sure you really want the browser route. This page is for lightweight, single-conversation use. If you want CCOS to work across files, persistent context, and connected workflows, the browser will feel limited fast.

    • Best browser use case: one-off copy, brainstorming, light audits, and simple self-contained skills
    • Bad browser use case: file-heavy projects, multi-step builds, or anything that should persist cleanly between tasks
    • If that second list sounds like you, switch to Codex Desktop before you go further
  3. Check which ChatGPT plan you’re on

    How much of this guide applies depends on your plan. ChatGPT Business has native skills support. Most other plans do not, which means you are working with a temporary file-attachment workaround rather than a true installed skill experience.

    • If you’re on a Business plan: follow Steps 4–6 below for native skill install
    • If you’re on Plus, Pro, or Free: skip to Step 7 for the limited attach-and-go method
    • Not sure which plan you have? Go to chatgpt.com/settings — your plan is listed under Subscription
  4. Business plan: Open the Skills settings page

    If you’re on a ChatGPT Business plan, go to your account settings and find the Skills section. This is where you can upload individual CCOS skill ZIP files.

    These native install steps are for Business plan users only. If you’re on Plus, Pro, or Free, skip ahead to the attachment method later in the guide.
  5. Business plan: Upload a skill ZIP

    Click the option to add a new skill, then upload one of the skill ZIP files from your skills folder. Each skill is installed individually.

    • Start with the cc-help skill — it will guide you on what to add next
    • The cc-create-dna skill is the recommended second install — most skills rely on your Creator DNA context
    • Even on Business, browser ChatGPT is still better for lighter tasks than for true project-based CCOS work
  6. Business plan: Use a skill in any chat

    Once installed, you can use a skill by name in any ChatGPT conversation.

    Paste this into Claude
    Use the cc-help skill
  7. All plans: Attach a skill ZIP to any conversation

    If you don’t have native skills support, you can still sometimes get useful results by attaching a skill ZIP file directly to a ChatGPT conversation and asking it to use the skill. Treat this as a lightweight workaround, not a full installation path.

    • Open any ChatGPT conversation
    • Click the attachment icon (paperclip) and select a skill ZIP file from your skills folder
    • Send the message below along with the attached file
    • If the result feels incomplete or fragile, that is a sign to move to desktop rather than forcing the browser route
    Paste this into Claude
    Here is an AI skill zip file. I would like to use the skill in this file.
  8. Start with cc-help, then cc-create-dna

    If you stay in the browser, start with cc-help — it will orient you and recommend your next step. After that, run cc-create-dna to set up your Creator DNA context files. Just know that browser ChatGPT will not handle this context as cleanly or reliably as the desktop setups.

    If you’re using the attach method, you’ll need to attach the skill ZIP file each time you want to use a skill in a new conversation. The skill isn’t permanently installed — it’s loaded for that conversation only.
  9. What chatgpt.com is actually good for

    If you insist on staying in browser ChatGPT, keep your expectations narrow. It can still be genuinely useful when the task is small and self-contained.

    • Brainstorming, copywriting, and idea generation
    • Single-purpose skills that produce a self-contained output
    • Quick experiments before you decide to move the task into a real project workspace
    • Short sessions where you do not mind manually saving, copying, and moving files yourself
    Do not expect browser ChatGPT to be the best place for serious CCOS production work. For connected workflows where multiple plugins share context and files, the Codex desktop app or Claude Cowork are better options.

You’re all set up. Time to build something.

Your plugins are installed and your project folder is ready. Explore the full plugin library to see what’s possible, or head back to the start to pick a different setup path.