Skills

Skills let you package repeatable instructions in SKILL.md files and trigger them as commands (for example /my-skill or $my-skill, depending on provider).

How Skills Work in CloudCLI

CloudCLI does not create skill files for you. Instead, it reads provider-native skill directories and automatically exposes discovered skills in the chat composer command menu.

When a SKILL.md file is added or updated in a supported location:

1. CloudCLI discovers the skill for the selected provider
2. The command appears in the command menu
3. Selecting the command inserts it into your prompt input

Using a Skill

1. Open a chat session for your selected provider
2. Focus the message input
3. Type the provider command prefix (/ or $)
4. Pick a skill from the Skills section in the command menu
5. Send your prompt

Creating a Skill

1. Choose the provider and scope (project or user)
2. Create a folder for the skill in one of that provider's supported skill paths
3. Add a SKILL.md file with frontmatter
4. Return to CloudCLI and open the command menu in chat

Minimal SKILL.md Example

---
name: summarize-pr
description: Summarize this pull request with risks and next steps.
---

Use this skill to generate a concise PR summary:
- Key changes
- Risks and regressions
- Suggested follow-up tasks

Provider Command Prefixes

Skill Locations by Provider

CloudCLI discovers skills from these provider-native paths.

Claude

• User: ~/.claude/skills
• Project: <workspace>/.claude/skills
• Plugin commands: discovered as /<plugin-name>:<skill-name>
• Plugin skill markdowns: discovered recursively from plugin skills/ folders

Codex

• Repo: <workspace>/.agents/skills
• Repo parent: path.dirname(workspacePath)/.agents/skills
• Topmost git root: <git-root>/.agents/skills
• User: ~/.agents/skills
• Admin: /etc/codex/skills
• System: ~/.codex/skills/.system

Cursor

• Project: <workspace>/.agents/skills
• Project: <workspace>/.cursor/skills
• User: ~/.cursor/skills

Gemini

• User: ~/.gemini/skills
• User: ~/.agents/skills
• Project: <workspace>/.gemini/skills
• Project: <workspace>/.agents/skills

Notes

• Skills are discovered from SKILL.md files.
• CloudCLI reads name and description from frontmatter.
• If name is missing, the containing folder name is used.
• Malformed skill files are skipped so valid skills still load.

Troubleshooting

Skill does not appear in command menu

1. Confirm the file is named exactly SKILL.md
2. Confirm frontmatter includes at least name and description
3. Confirm the file is in a provider-supported skill path
4. Confirm you are in a chat session for the same provider
5. Re-open the command menu after saving the file

Command prefix is wrong

• Use / for Claude, Cursor, and Gemini
• Use $ for Codex

Command appears but inserts unexpected name

• Check the name value in SKILL.md frontmatter
• If name is omitted, CloudCLI uses the skill folder name