When to use
- You need to discover what workflow endpoints are available for a process instance
- You want to download skills to use with Claude Code or the Claude API
- You need to inspect the available workflows and their input/output schemas
- An agent needs to understand how to interact with a deployed use case
Prerequisites
- Authenticated with
codika loginorCODIKA_API_KEYenvironment variable - A deployed process instance (with
devProcessInstanceIdin project.json, or known ID)
Command
Arguments
| Argument | Required | Description |
|---|---|---|
[processInstanceId] | No | Process instance ID. If omitted, resolves from project.json. |
Options
| Option | Default | Description |
|---|---|---|
--process-instance-id <id> | — | Alternative to positional argument |
--path <path> | Current directory | Path to use case folder (to resolve from project.json) |
--project-file <path> | project.json | Custom project file name |
-o, --output <dir> | ./skills | Output directory for skill files |
--stdout | false | Print to stdout instead of writing files |
--api-url <url> | Production | Override API URL |
--api-key <key> | Active profile | Override API key |
--profile <name> | — | Use a specific profile instead of the active one |
--json | false | Structured JSON output |
Process instance ID resolution
Priority order:- Positional argument (highest)
--process-instance-idflagdevProcessInstanceIdfrom project.json in--pathdirectorydevProcessInstanceIdfrom project.json in current directory
How it works
- Resolves process instance ID from flag, argument, or project.json
- Calls
getProcessSkillsPubliccloud function with API key auth - Reads skills from the process’s active deployment instance
- Writes each skill as a Claude-compatible directory:
{name}/SKILL.md
Examples
From inside a use case folder
devProcessInstanceId from project.json.
With explicit process instance ID
Download directly to Claude Code skills directory
JSON output for scripting
Print all skills to stdout
Output
Human-readable (default)
JSON output
Using downloaded skills
With Claude Code
.claude/skills/ and can use them in conversations.
With the Claude API
Triggering a workflow from a skill
After reading a skill, trigger the workflow it describes:Error reference
| Error | Cause | Fix |
|---|---|---|
Process instance ID is required | No ID found | Provide ID or ensure project.json has devProcessInstanceId |
API key is required | No API key found | Run codika login or set CODIKA_API_KEY |
No skills found | Process has no skills deployed | Add skills/ folder to use case and redeploy |
401 Unauthorized | Invalid API key | Run codika login to refresh credentials |
Exit codes
| Code | Meaning |
|---|---|
0 | Success |
1 | Error (API failure, auth failure) |