# Codemie Sdk

> Manage CodeMie platform assets (assistants, workflows, datasources, integrations, skills, users, assistant-categories) directly from CLI using CodeMie SDK. Use when user says "create assistant from this config", "list workflows", "update datasource", "delete assistant", "show my assistants", "get workflow details", "manage integrations", "create integration", "list integrations", "list llm models", "list embedding models", "list skills", "get skill", "create skill", "update skill", "delete skill", "publish skill", "import skill", "export skill", "attach skill", "list assistant categories", "get assistant category", "create assistant category", "delete assistant category", "who am i", "current user", "my profile", "user info", or any request to manage CodeMie platform resources. NOTE: For analytics requests (usage analytics, summaries, spending, users activity, leaderboards, etc.) use the codemie-analytics skill instead. NOTE: To build an assistant for a purpose, test it against scenarios, or tune/improve an a

- Skill: `codemie-ai/codemie-sdk` (Agent Skill, multi-file: 8 files)
- Install (CLI): `npx get-skill add codemie-ai/codemie-sdk`
- Raw SKILL.md: https://api.skillmd.com/api/skills/codemie-ai/codemie-sdk/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Data & Analytics
- Author: codemie-ai (https://skillmd.com/u/codemie-ai)
- Updated: 2026-11-16
- Page: https://skillmd.com/skills/codemie-ai/codemie-sdk

---


# CodeMie SDK Asset Management

Manage CodeMie platform assets from the CLI.

> **Analytics requests** (usage data, summaries, spending, activity, etc.) are handled by the **codemie-analytics** skill — use that instead.

**Asset Types:** `assistants`, `workflows`, `datasources`, `integrations`, `skills`, `users`, `assistant-categories`

**Operations:** `list`, `get`, `create`, `update`, `delete`

---

## 🚨 Project Clarification (MANDATORY)

**Before proceeding with any work, you must determine which project to use by following these steps:**

### Step 1 — Fetch the User Profile

```bash
codemie sdk users me --json
```

This command returns `user_id`, `username`, `email`, `is_admin`, `applications`, and `applications_admin`.

### Step 2 — Identify Available Projects

- If `is_admin = true`: the user can access **all** projects on the platform, not just those listed in `applications`.
- If `is_admin = false`: the user can only work with projects listed in `applications`.
- The **default project** is the one matching the user's email (e.g., for `alice@acme.com`, the default project is `alice@acme.com`).

### Step 3 — Confirm the Project Selection

- If the user **explicitly** states a project name, or uses phrases like **"use my project"** or **"in my project"**, proceed with the identified project (use the default project for phrases like "my project" or "my default project").
- In **all other cases**, ALWAYS ask the user which project to use.

Aks the user what project to use with the options as follows:

1. **Default project** — `<user-email>` *(personal default project)*
2. **Choose a different project** — let the user to manually type the project name.

**Example prompt:**
> *Which project should I use?*  
> *1. alice@acme.com (your default project)*  
> *2. Choose a different project*

---

**Note:**  
Only select a project automatically if the user has explicitly named it, or used clear phrases indicating the default (e.g., "my project", "my default project"). In all other situations, always ask for project clarification.

### Step 4 — Proceed

Once the project is known, use it in all subsequent commands:
- Assistants, skills, assistant-categories: `"project": "<name>"`
- Workflows, datasources, integrations: `"project_name": "<name>"`

---

## 📖 Consult Examples Before Working on an Asset (MANDATORY)

**Before creating, updating, or querying any asset**, read the corresponding example file for complete field references, schemas, and commands to fetch referenced assets.

| Asset | Example file |
|-------|-------------|
| Assistants | [examples/assistants.md](${CLAUDE_PLUGIN_ROOT}/skills/codemie-sdk/examples/assistants.md) |
| Workflows | [examples/workflows.md](${CLAUDE_PLUGIN_ROOT}/skills/codemie-sdk/examples/workflows.md) |
| Datasources | [examples/datasources.md](${CLAUDE_PLUGIN_ROOT}/skills/codemie-sdk/examples/datasources.md) |
| Integrations | [examples/integrations.md](${CLAUDE_PLUGIN_ROOT}/skills/codemie-sdk/examples/integrations.md) |
| Skills | [examples/skills.md](${CLAUDE_PLUGIN_ROOT}/skills/codemie-sdk/examples/skills.md) |
| Users | [examples/users.md](${CLAUDE_PLUGIN_ROOT}/skills/codemie-sdk/examples/users.md) |
| Assistant Categories | [examples/categories.md](${CLAUDE_PLUGIN_ROOT}/skills/codemie-sdk/examples/categories.md) |

Do **not** guess field names or skip this step — all required/optional fields, nested schemas, and asset cross-reference commands are documented there.

---

## Input / Output

**Two ways to pass data:**
- Inline JSON: `--data '{"key":"value"}'`
- From file: `--json path/to/config.json`

**IDs are UUIDs**, e.g. `bc1a4b75-955c-48a5-b26d-bf702c1fee5d`

**Create does not return the new ID** in the output. After creating, use `list --search` to find the new asset's ID.

**Update replaces non-primitive values in full** — arrays and objects are not merged with existing values; the value you provide replaces the entire field. To preserve existing entries, either do not provide the value at all or fetch the current state first (`get <id> --json`), merge locally, then send the full updated value.

---

## Assistants

> See [examples/assistants.md](${CLAUDE_PLUGIN_ROOT}/skills/codemie-sdk/examples/assistants.md) for full field reference and examples.

```bash
codemie sdk assistants list [--scope visible_to_user|marketplace] [--search <text>] [--projects <name>] [--page <n>] [--per-page <n>] [--full-response] [--json]
codemie sdk assistants get <id> [--json]
codemie sdk assistants get-tools [--json]
codemie sdk assistants create --data '<json>' | --json <file>
codemie sdk assistants update <id> --data '<json>' | --json <file>
codemie sdk assistants delete <id>
codemie sdk assistants chat <id> "<message>" [--history <file>] [--assistant-version <n>] [--timeout <s>] [--json]
codemie sdk assistants test <id> --scenarios <file> --out <dir> [--assistant-version <n>] [--concurrency <n>] [--only <ids>] [--timeout <s>]
codemie sdk assistants versions <id> [--current] [--json]
codemie sdk assistants rollback <id> <version>
codemie sdk assistants report <workspace-dir> [--name <name>] [--json]
codemie sdk assistants conversations [<id>] [--limit <n>] [--ids <ids-or-links>] [--json]
```

`chat` is stateless and works with any assistant ID (no `codemie assistants setup` needed); history is not saved on the platform.

**Required on create:** `name`, `project`, `system_prompt`

---

## Workflows

> See [examples/workflows.md](${CLAUDE_PLUGIN_ROOT}/skills/codemie-sdk/examples/workflows.md) for full field reference and examples.

```bash
codemie sdk workflows list [--search <text>] [--projects <name>] [--page <n>] [--per-page <n>] [--json]
codemie sdk workflows get <id> [--json]
codemie sdk workflows create --data '<json>' --config '<yaml>' | --config path/to/config.yaml
codemie sdk workflows update <id> --data '<json>' [--config '<yaml>' | --config path/to/config.yaml]
codemie sdk workflows delete <id>
```

**Required on create:** `name`, `project`, `mode` (`"Sequential"`), `shared` (boolean), plus `--config` with YAML graph definition

---

## Datasources

> See [examples/datasources.md](${CLAUDE_PLUGIN_ROOT}/skills/codemie-sdk/examples/datasources.md) for full field reference and examples.

Type subcommands for create/update: `confluence`, `jira`, `file`, `code`, `google`, `provider`, `azure-devops-wiki`, `azure-devops-work-item`, `xray`, `sharepoint`

```bash
codemie sdk datasources list [--search <text>] [--projects <name>] [--status <status>] [--datasource-types <types>] [--sort-key date|update_date] [--sort-order asc|desc] [--page <n>] [--per-page <n>] [--json]
codemie sdk datasources get <id> [--json]
codemie sdk datasources create <type> --data '<json>' | --json <file>
codemie sdk datasources update <type> <id> --data '<json>' | --json <file>
codemie sdk datasources delete <id>
# file type only: --file ./doc.pdf (repeatable, max 10)
```

**Required on create (all types):** `name` (no spaces, use hyphens), `project_name`, plus type-specific required fields

---

## Integrations

> See [examples/integrations.md](${CLAUDE_PLUGIN_ROOT}/skills/codemie-sdk/examples/integrations.md) for full field reference and examples.

```bash
codemie sdk integrations list [--setting-type user|project] [--search <text>] [--projects <name>] [--page <n>] [--per-page <n>] [--json]
codemie sdk integrations get <id> [--setting-type user|project] [--json]
codemie sdk integrations get-by-alias <alias> [--setting-type user|project] [--json]
codemie sdk integrations create --data '<json>' | --json <file>
codemie sdk integrations update <id> --data '<json>' | --json <file>
codemie sdk integrations delete <id> [--setting-type user|project]
```

**Required on create:** `credential_type`, `project_name`, `credential_values` (must include `{"key":"alias","value":"<alias>"}`)

---

## LLM Models

```bash
codemie sdk llm list [--json]
codemie sdk llm list --embeddings [--json]
```

Use `base_name` when setting `llm_model_type` on an assistant or `embeddings_model`/`summarization_model` on a datasource.

---

## Skills

> See [examples/skills.md](${CLAUDE_PLUGIN_ROOT}/skills/codemie-sdk/examples/skills.md) for full field reference and examples.

```bash
codemie sdk skills list [--scope marketplace|project|project_with_marketplace] [--page <n>] [--per-page <n>] [--json]
codemie sdk skills get <id> [--json]
codemie sdk skills create --data '<json>' | --json <file>
codemie sdk skills update <id> --data '<json>' | --json <file>
codemie sdk skills delete <id>
codemie sdk skills import <file.md> --project <name> [--visibility private|project|public] [--json]
codemie sdk skills export <id>
codemie sdk skills attach <assistant-id> <skill-id>
codemie sdk skills detach <assistant-id> <skill-id>
codemie sdk skills list-assistant-skills <assistant-id> [--json]
codemie sdk skills bulk-attach <skill-id> --assistant-ids <id1>,<id2>,...
codemie sdk skills get-assistants <skill-id> [--json]
codemie sdk skills publish <id> [--categories <cat1>,<cat2>]
codemie sdk skills unpublish <id>
codemie sdk skills list-categories [--json]
codemie sdk skills get-users [--json]
codemie sdk skills react <id> --reaction like|dislike
codemie sdk skills remove-reactions <id>
```

**Required on create:** `name` (kebab-case, 3–64 chars), `description` (10–1000 chars), `content` (markdown, min 100 chars), `project`

---

## Users

> See [examples/users.md](${CLAUDE_PLUGIN_ROOT}/skills/codemie-sdk/examples/users.md) for full field reference and examples.

```bash
codemie sdk users me [--json]
codemie sdk users data [--json]
```

---

## Assistant Categories

> See [examples/categories.md](${CLAUDE_PLUGIN_ROOT}/skills/codemie-sdk/examples/categories.md) for full field reference and examples.

**Note:** Categories can only be used for assistants (set via the `categories` field on create/update).

```bash
codemie sdk assistant-categories list [--paginated] [--page <n>] [--per-page <n>] [--json]
codemie sdk assistant-categories get <id> [--json]
codemie sdk assistant-categories create --data '<json>' | --json <file>
codemie sdk assistant-categories update <id> --data '<json>' | --json <file>
codemie sdk assistant-categories delete <id>
```

**Required on create:** `name` (1–255 chars)


