| name | kortix-marketplace |
| description | The Kortix marketplace โ how to discover capabilities and IMPORT them into this project. The marketplace is a catalog of open git repos: whole ready-made PROJECTS (registry:project) and individual skills/agents/tools. There is no deterministic 'installer' โ you (the agent) import an item by reading its source and merging the files that fit into this project, then opening a change request. Use when the user wants to browse/search the Kortix catalog, 'add/clone the <X> project', 'import that skill/agent', pull in a marketplace capability, or add a new source. For the open npx-skills ecosystem, see find-skills-sh. |
The Kortix marketplace is the Kortix-native catalog. Every item is an open
git repo made of plain files โ a whole clonable project (its kortix.yaml,
agents, skills, tools) or an individual skill / agent / tool. There is no
deterministic installer, no version lock, and no update system: you add an item
by importing it โ reading its source and merging what fits into this
project's own files, then opening a change request. Everything you import becomes
100% user-owned files in this repo, exactly like any other code you write.
Why it works this way: the Kortix system layer (this kortix-* family, the
kortix CLI) is served live and always-latest, so it never goes stale. Marketplace
items are the opposite โ they're yours to own and edit, so they're imported as
files, not pinned to an upstream that could clobber your changes.
Browse/search the catalog from the `kortix` CLI (already authenticated here):
kortix marketplace search "<query>" --json
kortix marketplace show <id> --json
Read-only. There is no install / update / remove subcommand anymore โ
adding an item is the import flow below.
**The standard import recipe.** To add a marketplace item to this project:
- Get the source. From
kortix marketplace show <id> --json, take the item's
source git repo/ref (or its inline files). Clone/read it in the sandbox.
- Detect what it is from its file structure:
- a
kortix.yaml at the repo root โ a project (agents + skills + tools +
config),
- a
SKILL.md โ a skill,
- an agent definition (an
agents/*.md) โ an agent,
- a tool file (a
tools/*.ts) โ a tool.
- Merge what fits into this project, in the right place:
- skills โ
.kortix/opencode/skills/<name>/,
- agents โ
.kortix/opencode/agents/, tools โ .kortix/opencode/tools/,
- for a whole project: pull in its skills/agents/tools and reconcile its
kortix.yaml into this project's (merge connectors/triggers/agents โ never
blindly overwrite the user's manifest). Use judgment; keep what's relevant.
- Adapt it to this project. If a skill carries a "TODO: make this yours"
placeholder or generic copy, tailor it to what this project actually does.
- Wire up its needs. If the item requires a connector/secret, don't hardcode
anything โ mint a setup link (
kortix secrets request โฆ / the executor
connect flow) and surface it to the user.
- Commit + open a CR.
git add/commit, git push origin HEAD, then
kortix cr open --title "Import <item>". The user reviews the diff and merges
โ that's how it becomes permanent (see kortix-system for the CR mandate).
Importing is just you reading files and writing files, landed through a change
request. No lock file, no tracked "installed" state โ git is the source of
truth for what's in this project.
A whole **project** item is the richest thing in the marketplace โ a working,
end-to-end Kortix project focused on a function. You can spin it up as its **own
new project** (from the web UI's "Add to a project" โ new project, which seeds
the files deterministically), or **import/merge it into this existing project**
via the recipe above to make this project bigger. It's all just files.
To make another registry's items discoverable here, add it as a **source** โ any
public git repo that ships `SKILL.md` files or a `marketplace.json` (e.g.
`anthropics/skills`, community repos from skills.sh). Curated sources enable in
one click; an arbitrary git URL is admin-gated. Once added, its items show up in
`kortix marketplace search`, and you import them the same way.
- **`kortix-marketplace`** (this) โ the Kortix catalog: whole projects + skills/
agents/tools, imported into this repo as owned files via a CR.
- **`find-skills-sh`** โ the open `npx skills` / skills.sh ecosystem, for pulling a
battle-tested community skill when the Kortix catalog doesn't have it.
Reach for the Kortix marketplace first for anything project-shaped; reach for
find-skills-sh to tap the wider open ecosystem. Either way you end up importing
plain files you own.
