feat: add client.skills namespace for skill management#126
Merged
shahrear33 merged 3 commits intomainfrom Feb 26, 2026
Merged
Conversation
Co-Authored-By: unknown <>
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
…unit tests for skills management
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a top-level
client.skillsnamespace to the Node SDK, exposing skill management methods directly on theVlmRunclient instead of nesting them underclient.agent.skills. This aligns with the updated docs convention from vlm-run/docs#191.New file:
src/client/skills.ts—Skillsclass with methods:list()→GET /v1/skillsget({ name?, id?, version? })→GET /v1/skills/{id}orPOST /v1/skills/lookupcreate({ prompt?, jsonSchema?, sessionId?, fileId?, name?, description? })→POST /v1/skills/createupdate({ skillId, fileId?, description? })→POST /v1/skills/{skill_id}/updatedownload({ skillId })→GET /v1/skills/{skill_id}/downloadNew types in
src/client/types.ts:SkillInfo,SkillDownloadResponse,SkillGetParams,SkillCreateParams,SkillUpdateParams,AgentSkillRegistration in
src/index.ts:this.skills = new Skills(this.client)Review & Testing Checklist for Human
SkillInfofields match the actual API response — the interface was inferred from docs, not the OpenAPI spec atagent.vlm.run/openapi.json. Confirm field names (id,name,description,version,created_at,updated_at,status) are correct and no required fields are missing.get()routing logic — when bothidandnameare provided, the method falls through to thenamebranch (lookup), not theidbranch (direct GET). Confirm this is the desired behavior or ifidshould take precedence.skills,skills/lookup,skills/create,skills/{id}/update,skills/{id}/downloadexist on the agent API base URL. Confirm these match the live API.client.skills.list()against the agent API to confirm the plumbing works.AgentSkillinterface is exported but unused — it's available for consumers but not referenced internally. Confirm this is intentional for downstream use.Notes