Plugin skills

The codika-os-plugin is an Open Plugin v1-conformant plugin. Once installed, every codika-os-* skill is available in any compatible agent session (Claude Code, Cursor, …). The agent can set you up, sync, check status, switch profiles, all by name.

Install

In Claude Code:

/plugin marketplace add codika-io/codika-os-plugin
/plugin install codika-os@codika-os-plugin

For any other Open-Plugin-compatible host:

npx plugins add codika-io/codika-os-plugin

Both paths surface the same /codika-os:* skills.

What the skills do

Every skill shells out to the codika-os CLI with --json and parses the structured output. The CLI is the canonical interface; the skills make it ergonomic for the agent to use. You can always drop down to the CLI if a skill misbehaves — the skill output shows you which CLI command it ran.

Prerequisites

Just one: install Claude Code (or any Open-Plugin host) on the machine. The very first skill you’ll run, setup-codika-os, installs the codika-os CLI itself (npm install -g codika-os), so you do not need to install the CLI by hand first.

The skills

Lifecycle

Skill	Wraps	When to invoke
`setup-codika-os`	`npm i -g codika-os` + `auth signup\|login` + `install`	First-time bootstrap on a new machine. Also the recovery path for a missing CLI or a bad/expired key.
`install-codika-os-hooks`	`codika-os install`	Repair Claude Code hooks after an upgrade or stale config. Idempotent.
`logout-codika-os`	`codika-os logout [name]`	Remove a profile locally. The backend key stays valid until you revoke it from the dashboard.

Operate

Skill	Wraps	When to invoke
`sync-codika-os`	`codika-os sync`	Force-flush pending events to the dashboard now. Path classifier only — anything it can’t decide is left for `classify-sessions`.
`classify-sessions`	`codika-os classifications pending` + `submit`	Attribute pending sessions to a project (and optional subcategory) in-context, month by month. Walks the backlog, builds an evidence prompt per session, picks from the project catalog grouped by category, and surfaces new-project suggestions at the end for the team to triage. Invoke when sync reports `unattributed > 0`.
`codika-os-status`	`codika-os status`	Health check: hook count, last sync, pending events.
`codika-os-whoami`	`codika-os whoami`	Show active profile, org, masked `cos_` prefix.
`codika-os-verify`	`codika-os verify`	Round-trip the active key against `/api/auth/cli/verify`.

Config

Skill	Wraps	When to invoke
`codika-os-config`	`codika-os config show\|set\|clear`	Inspect or mutate the on-disk config (API key, base URL).
`switch-codika-os-profile`	`codika-os use [name]`	List profiles or switch the active one (e.g. dev-local ↔ prod).

A typical first day

> /codika-os:setup-codika-os
  → installs codika-os globally
  → email: you@codika.io
  → 6-digit code: 123456
  → mints cos_xxxx... and stores it
  → installs 5 hooks
  ✓ Setup complete

[ ... use Claude Code normally, hooks capture everything ... ]

> /codika-os:codika-os-status
  ✓ codika-os healthy, 12 pending events, last sync 1d ago

> /codika-os:sync-codika-os
  → ran: codika-os sync --json
  ✓ 47 sessions upserted, $1.23 this run

> /codika-os:codika-os-whoami
  Profile: codika  | Org: Codika  | Key: cos_xxxx...9a2f

A second profile (dev-local)

> /codika-os:codika-os-config
  → set apiBaseUrl=http://localhost:5190 on a new profile "dev-local"

> /codika-os:setup-codika-os
  → run with --profile dev-local
  → OTP login against the local app
  ✓ Setup complete on profile dev-local

> /codika-os:switch-codika-os-profile dev-local
  ✓ Active profile is now dev-local

Source

Skill definitions: codika-os-plugin/skills/. Each skill’s SKILL.md is self-contained and describes the exact CLI invocations it issues, the prompts it asks the user, and the error-handling branches it follows.