Skip to content
Agentic Levels

Everything starts here.

GuestLocal progress only
PreferencesSign in
01Start with one taskBest first move for beginners.02Check your LevelMeasure where you are.03Score an AI resultFind the habit to practice first.04Return to Your WorkScores, links, and checkpoints.
Start here

Begin

HomeThe main entry point.New to AIStart with one useful task.
Know where you are

Measure

Check your LevelUse this after you have tried AI.Fluency ScoreScore an AI result you can review.
Build the habit

Learn

LevelsLessonsTracks
Find the reference

Library

PromptsReferenceResourcesCompare Tools
Turn it into work

Apply

Your Next MoveChoose what AI should change next.Tool SetupGet the tools ready.
Come back later

Return

Your WorkScores, links, and checkpoints.My PathContinue from your level.Updates
Site

Site

PricingAboutFAQ & FeedbackPreferences

© 2026 Fuentes Studio

Privacy·Terms
yourCouncil
Ready to help
✦

What do you want to understand?

Ask anything about what you're learning.

Tracks›Codex Fundamentals
L6Lesson 2Free

Add skills and plugins without bloat

Reuse instructions only when they earn the setup

After this, you'll be able to decide when to keep a workflow in a prompt, when to create a skill, and when plugin packaging is worth it.

Before you start

Complete Use MCP only for a real gap first.

The idea

Skills and plugins are for repeated work, not for every preference. A skill packages task-specific instructions, references, and optional scripts. A plugin can distribute skills and bundle app mappings, MCP configuration, hooks, or other setup.

Optional extension cards sit outside a repeated-use proof gate with no reason selected yet.
Optional extension cards sit outside a repeated-use proof gate with no reason selected yet.
Plugin ChoiceMove through Add skills and plugins without bloat, check proof, then fix only the weak part.
yesnorun it again
StartBegin with the real task
Add skills and plugins withoutAfter this, you'll be able to decide when to keep a workflow in a prompt, when to
1Proof visible?One-time instructions stay in prompts
Ready to useClassify one repeated workflow as prompt, AGENTS.md, skill, plugin, or discard
Fix the weak partBreaks when too many skills compete and Codex loads the wrong process

Here is the before and after: before, Codex is guessing from a loose request. After, you can decide when to keep a workflow in a prompt, when to create a skill, and when plugin packaging is worth it.

Now try it use the exercise prompt on one real repo task. Keep the output small enough to check before you accept the change.

You are ready when the Codex action, boundary, and proof all match the task.

Try it (12 min)

Watch out for

  • Creating a skill for a rule that belongs in AGENTS.md.
  • Creating a plugin before a local workflow is stable.
  • Installing broad plugins without reviewing bundled hooks or MCP config.
  • Keeping old skills that no one uses.

Paste this into Claude

Classify this repeated Codex workflow:

Workflow: [describe repeated task]
Frequency: [daily, weekly, rare]
Steps that must happen every time: [list]
References or scripts needed: [list]
Needs MCP, app connection, hooks, or shared install: [yes/no]
Audience: [me only, repo team, many teams]

Choose prompt, AGENTS.md, skill, plugin, or do not keep. Give the reason and the proof that would show it worked.

Created by potrace 1.16, written by Peter Selinger 2001-2019 What a good response looks like

Use a skill. The workflow runs every content pass, requires the authoring spec and gate commands, and has a stable proof list. Do not make a plugin until another repo needs the same workflow plus installable scripts.

Created by potrace 1.16, written by Peter Selinger 2001-2019 What good looks like

  • One-time instructions stay in prompts
  • Repo-wide rules go to AGENTS.md
  • Repeat workflows with steps become skill candidates
  • Plugins are reserved for shared bundled setup

When this breaks

  • Breaks when too many skills compete and Codex loads the wrong process.
  • Breaks when a plugin bundles permissions the user did not expect.

AI can help with this

Use Codex to help you you can decide when to keep a workflow in a prompt, when to create a skill, and when plugin packaging is worth it. Start with the exercise prompt and your real input. Ask for one draft, then check it against this proof: One-time instructions stay in prompts. Accept only the version you can verify yourself.

Reusable instruction card, trigger card, proof case card, and reject pile card surround one extension boundary with the golden dot on the kept card.

Created by potrace 1.16, written by Peter Selinger 2001-2019 You can now

✓

You can explain what a skill packages

  • ✓You can explain what plugins distribute
  • ✓You can avoid setup bloat
  • ✓You can name proof for a reusable workflow

Key takeaways

Reusable Codex setup should remove repeated decisions and add proof. If it only adds surface area, skip it.

  1. 1Prompts are for one-off instructions.
  2. 2AGENTS.md is for repo-wide rules.
  3. 3Skills package repeated workflows.
  4. 4Plugins distribute bundled setup when sharing matters.

Created by potrace 1.16, written by Peter Selinger 2001-2019 Go deeper

  • Codex skills
  • Codex plugins

Was this helpful?

Up nextSplit work with subagents→

Related lessons

Package Your First SkillMCP is how your agent reaches your real tools
← Back to Codex Fundamentals