setup-prezento

Prezento Setup

Get a prezento organization API key, store it in the workspace .env, and verify it works. After this, all other prezento skills authenticate automatically.

Prerequisites

• A prezento-app account (sign up at https://prezento-app.web.app if you don't have one)
• Workspace .env file at ~/.codika/.env (it already exists if you've used Codika before)

Step 1: Get an organization API key

The dashboard creates the key for you and shows the raw value once:

1. Go to https://prezento-app.web.app, sign in if needed
2. Click your organization → API Keys in the sidebar (URL pattern: /organizations/<orgId>/org/api-keys)
3. Click Create API key
4. Name it (e.g. claude-skill), select scope presentations:write (and optionally presentations:read)
5. Copy the raw cko_… value when the modal shows it. This is the only time you'll see it.

If the user wants to do this from the CLI instead of the dashboard, that's a v2 feature — for v1, the dashboard is the only path.

Step 2: Store the key in the workspace .env

echo 'PREZENTO_API_KEY=cko_paste_the_value_here' >> ~/.codika/.env

If ~/.codika/.env doesn't exist, create it. The other prezento skills read this env var.

Step 3: Verify the key works

source ~/.codika/.env
curl -sS -X POST \
  -H "X-Process-Manager-Key: $PREZENTO_API_KEY" \
  https://europe-west1-prezento-app.cloudfunctions.net/verifyApiKey

Expected response (success):

{
  "valid": true,
  "type": "organization",
  "keyPrefix": "cko_xxxxxxxx",
  "keyName": "claude-skill",
  "scopes": ["presentations:write"],
  "organizationName": "<Your workspace name>",
  "expiresAt": null
}

If you get 401 Unauthorized or valid: false, the key was mis-pasted or revoked. Repeat Step 1.

Output checklist

• User has a cko_… key from the prezento-app dashboard
• Key is stored as PREZENTO_API_KEY in ~/.codika/.env
• verifyApiKey returns valid: true with the expected scopes
• Tell the user: "Setup complete. You can now use share-presentation, update-presentation, list-presentations, and get-presentation."

Pitfalls

• Wrong scope → Other skills will return 403 even though the key is valid. Make sure presentations:write is selected.
• Key not loaded by shell → Don't forget source ~/.codika/.env in the same shell session, or restart the terminal.
• Multiple Codika products → If the user already has CODIKA_ADMIN_API_KEY for codika-app, that's a different key. Prezento uses its own PREZENTO_API_KEY.
• Wrong header name → Header must be X-Process-Manager-Key, NOT Authorization: Bearer. This is the prezento-app convention (inherited from codika-app-platform).