catalog-porter

Analyze GitHub repositories and port agent skills into a local catalog.

1|1|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/yunseo-kim/agent-toolbox --skill catalog-porter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: catalog-porter
Source: https://github.com/yunseo-kim/agent-toolbox/tree/main/.agents/skills/catalog-porter
Command: npx skills add https://github.com/yunseo-kim/agent-toolbox --skill catalog-porter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of discovering, classifying, and integrating agent skills from external GitHub repositories into the catalog/skills/ directory, ensuring proper attribution, licensing, and documentation.

Core Features & Use Cases

  • Upstream Analysis: Scans provided GitHub repositories to identify potential agent skills.
  • Skill Classification: Determines the provenance (ported, adapted, synthesized, ignored) of each skill based on defined criteria.
  • Automated Porting: Creates catalog entries, including SKILL.md frontmatter, NOTICE.md attribution, and updates to tracking files.
  • Use Case: When you find a promising collection of agent skills on GitHub, use this Skill to analyze them and bring the compliant ones into your project's catalog with all necessary metadata and attributions.

Quick Start

Use the catalog porter skill to analyze and port skills from the GitHub repository at https://github.com/example/repo.

Frequently Asked Questions about catalog-porter

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

FAQPage Schema
How do I automate porting agent skills from a GitHub repository into a local catalog?

Automating GitHub repository porting involves cloning the repo, identifying skill units via SKILL.md files, and generating catalog metadata like frontmatter and NOTICE.md to integrate them locally.

What is the process for classifying upstream repository skills by license and attribution?

Classifying upstream repository skills involves analyzing provenance to categorize them as ported, adapted, synthesized, or ignored, ensuring proper license compliance and attribution tracking.

Do I need Python and Git installed to catalog agent skills from external sources?

Yes, you need Python and Git installed to catalog agent skills, as the porting process relies on Python scripts for file operations and Git for cloning and interacting with upstream repositories.

How are tracking files like upstream-sources.yaml and AGENTS.md updated when porting skills?

Tracking files like upstream-sources.yaml and AGENTS.md are updated automatically during the porting process to maintain accurate provenance records and document the newly integrated agent skills.

What's the best way to analyze external GitHub repositories for compatible agent skills?

The best way to analyze external GitHub repositories for compatible agent skills is to scan for SKILL.md files, evaluate license classifications, and generate the required catalog metadata structures.