sub-skill

Reorganize skill inventories into hierarchical sub-skill bundles with backups.

18|8|Updated Jun 17, 2026
One-click install
npx skills add https://github.com/PyModel/pythinker-code --skill sub-skill-pymodel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sub-skill
Source: https://github.com/PyModel/pythinker-code/tree/main/packages/agent-core-v2/src/features/skill/catalog/builtin/sub-skill
Command: npx skills add https://github.com/PyModel/pythinker-code --skill sub-skill-pymodel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? As a skill inventory grows, loosely related skills become hard to discover and maintain. This Skill analyzes the existing inventory and reorganizes related skills into hierarchical parent bundles with sub-skills, keeping the catalog structured without losing any files. ## Core Features & Use Cases - Inventory Review (sub-skill.review): Scans the skill registry, groups skills by domain, detects coupling and granularity issues, and produces a read-only consolidation proposal. - Safe Consolidation (sub-skill.consolidate): Applies an approved grouping by moving skill directories under a parent bundle, creating timestamped backups of every modified directory first. - Documentation Alignment: Moves references, assets, examples, and templates together with each child skill so relative links keep working. - Use Case: You have separate web-search and fetch-url skills. Run a review to get a proposed web-research parent bundle, approve the plan, then consolidate moves both children under it with backups. ## Quick Start Review my current skill inventory and propose candidate sub-skill groupings, then consolidate the ones I approve.

Frequently Asked Questions about sub-skill

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

FAQPage Schema
How do I reorganize skills into sub-skill bundles?

Run the review step first to get a read-only proposal grouping skills by domain and coupling. After you approve a plan, the consolidate step moves each child skill directory under the parent bundle and sets has-sub-skill: true in the parent frontmatter.

How to safely move skill directories without losing files?

The consolidate process creates a timestamped backup copy of every skill directory before moving anything, using a cp -r command with a date-based suffix. Backups are never overwritten, and the entire directory including frontmatter and payload files is preserved.

Does the review step modify any skill files?

No, the review sub-skill is strictly read-only. It scans the skill registry, categorizes skills by domain, detects coupling, and outputs a proposal report. File changes only happen in the separate consolidate step after explicit user approval.

What happens to references and assets when a skill is moved?

Documentation payload directories such as references, assets, examples, and templates move together with their child skill so relative links from SKILL.md stay valid. They are never left in the old location or merged into unrelated directories.

When should I avoid creating sub-skill hierarchies?

Avoid hierarchies when skills do not share a domain or workflow, and avoid nesting deeper than two levels unless explicitly requested. A good grouping needs shared context, a composable parent entry point, and backward-compatible skill names.