Skip to main content
Skills are Markdown instruction files that agents read at the start of each session. You can use them to define coding conventions, project context, agent personas, or any persistent instructions you want an agent to follow. Navigate to Settings → Skills to manage skills.

​
How skills work

Codeg stores skills as files on disk in directories that each agent monitors. When an agent starts a session, it reads the skill files from its configured skill directories and incorporates them as system-level context. Skills are agent-specific — each agent has its own skill directory structure and layout requirements. Codeg shows only agents that support skills in the Settings → Skills view.

​
Skill scopes

Global skills apply to all projects. They are stored in the agent’s home-directory skill folder. Codeg’s Settings UI manages global skills only.
AgentGlobal skill directory
Claude Code~/.claude/skills/
Codex CLI~/.agents/skills/ or ~/.codex/skills/
OpenCode~/.config/opencode/skills/
Gemini CLI~/.gemini/skills/ or ~/.agents/skills/
OpenClaw~/.openclaw/skills/
Cline~/.agents/skills/ or ~/.cline/skills/

​
Skill layouts

Codeg supports two file layouts, depending on what each agent expects:
A skill directory is a folder named after the skill that contains a SKILL.md file:
~/.claude/skills/
└── my-conventions/
    └── SKILL.md
All agents support this layout. Codeg creates skill directories by default for Claude Code, OpenCode, Codex, Gemini CLI, OpenClaw, and Cline.
Codeg shows a message in the Skills panel when a selected agent does not support skills management via the UI.

​
Creating a skill

1

Select an agent

In Settings → Skills, choose the agent from the dropdown on the left. Only agents that support skills appear in this list.
2

Click New Skill

Click the New Skill button at the bottom of the skills list.
3

Enter a skill ID

Type a name for your skill. The ID can contain letters, numbers, hyphens, underscores, and dots. It cannot start with a dot or contain path separators. Codeg shows you the resolved file path as you type.
4

Write your instructions

Use the built-in Markdown editor to write your skill content. Toggle between Edit and Preview modes using the button in the top-right corner of the editor. The preview renders GFM (GitHub Flavored Markdown), including tables, code blocks, and task lists.
5

Save

Click Save. Codeg writes the skill file to the agent’s global skill directory.

​
Editing an existing skill

Click any skill in the list to open it in preview mode. Click Edit to switch to the Markdown editor, make your changes, and click Save. Use Reset to discard unsaved changes and revert to the last saved version.

​
Deleting a skill

Right-click a skill in the list and select Delete, or open the skill and use the context menu. A confirmation dialog appears before the file is removed from disk.

​
Use cases

Coding conventions

Define language-specific style rules, naming conventions, or linting preferences the agent should follow across all sessions.

Project context

Describe your project’s architecture, key modules, or common patterns so the agent has useful background without you restating it every session.

Agent persona

Give the agent a specific communication style, level of verbosity, or decision-making approach.

Workflow instructions

Define multi-step processes (e.g., “always write tests before implementation”) that the agent should apply consistently.

​
Skill content format

Skills are plain Markdown. Codeg also supports YAML frontmatter at the top of a skill file: 
---
name: My Coding Standards
version: 1.0
---

## TypeScript conventions

- Use `const` by default; `let` only when reassignment is necessary.
- Prefer explicit return types on all exported functions.
- Use `unknown` instead of `any`.
Frontmatter fields are displayed in a structured metadata panel in the preview mode. The body content is rendered as standard Markdown.