One-click install
npx skills add https://github.com/XWIlluDelu/agent-share --skill skill-manager-xwilludelu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-manager
Source: https://github.com/XWIlluDelu/agent-share/tree/main/lib/skill-manager
Command: npx skills add https://github.com/XWIlluDelu/agent-share --skill skill-manager-xwilludelu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of keeping the local .agent-share skill library consistent, up to date, and correctly registered when skills and packs evolve over time.

Core Features & Use Cases

  • Skill library maintenance workflows: sync upstream skill sources, add/update/delete/rename shared skills, modify local normalization, and change pack membership.
  • Manifest-driven governance: uses manifest.yaml as the registry of provenance, pack membership, and normalization intent so changes remain traceable and auditable.
  • Always-on materialization and cleanup: maintains skills/ materialized symlinks for pack: always-on and removes stale generated debris during maintenance operations.
  • Agent fragment hygiene: supports editing agents-fragments/AGENT-*.md to keep reusable project instruction fragments correct while ensuring these fragments are not treated as skills.
  • Consistency auditing: runs an audit checklist that validates manifest parsing, name uniqueness, presence of required SKILL.md files, correct symlink targets, and absence of stale/duplicate registry artifacts.

Quick Start

Use the skill-manager when you are modifying .agent-share itself, shared skills, packs, fragments, or the shared skill registry, and run the maintenance operation you requested.

Frequently Asked Questions about skill-manager

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

FAQPage Schema
How do I sync upstream skill sources in a local agent-share library?

To sync upstream skill sources in an agent-share library, the skill-manager updates local canonical lib copies and manifest.yaml provenance entries, ensuring the upstream changes are correctly registered and audited for consistency.

What is a manifest.yaml provenance registry for shared skills?

A manifest.yaml provenance registry tracks the origin, pack membership, and normalization intent of shared skills, providing a traceable and auditable record that keeps the local library consistent during updates.

How do I materialize always-on pack symlinks into the skills directory?

To materialize always-on pack symlinks, the skill-manager creates symlinks in the skills/ directory pointing to canonical lib/<skill> copies, while clearing stale generated debris to maintain a clean state.

Can I use skill-manager to rename or delete shared skills without breaking consistency?

Yes, you can safely rename or delete shared skills because skill-manager runs a consistency audit validating name uniqueness, manifest parsing, and symlink targets to prevent broken artifacts.

Why does my skill library consistency audit report stale duplicate registry artifacts?

A consistency audit reports stale duplicate artifacts when maintenance operations leave behind broken symlinks or outdated registry entries, requiring cleanup to enforce operational separation and an audit-verified end state.

Do I need to manually edit agents-fragments to maintain reusable project instructions?

You need to edit agents-fragments/AGENT-*.md files to maintain reusable project instructions, while ensuring the skill-manager does not mistakenly treat these fragments as skills during the consistency audit.