child-skill

Activate a nested skill from a subdirectory using SKILL.md frontmatter.

484|76|Updated Oct 23, 2025

Search Tags:#repository organization #skill loading #subdirectory #modular instructions #nested skill

Ready to run

npx skills add https://github.com/bastani-inc/atomic --skill child-skill-bastani-inc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: child-skill
Source: https://github.com/bastani-inc/atomic/tree/main/packages/coding-agent/test/fixtures/skills/nested/child-skill
Command: npx skills add https://github.com/bastani-inc/atomic --skill child-skill-bastani-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you package and activate a reusable capability that lives in a subdirectory, keeping larger repositories organized without losing discoverability.

Core Features & Use Cases

Nested Skill Structure: Demonstrates how a skill can exist outside the repository root while still remaining self-contained.
Modular Organization: Useful for splitting related instructions into smaller, maintainable units.
Use Case: Add this pattern when you want a child directory to behave like an independent skill with its own entry point.

Quick Start

Ask the assistant to use the child-skill instructions from the nested subdirectory.

Frequently Asked Questions about child-skill

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

FAQPage Schema

How do I load a nested skill from a subdirectory without breaking repository organization?▼

To load a nested skill from a subdirectory, you need a valid SKILL.md frontmatter entry containing a name and description to support discovery and activation of the self-contained instructions.

What is a modular instruction set and when do I need it for my repository?▼

A modular instruction set splits related instructions into smaller, maintainable units. You need it when organizing larger repositories that require reusable workflows and isolated skill entry points.

How do I set up a subdirectory to behave like an independent skill with its own entry point?▼

You set up a self-contained nested skill in a subdirectory by adding a SKILL.md file with valid frontmatter, including a name and description, to serve as the isolated skill entry point.

Does a nested skill in a subdirectory require specific frontmatter to be discoverable?▼

Yes, nested skills require a valid SKILL.md frontmatter entry with a name and description to support discovery and loading by the assistant.

Can I split related instructions into smaller units while keeping them discoverable in a large repository?▼

Yes, you can split instructions into smaller units by using a nested skill structure in subdirectories, which keeps larger repositories organized without losing discoverability.

What's the best way to organize reusable workflows in isolated subdirectories?▼

The best way to organize reusable workflows is using a nested skill structure with self-contained instructions and a SKILL.md entry point in each isolated subdirectory.