Manage and update your resources

An installed skill is just a folder of files. Managing it means checking what sits in the right folders, replacing a folder with a newer version, or removing it. This article walks through each step, with the specifics of Claude Code and Codex.

List what is installed

Each skill is a folder containing a SKILL.md file. To see what your agent can use, look at its skills folders: a global one for all your sessions, and a project one for a given repository. Each agent's page lists its own, for example Claude Code or Codex.

In Claude Code, the /skills command opens a menu of the skills loaded in the session. The /skill-doctor command also shows what each skill costs in context and whether it has ever been used, which helps you spot the ones you can drop. In Codex (CLI and editor extension), the /skills command or the $ character lets you list and mention a skill.

Update a skill

There is no hidden step: an update means replacing the folder with the newer version.

1. Open the skill's page on PalateKit and check its update date and version. If they are later than your install, a newer version exists.
2. If you edited the skill's files, copy your changes somewhere else first. Overwriting would erase them.
3. Run the page's install method again (prompt, command or ZIP), for the same agent and the same folder:

Read https://palatekit.com/en/skills/landing-page-audit/install.md and follow the instructions to install it.

npx --yes palatekit@latest install landing-page-audit

4. Reapply your edits if needed, then open a new session to check that the agent uses it.

Claude Code watches its skills folders: a skill added, edited or removed under ~/.claude/skills/ or .claude/skills/ is picked up without a restart. If the skills folder did not exist when the session started, run /reload-skills. Codex also detects changes; if an update does not show up, restart it.

Disable without deleting

Disabling is useful to test without the skill or to lighten the context, without losing the files.

For Codex, the entry looks like this:

[[skills.config]]
path = "/path/to/the-skill/SKILL.md"
enabled = false

Remove a skill

In both Claude Code and Codex, a local skill is removed by deleting its folder, for example ~/.claude/skills/skill-name/ or .claude/skills/skill-name/. Claude Code drops it from /skills in the current session. Content already loaded into the conversation may stay until the session ends.

A skill that comes from a plugin cannot be removed this way: disable or uninstall the plugin from the /plugin menu.

Keep different versions per project

The project folder (.claude/skills/, or .agents/skills/ for Codex and other agents) lets you commit a specific version of the skill with the repository. Anyone who clones the project gets the same version, and you decide when to update it, project by project. This is the right choice for a skill your team must use the same way.

The global folder follows your machine instead: one version for all your projects.

Avoid duplicates

Installing the same skill in both the user folder and the project creates two copies, which may differ. What happens depends on the agent:

• Claude Code: with the same name, the personal skill takes precedence over the project one. The project version is therefore hidden without warning if the global one is older.
• Codex: two skills with the same name are not merged, and both can appear in the selectors.

Pick a single location for each skill. Keep the global version for your personal tools, and the project version for what must be shared and pinned. If you use several agents, note that some read the common ~/.agents/skills/ folder and others their own: check on each agent's page that a skill has not been copied to two places the same agent reads.