Spice.ai Marketplace

Open Agent Skills and plugins for AI coding agents working with the Spice.ai OSS runtime — data federation, acceleration, search, AI/LLM, and cloud management.

This is the Spice.ai Marketplace: packaged skills/plugins any compatible harness can load. The format works across Claude Code, Cursor, Codex, Grok, OpenCode, Pi, and other agents that support the open Agent Skills / plugin standard — not Claude-only.

Installation

OpenAI Codex

npx skills add spiceai/skills -a codex

Global (all projects):

npx skills add spiceai/skills -g -a codex

Skills install under .agents/skills/ (project) or ~/.codex/skills/ (global). Inside a Codex session you can also run $skill-installer and point it at spiceai/skills, then restart Codex if the skills do not appear. Verify with /skills.

See Codex Skills.

Publish (maintainers): for the universal ChatGPT/Codex Plugins Directory, submit the repo (skills-only) via the OpenAI plugin submission portal. Compatibility manifest: .codex-plugin/plugin.json; portable Agent Plugins: plugin.json. Local/repo catalog: .agents/plugins/marketplace.json (codex plugin marketplace add spiceai/skills).

Grok Build

npx skills add spiceai/skills -a grok

Or install as a Grok plugin from the repo:

grok plugin install spiceai/skills --trust

Add this repo as a marketplace source, then install spiceai-skills:

grok plugin marketplace add spiceai/skills
grok plugin install spiceai-skills --trust

Browse/install from the TUI with /marketplace or /plugins. Skills land in .grok/skills/ (project) or ~/.grok/skills/ (global). Native manifests: .grok-plugin/plugin.json + .grok-plugin/marketplace.json. Grok also reads Claude Code marketplaces and .agents/skills/ with no extra setup — see Skills, Plugins & Marketplaces.

Publish (maintainers): after merge, open a PR to xai-org/plugin-marketplace adding a remote catalog entry for spiceai-skills pinned to a full commit sha of spiceai/skills (see their CONTRIBUTING). Until that lands, users can still grok plugin marketplace add spiceai/skills or grok plugin install spiceai/skills --trust.

Grok Bot

Grok Bot teammates use the same Agent Skills format. Install Spice skills into the Cursor skill paths the Bot shares:

npx skills add spiceai/skills -a cursor

Or ask a Grok Bot (or open Settings → Plugins) to add the spiceai/skills marketplace/plugin. After install, start a new Bot turn so the skills catalog refreshes.

Cursor (plugin marketplace)

Install skills into Cursor paths:

npx skills add spiceai/skills -a cursor

Or add this repo as a Cursor plugin / Team Marketplace source (requires .cursor-plugin/plugin.json).

Publish (maintainers): submit https://github.com/spiceai/skills at cursor.com/marketplace/publish after manifests land on trunk. Plugin id: spiceai-skills @ 2.3.1.

Other agents (`npx`)

npx skills add spiceai/skills

Target a specific harness with -a (examples: opencode, pi, claude-code, cursor). Use -g for a user-global install. Once installed, skills activate when the agent detects a relevant Spice task.

Claude Code (plugin marketplace)

/plugin marketplace add spiceai/skills
/plugin install skills@spiceai

Skills are then available as /skills:spice-setup, /skills:spice-ai, /skills:spicepod-config, etc.

Project-level auto-discovery (Claude Code)

To auto-suggest the plugin for all contributors, add this to your project's .claude/settings.json:

{
  "extraKnownMarketplaces": {
    "spiceai": {
      "source": {
        "source": "github",
        "repo": "spiceai/skills"
      }
    }
  },
  "enabledPlugins": {
    "skills@spiceai": true
  }
}

Versioning

Skills versions match the Spice.ai OSS runtime they target (e.g. 2.3.1 with runtime v2.3.1). Pin to GitHub release tag v2.3.1 when you need a fixed surface, or use trunk for latest.

The skills are version-aware. Each one names the release line it is written for, tells the agent to check your runtime version (spice version) before it recommends configuration, marks features added after v2.0.0 with the release that shipped them (for example (v2.2.0+)), and lists removed or deprecated configuration with its replacement. On an older runtime, the agent can then avoid newer settings and use the docs for your release (https://spiceai.org/docs/v2.2/...).

Available Skills

Skill	Description
spice-setup	Install Spice, initialize a project, and run the runtime
spicepod-config	Create and configure spicepod.yaml manifests
spice-connect-data	Connect to data sources and query across them with federated SQL
spice-data-connector	Configure individual data source connectors (PostgreSQL, S3, Snowflake, etc.)
spice-acceleration	Accelerate data locally for sub-second query performance
spice-accelerators	Choose and configure acceleration engines (Arrow, DuckDB, SQLite, etc.)
spice-search	Search with vector similarity, full-text keywords, or hybrid RRF
spice-ai	Add AI capabilities — tools, NSQL, memory, model routing
spice-models	Configure LLM providers (OpenAI, Anthropic, Azure, local GGUF, etc.)
spice-text-to-sql	Generate SQL for Spice's DataFusion engine and build text-to-SQL workflows
spice-caching	Cache query and search results with TTL and stale-while-revalidate
spice-secrets	Manage credentials with secret stores
spice-cloud-management	Manage Spice.ai Cloud resources via the Management API
spice-terraform	Manage Spice.ai Cloud infrastructure as code with Terraform

Maintaining this repo

Skill	Description
improve-skills	Weekly audit that keeps the skills above current with what has shipped

improve-skills is for maintainers of this repo rather than for using Spice. It audits published Spice.ai releases for user-visible changes, routes each one to the skills it affects, applies the edits through skill-creator, runs the eval regression gate, and opens a PR. Every fact it publishes must be citable from a public source; see its disclosure policy.

References

License

MIT