nested-skill

Recursively discover and validate nested SKILL.md frontmatter in directory trees.

Updated Apr 22, 2026
One-click install
npx skills add https://github.com/yxc023/agent-config-studio --skill nested-skill-yxc023
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nested-skill
Source: https://github.com/yxc023/agent-config-studio/tree/main/test/test-workspace/.opencode/skills/test-group/nested-skill
Command: npx skills add https://github.com/yxc023/agent-config-studio --skill nested-skill-yxc023

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify and validate Skill units that reside in nested directories, ensuring every SKILL.md includes required frontmatter (name and description) and is discoverable at any depth.

Core Features & Use Cases

  • Recursive discovery of Skill units across arbitrary directory depths.
  • Frontmatter validation to ensure each SKILL.md contains a valid name and description.
  • Generate a consolidated view of discovered skills for auditing and onboarding.

Quick Start

Scan the repository to discover all nested Skill units by recursively locating SKILL.md frontmatter and validating name and description.

Frequently Asked Questions about nested-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I discover nested SKILL.md files across a multi-level directory structure?

Recursive directory scanning locates every SKILL.md file at any depth within a repository. It then extracts metadata from each file, providing a consolidated view of all discovered nested skill units.

How does frontmatter validation work for skill metadata in subdirectories?

Frontmatter validation checks that each discovered SKILL.md file contains the required name and description fields. This ensures every nested skill unit is properly documented and discoverable at any directory level.

Can I extract dependencies and component presence from deeply nested skill trees?

Yes, the recursive discovery process reports dependencies and component presence for each located SKILL.md file. This enables comprehensive auditing of skill trees containing multiple subdirectories and nested units.

What is the best way to audit skill units across arbitrary directory depths?

Running a recursive scan to locate SKILL.md files and validate their frontmatter is the best way to audit skill units. This generates a consolidated view of all discovered skills for onboarding and review.

Do I need any external dependencies to scan a repository for nested skill units?

No external dependencies are required to scan for nested skill units. The discovery process works directly on the repository's directory structure to locate and validate SKILL.md files natively.