SkillToolset, and connect cloud skill spaces
through VeADK’s VeSkillRegistry.
Local skills
Load a local skill directory with ADK’sload_skill_from_dir and pass it as a
standard toolset to the agent:
list_skills, load_skill,
load_skill_resource, and run_skill_script. If a skill runs scripts from
scripts/, configure a suitable code_executor on the SkillToolset or the
agent — VeADK does not create a local code executor by default.
Cloud skill spaces
Connect a cloud skill space throughVeSkillRegistry, then hand it to
SkillToolset:
search_skills fetches the remote
skill list in real time, and get_skill downloads and loads a specific skill on
demand; when the remote version changes, the new version is re-downloaded.
Skill directory layout
A local skill is a directory containing aSKILL.md file, and may include
references/, assets/, and scripts/ subdirectories:
SKILL.md must declare name and description in frontmatter, and the
directory name must match name:
SKILL.md
Legacy local entry (deprecated)
VeADK’s oldAgent(skills=..., skills_mode="local") local entry still works but
is deprecated; migrate to SkillToolset above. The skills_sandbox and
aio_sandbox modes are unaffected and used as before:
Sandbox mode example: