🤖 Generated by the Daily AI Engineer
Problem. AGENTS.md → Validation step 3 asserts each plugin.json has .skills == "skills/", but the repo convention now omits the bare-string skills/agents fields (they are auto-discovered). Running the documented step 3 locally reports BAD fields for all 8 plugins — the doc snippet drifted from the real CI gate (CI validates via the real tool, not this check). Found while running the documented validation for #63.
Proposed direction. Update the step-3 snippet to match the actual convention (drop the .skills=="skills/" assertion; validate the non-empty name/description/version + the presence of a skills/ dir with at least one SKILL.md, consistent with CI). Trivial doc fix.
Size. XS.
Problem.
AGENTS.md→ Validation step 3 asserts eachplugin.jsonhas.skills == "skills/", but the repo convention now omits the bare-stringskills/agentsfields (they are auto-discovered). Running the documented step 3 locally reportsBAD fieldsfor all 8 plugins — the doc snippet drifted from the real CI gate (CI validates via the real tool, not this check). Found while running the documented validation for #63.Proposed direction. Update the step-3 snippet to match the actual convention (drop the
.skills=="skills/"assertion; validate the non-empty name/description/version + the presence of askills/dir with at least oneSKILL.md, consistent with CI). Trivial doc fix.Size. XS.