agentleFS
veniceaiveniceai/skills/AGENTS.md

skills

AGENTS.md171 starsChanged 12 days agoMITView on GitHub

This repo is the authoritative Venice API reference, kept in sync with the Venice OpenAPI spec. When you build anything that touches the Venice API — guides, code samples, sandboxes, scripts — load the relevant skill instead of guessing endpoints, params, or model slugs. New skill? Copy template/ to skills/<name>/ and follow CONTRIBUTING.md. Source of truth: the Venice OpenAPI spec + public docs at https://docs.venice.ai. For the broader product/surface picture (every endpoint mapped to user actions), see the sibling venice-kb/…

The file

We split this AGENTS.md into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Treat its endpoint tables, params, and curl/SDK examples as the source of truth.

    line 13
  2. Very specific:

    If a skill looks stale vs.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 42,283 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Agent guide — venice-skills

This repo is the authoritative Venice API reference, kept in sync with the Venice OpenAPI spec. When you build anything that touches the Venice API — guides, code samples, sandboxes, scripts — load the relevant skill instead of guessing endpoints, params, or model slugs.

Read this first

  • README.md — the full skill catalog and how the format works.
  • skills/<name>/SKILL.md — one self-contained reference per API surface (auth, chat, image, video, audio, embeddings, billing, errors, etc.).

How to use

  1. Pick the skill matching the surface you're documenting (e.g. venice-image-generate, venice-video, venice-chat, venice-text-routing).
  2. Treat its endpoint tables, params, and curl/SDK examples as the source of truth.
  3. If a skill looks stale vs. the live API, flag it — don't invent. scripts/sync_from_swagger.py checks for drift against the spec.

Authoring

New skill? Copy template/ to skills/<name>/ and follow CONTRIBUTING.md.

Source of truth: the Venice OpenAPI spec + public docs at https://docs.venice.ai. For the broader product/surface picture (every endpoint mapped to user actions), see the sibling venice-kb/ repo.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.