Voyager pattern: validate a procedural skill store before you trust a saved skill

The Stack

Steps

1. 1

   Capture a skill and validate the library structure

   After a task succeeds, save the working script under a descriptive slug with a language tag. CI checks the library has at least one skill entry with all required fields and non-trivial code. Retrieving and running a skill by an agent is fenced.

   cat > skill-library.json <<'JSON'
   {
     "version": 1,
     "skills": [
       {
         "slug": "deploy-vercel-preview",
         "description": "Deploy a Vercel preview branch from a git checkout and return the preview URL",
         "language": "shell",
         "tags": ["deploy", "vercel", "ci"],
         "code": "git checkout -b preview/$1 && vercel --yes --env NEXT_PUBLIC_ENV=preview 2>&1 | tail -1"
       }
     ]
   }
   JSON
   node -e '
   const fs = require("fs");
   const lib = JSON.parse(fs.readFileSync("skill-library.json", "utf8"));
   function bad(m) { console.error("BAD: " + m); process.exit(1); }
   if (typeof lib.version !== "number") bad("version must be a number");
   if (!Array.isArray(lib.skills) || lib.skills.length === 0) bad("skills must be a non-empty array");
   for (const s of lib.skills) {
     if (!s.slug || typeof s.slug !== "string") bad("each skill must have a string slug");
     if (!s.description || s.description.length < 10) bad("skill " + s.slug + " needs a real description (>=10 chars)");
     if (!s.language) bad("skill " + s.slug + " must declare a language");
     if (!s.code || s.code.length < 10) bad("skill " + s.slug + " must have non-trivial code (>=10 chars)");
   }
   console.log("skill-library OK: " + lib.skills.length + " skill(s) validated (" + lib.skills.map(function(s){return s.slug;}).join(", ") + ")");
   '

2. 2

   Retrieve and reuse skills by agent (the execution step, not checked by CI)

   At task time, embed the task description, find the closest-matching skill by cosine similarity or keyword search, and inject the code as a starting point. After success, upsert the (possibly improved) code back. The match scoring and execution are fenced.