Troubleshooting

Check the selected agent, installation scope, target path, and source version when a skill is missing or stale.

The skill does not appear in my agent

Check that the command names the agent you are using. For a project install, run it from the intended repository and review the destination printed by the installer. Inspect that destination and confirm the installed folder still contains SKILL.md.

List installed Claude skills

Choose the matching scope. Replace claude-code with codex as needed.

Project Claude installed skills
npx skills@1.7.0 list --agent claude-code --json
Global Claude installed skills
npx skills@1.7.0 list --global --agent claude-code --json

If the selected agent no longer lists a skill but its folder remains, another universal agent may still use the canonical shared folder. Check the installer-reported destination and remaining agent uses before manual cleanup.

To check which skills are available in the source release, use its tagged folder URL. This lists source skills; it does not confirm an installed copy.

Browse skills in this release
npx skills@1.7.0 add https://github.com/OrphexTech/agent-skills/tree/v1.0.0/skills --list

The install command fails

Confirm Node.js and npm are available, then retry with the pinned installer version 1.7.0. If the source cannot be reached, check your connection and open the source repository to confirm that the selected release is available.

I need to update or remove it

To update, run the selected skill’s install command again and review the replacement prompt. For removal, use the selected-skill command on the installation guide.

The agent does not follow the skill

Confirm that the installed folder is in the location used by the selected agent and that its entry file is still named SKILL.md. Runtime behavior has not been verified for every target environment; check the agent’s current skill-loading guidance before relying on it.