skills trained

Each moe-* guru carries one discoverable SKILL.md. Companion guides live beside it as SUBSKILL.md files rather than as competing discoverable entry points, and a single-file guide folds into its guru's directory. A router selects the guide, while this layer resolves conflicts with local law.

Run skillsearch index after reference content changes. The skills fleet's AGENTS.md owns its shape and validation requirements. For a user-authorized external install, verify current syntax in the official Skills CLI docs and CLI repository before executing it; search results alone are not an installation decision. The current upstream example for a selected global skill is npx skills add owner/repo --skill <name> -g -a codex -y; it was source-checked, not run here.

• Search local skillsearch first; check the root guru and its relevant guide before seeking an external source.
• Preserve useful source guidance while removing commands that cannot run here. Put decisions that span guides in the root router and this layer.
• Verify the candidate's actual source and trust boundary before installing. An install or update writes global state and needs user task authority.
• Use plugin-creator only for an explicitly authorized plugin task. A skill request does not imply a plugin request.

• One router per domain avoids competing discoverable skills.
• Local semantic search gives a fast entrypoint into the installed fleet.

• Bundled examples can describe another runtime's directories and tools.
• Popularity and install counts change; they cannot replace source review.

• skill-installer targets a separate installation directory's skills folder, not this fleet of moe-* guides.
• The writing-skills and skill-creator upstream layouts allow nested SKILL.md files and one-file wrappers. Local law forbids both.
• Plugin marketplace scaffolding, cachebusting, and reinstalling are external changes; do not infer authorization from an ordinary skill edit.

No version-specific Skills CLI or skillsearch defect was confirmed in this audit. Check current CLI docs again when installing or updating.

• A guide whose cross-references point at a nonexistent sibling SKILL.md breaks quietly after a rename. Re-point them at the SUBSKILL.md guide that actually exists.
• A single-file fixture, grader, or example sitting alone in its own folder signals the upstream wrapper layout. Flatten the file into its guide's directory and update its consumers.

• skillsearch found git and review for an audit query. skillsearch check reported 40 live skills and 10 stale indexes before the index was rebuilt; rebuild the index after every content change.
• Three one-file folders under the covered gurus were flattened into their guide directories, and the eval fixture, grader, and example reference moved with them. In a scratch directory the grader scored a broken fixture 0/5 and a valid fixture 5/5. No external skill or plugin was installed.