skills-manager

Discover, import, and normalize skills from registries into a library.

2|1|Updated Jul 19, 2024

Search Tags:#automation #library #skills #repository #import #version-control #normalize

Ready to run

npx skills add https://github.com/TeamDay-AI/agents --skill skills-manager-teamday-ai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: skills-manager
Source: https://github.com/TeamDay-AI/agents/tree/main/skills/teamday/skills-manager
Command: npx skills add https://github.com/TeamDay-AI/agents --skill skills-manager-teamday-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintains the centralized TeamDay skills library by discovering, importing, and normalizing skills from multiple sources, ensuring a consistent structure and up-to-date catalog.

Core Features & Use Cases

Discover new skills from registries like awesome-agent-skills and provider submodules, centralizing them in skills/community.
Normalize skill structures (frontmatter) and prepare entries for commit, including licensing attribution when available.
Update existing skills and coordinate with provider submodules to keep the library in sync with upstream sources.

Quick Start

Identify a new skill in a registry, import it into skills/community, normalize its structure, validate the frontmatter, and commit the changes.

Frequently Asked Questions about skills-manager

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

FAQPage Schema

How do I import skills from a registry into a centralized library?▼

To import skills from a registry, you discover them from sources like awesome-agent-skills and provider submodules, then import and normalize their structure into a centralized community directory before committing. This ensures a consistent, up-to-date catalog.

What does normalizing a skill's frontmatter structure involve?▼

Normalizing skill frontmatter involves validating that the SKILL.md file contains required fields like name and description. It ensures consistent structure, validates repository integrity, and prepares the skill entry for commit with proper licensing attribution.

Can I use this to sync my skills library with upstream provider submodules?▼

Yes, you can sync your skills library with upstream sources by updating existing skills and coordinating with provider submodules. This keeps your centralized catalog in sync with the latest upstream changes from registries.

What is the best way to maintain a centralized skills repository across multiple sources?▼

The best way to maintain a centralized skills repository is to automate the discovery, import, and normalization of entries from multiple sources. This validates structure and licensing while keeping the catalog consistently updated with upstream changes.

Do I need specific frontmatter fields when onboarding new skills?▼

Yes, when onboarding new skills you need the SKILL.md frontmatter to contain required fields, specifically name and description. The import process validates these fields alongside the overall structure, licensing, and repository integrity.

Why does my imported skill fail structure validation?▼

Imported skill structure validation fails when the SKILL.md frontmatter is missing required fields like name or description, or when repository integrity and licensing attribution checks are not met during the normalization process.