Skip to content

Workspace Skills

Skills are reusable instructions — markdown playbooks authored once per workspace and synced to every developer's Claude Code as slash commands. Write "how we do database migrations" once on the Skills page; every agent in the team can run it as /acme:db-migration.

The model

  • A skill is a named markdown document scoped to a workspace. Names are URL-safe slugs (lowercase letters, numbers, hyphens; max 64 chars).
  • Each workspace has a prefix (e.g. acme) — synced skills appear in Claude Code as /<prefix>:<name>.
  • Every save bumps the skill's version; the sync client uses versions to pull only what changed.
  • Skills come from two origins: workspace skills your team writes, and platform skills Dezycro ships into every workspace (see Platform Skills).

Managing skills

Open Skills in the top bar (next to Notebooks). Every workspace member can read skills; editors can create, edit, and delete them.

  • Create — pick a slug name and write the markdown body. The body is exactly what Claude Code receives as the slash command's instructions, so write it like you'd brief a teammate: when to use it, the steps, the gotchas.
  • Edit — saves a new version; developers pick it up on their next sync.
  • Delete — removes the skill from the workspace. Developers lose it on their next sync. For workspace skills this is permanent; for platform skills it's an opt-out you can undo (see below).
  • Copy — each card has a copy button for the /<prefix>:<name> invocation.

The workspace prefix

The prefix namespaces your skills in Claude Code so skills from different workspaces never collide. It's derived automatically from the workspace name on first use and can be changed by workspace admins under Workspace Settings → Skills.

  • Must be a URL-safe slug, unique across all of Dezycro.
  • dezycro is reserved for the plugin's own commands.
  • Changing the prefix re-namespaces every synced skill on developers' next sync.

Syncing to Claude Code

Skills reach developers through the Dezycro CLI (installed with the Claude Code plugin):

dezycro skills sync                # pull skills for your configured workspaces
dezycro skills sync --configure    # (re)pick which workspaces to sync from
dezycro skills sync --force        # overwrite conflicting foreign files (takes ownership)

On first run the CLI asks which of your workspaces to sync — you pick from a list, never paste IDs. Skills are written to ~/.claude/commands/<prefix>/<name>.md, which Claude Code exposes as /<prefix>:<name>.

You rarely need to run this by hand: the plugin syncs automatically at session start and every 5 minutes while the Companion gateway is running.

Your files are safe

The CLI tracks every file it writes in a local ledger and never overwrites or deletes a file it doesn't own. If a synced skill would collide with a command file you created yourself, the CLI skips it with a warning; --force takes ownership explicitly.

Platform skills

Every workspace ships with two platform skills — kb-learn and kb-recall — that turn the workspace's default notebook (the Knowledge Base) into your team's long-term memory. See Platform Skills for what they do and how the platform-skill lifecycle (auto-updates, opt-out, reset) works.