The Kodexa Metadata Skills plugin is a Claude Code plugin published at kodexa-ai/kodexa-metadata-skills. It adds Kodexa-specific authoring guidance to Claude Code so it can work with platform metadata files instead of guessing schema shape from scratch.
Prerequisites
Before installing the plugin:
- Install Claude Code.
- Install the KDX CLI.
- Configure KDX authentication for at least one Kodexa environment.
- Have a Git repository for Kodexa metadata, or plan to create one with
kdx sync pull --discover.
Install From The Marketplace
Run these commands in your terminal:
After installation, the skills are available in Claude Code sessions automatically.
Use A Local Checkout
For development or testing, load the plugin from a local clone:
Use a local checkout when you are testing a new version of the skills or contributing improvements to the plugin itself.
Let Claude Code Pick The Skill
Most of the time you can describe the work naturally:
Claude Code should select the relevant Kodexa skill based on the task. For that example, it should use Activity Plan guidance, and may also draw on task template, data form, service bridge, and KDX CLI guidance depending on the files involved.
Invoke A Skill Directly
When you know the resource type, invoke the skill explicitly:
Direct invocation is useful when you want Claude Code to stay focused on one class of metadata.
Recommended Activity-First Usage
For new business workflows, start from this order:
data-definition: model the structured data the workflow produces.task-template: define the human work item.data-form: build the review UI for the task.activity-plan: define the automated process, including when it creates or waits for tasks.knowledge-system: add context-dependent prompts, rules, examples, or configuration.project-template or project bindings: bind reusable resources into the project.kdx-cli: validate and sync the configuration.
If you are maintaining older configuration, the skills repository may contain guidance for legacy resource shapes. For new orchestration work, use Activity Plans and triggers instead of putting process steps inside a Task template.
Verify The Plugin Is Available
Open Claude Code in your metadata repository and ask:
Then ask it to inspect the repository layout:
Claude Code should respond with Kodexa-specific terminology and should not suggest deploying until it has inspected the local files. 