vm0-agent_skill

This skill guides you through building, deploying, and scheduling AI agents on VM0, from requirements to production with observable execution.

Shell

39

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill vm0-ai/vm0-skills --skill vm0-agent

SKILL.md22.9 KB

Overview

This skill guides you to build, deploy, and operate AI agents on VM0's agent-native infrastructure. It covers the full lifecycle from intent analysis and composing vm0.yaml/AGENTS.md to collecting secrets, running tests, scheduling, and monitoring. The goal is reproducible, observable, and scheduled agent automation.

How this skill works

The skill walks you through three main phases: Research (clarify the recurring workflow and sources), Innovate (select appropriate skills and convert them into VM0-compatible configurations), and Compose (author vm0.yaml and AGENTS.md, collect credentials, and deploy). It uses VM0 CLI commands for cloning, composing, running, listing agents/schedules, and managing secrets and variables to ensure correct cloud deployment and scheduled execution.

When to use it

You want to automate a recurring workflow (daily digest, repo reports, site monitoring, etc.)
You need to move an agent from local development to reliable cloud execution and scheduling
You need help composing vm0.yaml and AGENTS.md for a new agent
You must add or rotate credentials and ensure scheduled runs have required secrets
You want to verify current agents, view schedules, and inspect recent activity

Best practices

Start with a clear recurring workflow framed as Fetch → Process → Output
Always clone the remote agent config before modifying: vm0 agent clone <name> /tmp/<name>
Keep secrets in VM0 remote secrets via vm0 secret set and non-sensitive config in vm0 variable set
Use vm0 compose to deploy; it is idempotent—successful compose without version change is normal
Run test prompts with vm0 cook and inspect logs/artifacts to iterate until stable

Example use cases

Daily tech digest: fetch RSS/YouTube, summarize, and post to Slack or Notion every morning
Weekly repository report: aggregate PRs/issues/commits and deliver a team summary
Website change monitor: crawl target pages, diff content, and alert only on detected changes
Customer support automation: poll an inbox, auto-reply common queries, and escalate via Slack
Crypto morning briefing: aggregate price feeds and news into a concise morning report

FAQ

Run vm0 agent ls to list agents and vm0 schedule ls to list scheduled tasks; summarize recent activity from the CLI output.

What is the correct way to fetch an agent configuration from the cloud?

Use vm0 agent clone <agent-name> /tmp/<agent-name> to download vm0.yaml and AGENTS.md from the cloud before making updates.

What if my compose doesn’t change the version hash?

This is expected if the configuration is identical; vm0 compose is idempotent and a stable hash means no changes were deployed.