POST /v1/skills with custom_llm_provider=litellm_proxy ignores version, never sets latest_version

[RenoV8-tls]

Hello

What happened?

On custom_llm_provider=litellm_proxy, latest_version on a created skill is always null, and there's no documented way to set a version on create or attach one afterward (POST /v1/skills/{id}/versions returns 404; not in the OpenAPI schema).

Reproduction

curl -X POST "http://localhost:4000/v1/skills?beta=true&custom_llm_provider=litellm_proxy" \
  -H "Authorization: Bearer sk-1234" \
  -F "display_title=version-test" \
  -F "version=1.2.3" \
  -F "files[]=@hello-world.zip"

Response:

{"id":"litellm_skill_01c3c83f-...","display_title":"version-test","latest_version":null,"description":null,...}

The version form field has no effect. description is also not parsed from the uploaded SKILL.md, even though the archive itself is stored correctly (confirmed by downloading it back via GET /v1/skills/{id}/archive).

Question

Is there a supported way to set/attach a version for a litellm_proxy-stored skill? If not, is this planned?
Is it possible to give a list of all the parameters available for POST /v1/skills?

LiteLLM version

1.108.0

[g4lb]

No. In v1.108.0, litellm_proxy skills have no versions: create_skill does not write latest_version.

Form fields: display_title, description, instructions, files. LiteLLM does not read description from SKILL.md, so send it as a form field.