nested-skill

Platform discovery for a nested SKILL.md works by scanning multi-level skill trees to traverse into nested directories, registering the inner skill metadata into the catalog to verify visibility. It requires standard frontmatter and activation instructions for successful detection.

Yes, nested skill directories allow you to register multiple skills under a single parent platform. Platforms scanning multi-level skill trees will traverse into the references directory, identify the nested SKILL.md, and register it in the catalog if valid frontmatter is present.

To verify nested skill canary visibility, you need a platform that scans multi-level skill trees, a SKILL.md with name and description frontmatter, an activation instruction in the body, and a canary phrase to confirm successful recognition and end-to-end catalog loading.

To test deep discovery and activation of nested skills, place a SKILL.md inside another skill's references directory. Activate the nested skill by triggering the specified activation instruction and confirm it responds with the successful loading message to verify catalog registration.

A nested SKILL.md may not show up in the platform catalog if the platform lacks multi-level traversal capabilities, or if the file is missing required frontmatter fields like name and description, or lacks the necessary activation instructions in the body.

Yes, nested-skill supports testing catalog visibility for skills without dependencies. It validates multi-level traversal and registration by requiring only a SKILL.md file with proper frontmatter and activation instructions, ensuring platforms can discover standalone nested components.