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

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, pinned to a release
git clone --branch v0.2.0 [email protected]:veniceai/skills.git .cursor/skills-venice
# or copy individual skills
cp -r skills/venice-chat .cursor/skills/

Claude Code

Install the skills as a plugin from this repository’s marketplace. Inside Claude Code:

/plugin marketplace add veniceai/skills
/plugin install venice@venice

Or from a shell:

claude plugin marketplace add veniceai/skills
claude plugin install venice@venice

The skills are namespaced under the plugin, for example /venice:venice-chat. To pin a release, add the marketplace at a release tag, claude plugin marketplace add veniceai/skills@, using v0.3.0 or later; earlier tags don’t include the marketplace.

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:

One-liner install for most setups:

# clone once, pinned to a release
git clone --branch v0.2.0 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

Pin to a release

A single clone feeds every runtime you symlink it into, and some skills teach an agent to sign USDC payments and handle wallet keys. Pin to a release tag rather than tracking main, and upgrade deliberately after reading the changelog:

cd ~/src/venice-skills
git fetch --tags
git diff v0.2.0  -- skills/   # review what changed
git checkout 

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.

NanoCoder and similar minimal coding agents (Claw-Code, etc.) don’t ship their own skills runtime — they piggyback on whichever host agent (Claude Code, OpenCode, Hermes) is driving them. Install the skills in the host and NanoCoder will see them automatically.

As a git submodule

git submodule add [email protected]:veniceai/skills.git vendor/venice-skills
git -C vendor/venice-skills checkout v0.2.0

Then symlink or copy the subsets you want into your agent’s skill path.

Authoring a new skill

1. Copy template/ to skills//.
2. Fill in the frontmatter and body. Keep the description concrete — it’s what an agent uses to decide when to load the skill.
3. Link related skills at the bottom of the SKILL.md for cross-navigation.
4. Open a PR.

See CONTRIBUTING.md for style conventions (short first paragraph, explicit endpoint tables, curl + one SDK example, “gotchas” section, ≤ 500 lines).

Source of truth

Skills are derived from the current Venice OpenAPI spec and public docs at . When the spec changes, update the affected skills and cut a release.

Authentication quick reference

See skills/venice-auth for full signing details.

Staying in sync with the API

The skills are derived from the Venice OpenAPI spec. Run the sync script to diff the currently-published spec against the endpoints and model-type enums referenced in each SKILL.md:

python scripts/sync_from_swagger.py --spec https://api.venice.ai/api/v1/swagger.yaml
# or against a local copy
python scripts/sync_from_swagger.py --spec ./swagger.yaml

The script prints:

• endpoints in the spec that no skill references yet,
• endpoints referenced in skills but missing from the spec (stale docs),
• model-type enum drift (e.g. new type=… value added).

CI runs this nightly; any drift is filed as an issue with the sync label.

Integrity checks

Some skills teach an agent to sign USDC payments, hold wallet keys, manage API keys and send JSON-RPC to mainnets, so every change is gated before it can reach an install:

• scripts/check_skill_integrity.py runs on every PR and fails if lines added under skills/, scripts/, template/, AGENTS.md or skills.json introduce a URL host outside its allowlist (URLs are parsed, and credentials, percent-encoding, backslashes, missing slashes and templated hosts fail closed), a scheme-relative URL, a scheme-less host followed by a path in a curl / wget command, a wallet address other than the known USDC contracts and Solana mainnet id, a 0x + 64-hex or long base58 string that could be a private key, or curl / wget piped into a shell or interpreter. Run it locally with python scripts/check_skill_integrity.py --base origin/main. Extending an allowlist means editing that script, which needs a code-owner review.
• CODEOWNERS requires a review from @veniceai/api-reviewers, @tombystrican, @lightcap or @joshua-mo-143 for venice-x402, venice-auth, venice-api-keys, venice-crypto-rpc, scripts/ and .github/, and those PRs are labeled security-review.
• Releases are tagged; see Pin to a release and the changelog.

License

MIT — see LICENSE. Use these skills however you like; a credit link back to is appreciated but not required.