manage-skills

Find, add, update, and synchronize agent skills across repositories and shared commons.

9|1|Updated Jun 6, 2025

Search Tags:#automation #workflow #repository #governance #skill #management

Ready to run

npx skills add https://github.com/JeremyKuhne/touki --skill manage-skills-jeremykuhne

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: manage-skills
Source: https://github.com/JeremyKuhne/touki/tree/main/.agents/skills/manage-skills
Command: npx skills add https://github.com/JeremyKuhne/touki --skill manage-skills-jeremykuhne

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Finds, standardizes, and coordinates the creation, updating, and sharing of agent skills across this repository and its governance surfaces (commons and public catalogs). It provides a lifecycle model to ensure consistency, provenance, and safe synchronization between local overlays and upstream cores.

Core Features & Use Cases

Discover, add, update, and synchronize agent skills within a repo, including overlay handling and governance rules.
Perform tiered searches (local, commons when available, and public catalogs) to avoid duplicating work and to maintain provenance.
Validate changes with catalog integration and ensure frontmatter consistency and alignment with the repository's catalog inventory.

Quick Start

Run the manage-skills workflow to locate an existing skill and decide whether to build, vendor, or update it.

Frequently Asked Questions about manage-skills

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

FAQPage Schema

How do I manage agent skills across a repository and shared commons?▼

To manage agent skills across a repository, you can discover, add, update, and synchronize them using a lifecycle model that ensures consistency and safe synchronization between local overlays and upstream cores.

What is the best way to avoid duplicating skill work in a repository?▼

The best way to avoid duplicating skill work is to perform tiered searches across local repositories, shared commons, and public catalogs to locate existing skills before building new ones.

How do I track provenance for repository skills?▼

You track provenance for repository skills by applying frontmatter tracking, category alignment, and catalog integration rules to validate changes and ensure consistency within the governance surfaces.

When should I vendor a skill instead of publishing to the commons?▼

You decide whether to vendor a skill or publish it to the commons by running a workflow that evaluates existing local and upstream skills, applying governance rules to determine the correct synchronization path.

How do I handle local overlays for upstream skill cores?▼

Handling local overlays for upstream skill cores requires applying a synchronization lifecycle model that safely coordinates updates and maintains consistency between your local repository and shared catalogs.

Can I validate skill frontmatter against a repository catalog inventory?▼

Yes, you can validate skill frontmatter against a repository catalog inventory using validation tooling that ensures category alignment and enforces catalog integration rules for safe governance.