venice

Venice Skills

Agent Skills for the Venice API. Skills are self-contained folders of instructions (one SKILL.md each) that an LLM agent loads on demand to work correctly against a specific surface area of the API.

This repository is the canonical source of truth for Venice skills and is kept in sync with swagger.yaml. Use it with Cursor, Claude, Codex, Cline, or any other agent runtime that supports the Agent Skills format.

What's in here

skills/        One folder per skill, each with a SKILL.md
template/      Copy this as a starting point for a new skill

Skill catalog

Skill	Covers
venice-api-overview	Base URL, auth modes, response headers, pricing model, versioning
venice-auth	Bearer API keys + SIWE / x402 wallet authentication
venice-chat	/chat/completions — venice_parameters, multimodal, tools, reasoning, streaming
venice-responses	/responses — OpenAI-compatible Responses API (Alpha)
venice-embeddings	/embeddings — models, encoding formats, dimensions
venice-image-generate	/image/generate, /images/generations, /image/styles
venice-image-edit	/image/edit, /image/multi-edit, /image/upscale, /image/background-remove
venice-audio-speech	/audio/speech — TTS models, voices, formats, streaming
venice-audio-music	/audio/quote, /audio/queue, /audio/retrieve, /audio/complete
venice-audio-transcription	/audio/transcriptions — Whisper, Parakeet, Scribe, Wizper, xAI STT
venice-video	/video/* generation + transcription
venice-models	/models, /models/traits, /models/compatibility_mapping
venice-characters	/characters* + venice_parameters.character_slug
venice-api-keys	CRUD /api_keys, rate limits, Web3 key generation
venice-billing	/billing/balance, /billing/usage, /billing/usage-analytics
venice-x402	/x402/* — wallet credits, USDC on Base
venice-crypto-rpc	/crypto/rpc/* — JSON-RPC proxy with 1×/2×/4× pricing
venice-augment	/augment/text-parser, /augment/scrape, /augment/search
venice-errors	Error shapes, 402 payment required, 422 content policy, 429 rate limits, retry strategy

Using these skills

Each skill is just a folder with a SKILL.md that starts with YAML frontmatter:

---
name: venice-chat
description: …when the agent should load this skill and what's in it…
---

Cursor

Clone or subtree the repo and point your agent skills path at skills/:

# project-local
git clone git@github.com:veniceai/skills.git .cursor/skills-venice
# or copy individual skills
cp -r skills/venice-chat .cursor/skills/

Claude / Codex / OpenCode / Hermes / other runtimes

The SKILL.md format is a shared spec — drop the skills/ folder (or any subset) into whichever path your runtime watches:

Runtime	Project-local	Global
Claude Code	.claude/skills/	~/.claude/skills/
Codex	.codex/skills/	$CODEX_HOME/skills/ (default ~/.codex/skills/)
OpenCode	.opencode/skills/ (also reads .claude/skills/ + .agents/skills/)	~/.config/opencode/skills/
Hermes Agent (Nous Research)	$HERMES_OPTIONAL_SKILLS_DIR	~/.hermes/skills/
Cursor	.cursor/skills/	~/.cursor/skills/
Cline	.clinerules/skills/	n/a
Any other runtime	.agents/skills/ (convention)	~/.agents/skills/

One-liner install for most setups:

# clone once
git clone https://github.com/veniceai/skills.git ~/src/venice-skills

# symlink into every runtime you use
ln -s ~/src/venice-skills/skills ~/.claude/skills/venice
ln -s ~/src/venice-skills/skills ~/.codex/skills/venice
ln -s ~/src/venice-skills/skills ~/.config/opencode/skills/venice
ln -s ~/src/venice-skills/skills ~/.hermes/skills/venice

The agent discovers each SKILL.md by its frontmatter name + description and loads it on demand. Runtimes that define extra frontmatter fields (version, platforms, metadata.*, compatibility, …) are required by spec to ignore unknown fields, so the same skill file works everywhere without forks.