Skip to main content
Skills are reusable prompt packages that provide an agent with domain knowledge, procedures, and scripts. VeADK 1.0.1 recommends Google ADK’s SkillToolset for local and cloud skills. The existing Agent(skills=..., skills_mode="local") entry point remains available but is deprecated. The skills_sandbox and aio_sandbox modes are unchanged.

Use local skills

Load a skill directory with ADK’s load_skill_from_dir, then pass a SkillToolset to the VeADK agent:
ADK loads the skill, provides its prompt to the model, and exposes the list_skills, load_skill, load_skill_resource, and run_skill_script tools. If a skill runs files under scripts/, configure a code executor on the SkillToolset or agent. VeADK does not create a local code executor automatically.
Skill scripts can access the files and runtime exposed by the code executor. Load only trusted skills and restrict the executor to the permissions they need.

Use cloud skills

VeADK 1.0.1 adds VeSkillRegistry, which exposes skills from SkillHub or a Skill Space through the ADK registry interface:
search_skills retrieves the remote skill list, while get_skill downloads and loads a specific version when requested. This approach does not download every skill at initialization.

Skill directory

An ADK local skill has its own directory. It must contain SKILL.md and can also include references, assets, and scripts:
The SKILL.md frontmatter must define name and description, and the directory name should match name:
skills/kb-skill/SKILL.md

Legacy entry-point compatibility

The legacy entry point supports these modes: If skills_mode is unset, VeADK selects a mode from the runtime environment: local runs use local; an AgentKit tool runtime uses skills_sandbox or aio_sandbox according to its tool type. Legacy local example:
Legacy sandbox example:

Legacy parameters

Last modified on September 19, 2026