Skip to main content

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 login or CODIKA_API_KEY environment variable
  • A deployed process instance (with devProcessInstanceId in project.json, or known ID)

Command

Arguments

Options

Process instance ID resolution

Priority order:
  1. Positional argument (highest)
  2. --process-instance-id flag
  3. devProcessInstanceId from project.json in --path directory
  4. devProcessInstanceId from project.json in current directory

How it works

  1. Resolves process instance ID from flag, argument, or project.json
  2. Calls getProcessSkillsPublic cloud function with API key auth
  3. Reads skills from the process’s active deployment instance
  4. Writes each skill as a Claude-compatible directory: {name}/SKILL.md

Examples

From inside a use case folder

Resolves devProcessInstanceId from project.json.

With explicit process instance ID

Download directly to Claude Code skills directory

Skills are immediately auto-discoverable by Claude Code.

JSON output for scripting

Output

Human-readable (default)

JSON output

Using downloaded skills

With Claude Code

Claude Code auto-discovers skills in .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

Exit codes