Skills & Plugins

Skills are on-demand instruction sets that extend Gee-Code’s capabilities. When you invoke a skill, its full instructions are loaded into the conversation — giving the AI specialized knowledge and workflows for specific tasks.

Using Skills

Invoke a skill with a slash command:

/commit              # Load git commit instructions
/explore src/        # Load codebase exploration skill
/frontend-design     # Load frontend design skill

List and manage skills:

/skills              # Show all skills with status
/skills on commit    # Enable a skill
/skills off commit   # Disable a skill

Skill Anatomy

A skill is a directory with a SKILL.md file:

.gee/skills/my-skill/
├── SKILL.md          # Instructions with YAML frontmatter (required)
├── scripts/          # Python helper scripts (optional)
├── references/       # Reference documentation (optional)
└── assets/           # Binary assets (optional)

SKILL.md Format

---
name: my-skill
description: Does something useful
activation: /my-skill
args: "[target]"
user_invocable: true
---

# Instructions

When this skill is invoked, you should...

## Steps

1. First, do this
2. Then, do that

The instructions are written in natural language. The AI reads them and follows them when the skill is activated.

Skill Sources

Skills come from three places:

Source	Location	Managed By
Local (project)	.gee/skills/	You, via files
Local (global)	~/.gee-code/skills/	You, via files
Marketplace	Gee server	/marketplace

Creating Skills

Two workflows:

Local-First (recommended)

1. Scaffold: InitSkill(name="my-skill")
2. Edit .gee/skills/my-skill/SKILL.md
3. Sync: SyncSkill(skill_name="my-skill")

Direct Creation

Use the CreateSkill tool to send content directly to the server — no local files needed.

For the full creation guide, see Creating Skills.

Plugins

Plugins bundle multiple components together — skills, agents, commands, and MCP servers:

.gee/plugins/my-plugin/
├── plugin.json           # Metadata
├── skills/
│   └── skill-name/
│       └── SKILL.md
├── agents/
│   └── agent-name.md
├── commands/
│   └── command-name.md
└── .mcp.json             # MCP server configs

Sync a plugin with all its components:

SyncPlugin(plugin_name="my-plugin")

Skills vs Plugins

	Skill	Plugin
Scope	Single capability	Bundle of capabilities
Components	SKILL.md + scripts + refs	Skills + agents + commands + MCP
Location	.gee/skills/	.gee/plugins/
Use case	One focused task	Cohesive toolkit

Start with a skill. Promote to a plugin when you need agents, commands, or MCP servers.

Marketplace

Browse and install community skills:

/marketplace              # Browse available skills
/marketplace install x    # Install a skill

Next Steps

• Creating Skills — full step-by-step guide
• Building Plugins — multi-component plugin development
• Creating MCP Servers — add external tool capabilities