Root skill should win.

Root skill discovery takes precedence by selecting the root-level SKILL.md as the authoritative entry point and ignoring nested child skill definitions. This enforces deterministic directory traversal behavior in repositories with multiple skill-like directories.

Frontmatter recognition during fixture validation identifies the root-level entry point in a repository and excludes nested SKILL.md files. This enforces precedence rules to ensure only the top-level skill is activated.

Yes, directory traversal can ignore child SKILL.md files when a valid root skill is present. The system applies root precedence rules to exclude nested skill definitions and select only the root-level frontmatter entry point.

Skill discovery selects the root-level frontmatter entry point to ensure deterministic behavior in repositories containing fixture trees or multiple skill-like directories. This root precedence mechanism ignores nested SKILL.md files to avoid conflicts.

The best way to handle multiple SKILL.md files is to enforce root precedence by activating the root-level SKILL.md and excluding nested skill definitions. This approach ensures deterministic skill discovery and avoids ambiguity in directory traversal.

You need root precedence rules for skill discovery when a repository contains both root and nested SKILL.md files, such as in fixture trees or directories with multiple skill-like structures. This ensures the correct top-level entry point is selected.