Context
PR #1224 bundles skills into the npm package and adds agentv skills subcommand. This issue addresses follow-up refinements discussed in design review.
Changes
1. Add --ref flag to skills get
Allow loading individual reference files without --full:
agentv skills get agentv-bench --ref eval-yaml-spec # one reference
agentv skills get agentv-bench --full # all references (existing)
agentv skills get agentv-bench # SKILL.md only (existing)
Implementation: read <skill-dir>/references/<ref>.md (or templates/<ref>) and print to stdout.
2. Include agents/ in --full output
Add agents to the readSkill collect loop so agent role definitions (executor.md, grader.md, etc.) are included when --full is used:
// Before
for (const sub of ['references', 'templates']) {
// After
for (const sub of ['references', 'templates', 'agents']) {
3. Drop scripts/ and assets/ from bundled skills
Scripts (Python, bash, HTML) should not be shipped in the skill bundle. Either:
- Convert to CLI subcommands (e.g.
agentv eval lint replaces lint_eval.py)
- Or remove entirely if not needed (onboarding script already covered by
agentv init, trajectory HTML by agentv studio)
Remove scripts/ and assets/ directories from apps/cli/skills/ before the build copies them to dist/skills/.
4. Update SKILL.md files to document skills path usage
Add a note to each skill's SKILL.md explaining how to access individual reference files:
## Accessing reference files
To load a specific reference, use:
bash
cat $(agentv skills path <skill-name>)/references/<filename>.md
Or use the --ref flag: agentv skills get <skill-name> --ref <filename>
5. Remove plugin requirement from docs
Update README and onboarding docs to reflect that npm install -g agentv is sufficient — no separate plugin installation needed.
Relationship to agent-browser
This aligns agentv with agent-browser's pattern: skills are bundled in the npm package at dist/skills/ (analogous to skill-data/), agents read files from the known path via skills path, and --full is a convenience shortcut for bulk loading.
Acceptance criteria
Parent
#1224
Context
PR #1224 bundles skills into the npm package and adds
agentv skillssubcommand. This issue addresses follow-up refinements discussed in design review.Changes
1. Add
--refflag toskills getAllow loading individual reference files without
--full:Implementation: read
<skill-dir>/references/<ref>.md(ortemplates/<ref>) and print to stdout.2. Include
agents/in--fulloutputAdd
agentsto thereadSkillcollect loop so agent role definitions (executor.md, grader.md, etc.) are included when--fullis used:3. Drop
scripts/andassets/from bundled skillsScripts (Python, bash, HTML) should not be shipped in the skill bundle. Either:
agentv eval lintreplaceslint_eval.py)agentv init, trajectory HTML byagentv studio)Remove
scripts/andassets/directories fromapps/cli/skills/before the build copies them todist/skills/.4. Update SKILL.md files to document
skills pathusageAdd a note to each skill's SKILL.md explaining how to access individual reference files:
Or use the --ref flag:
agentv skills get <skill-name> --ref <filename>5. Remove plugin requirement from docs
Update README and onboarding docs to reflect that
npm install -g agentvis sufficient — no separate plugin installation needed.Relationship to agent-browser
This aligns agentv with agent-browser's pattern: skills are bundled in the npm package at
dist/skills/(analogous toskill-data/), agents read files from the known path viaskills path, and--fullis a convenience shortcut for bulk loading.Acceptance criteria
skills get <name> --ref <file>returns a single reference fileskills get <name> --fullincludes agents/ contentscripts/andassets/removed from bundled skillsskills pathusageParent
#1224