Skip to content

docs(skills): align parent-agent skills with current CLI - #1509

Open
vkehfdl1 wants to merge 2 commits into
mainfrom
docs/fix-parent-agent-skills
Open

docs(skills): align parent-agent skills with current CLI#1509
vkehfdl1 wants to merge 2 commits into
mainfrom
docs/fix-parent-agent-skills

Conversation

@vkehfdl1

@vkehfdl1 vkehfdl1 commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Fix AutoRAG Vercel/parent-agent skills so a higher-level agent can drive search and setup against current main
  • Correct stale contracts: MinSync auto-install is on by default, sessionId is only in --json --debug, HWP is a supported parser, unknown datasource names are skipped, and autorag ui is the datasource setup path
  • Add a contract test that locks those skill claims to the live CLI/config behavior

What was wrong

Parent agents following skills/autorag and skills/autorag-setup would do the wrong thing:

  • Tell the user MinSync must already be on PATH (auto-install has been default since fix: enable MinSync auto-install by default #1505)
  • Call autorag search --json and look for sessionId to record feedback (that field is debug-only)
  • Treat .hwp as unsupported (rhwp parses .hwp and .hwpx)
  • Assume unknown datasource names abort config resolution (they emit unknown-datasource-skill and continue)
  • Hand-edit datasource JSON and miss autorag ui, AUTORAG_HOME, and builtin templates such as kakao, clawgallery, and mail-export

Verification

  • bun test test/cli/skill-docs.test.ts — 6 pass
  • bun run lint — no issues in the changed files (pre-existing biome schema version info only)

Correct AutoRAG and AutoRAG-setup skill docs so a parent agent can drive
the librarian without stale contracts: MinSync auto-install on by default,
search sessionId only with --json --debug, HWP supported, unknown
datasources skipped, and autorag ui as the datasource setup path.
Windows checkout uses CRLF, so newline-anchored skill contract assertions
failed. Normalize skill markdown before matching.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant