Parent Test Skill

Locate the nearest SKILL.md in a parent directory and extract its name and description.

Updated Mar 27, 2022
One-click install
npx skills add https://github.com/emliunix/home.conf --skill parent-test-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Parent Test Skill
Source: https://github.com/emliunix/home.conf/tree/main/tskill/tests/fixtures/test_parent_repo/skills/test_skill
Command: npx skills add https://github.com/emliunix/home.conf --skill parent-test-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify skills located in a parent directory and surface their metadata to enable discovery and reuse in tooling and tests.

Core Features & Use Cases

  • Parent-scope skill discovery: locate the nearest SKILL.md in a parent directory and extract its name and description.
  • Metadata exposure: provide the skill's name and description for downstream tooling.
  • Reference and validation: assist in validating skill presence within repository structures.

Quick Start

Run the skill discovery from a nested directory to load the parent directory's SKILL.md.

Frequently Asked Questions about Parent Test Skill

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

FAQPage Schema
How do I discover skills located in a parent directory?

Parent directory skill discovery works by scanning ancestor paths from a nested directory to locate the nearest SKILL.md file. It then extracts the name and description from the frontmatter to enable skill reuse in tooling.

What is parent-scope skill discovery used for?

Parent-scope skill discovery is used to locate and surface metadata from a SKILL.md in an ancestor directory. It enables downstream tooling to reference and validate skills within nested repository structures.

Do I need a SKILL.md file in the parent directory to discover skills?

Yes, you need a SKILL.md file in the target parent directory to discover skills. The file must contain a name and description in its frontmatter for the discovery process to extract and surface the metadata.

How do I validate skill presence within nested repository structures?

You validate skill presence within nested repository structures by running discovery from a nested directory. The tool checks ancestor paths for a SKILL.md file and exposes its metadata for reference and validation.

Can I use this to find skills from any ancestor path in a nested project?

Yes, you can use this to find skills from ancestor paths in a nested project. It locates the nearest SKILL.md in a parent directory and surfaces its name and description for downstream tooling and tests.