skill-management

Manage agent skills with npx skills across canonical directories and flat overlays.

2|Updated Apr 2, 2026
One-click install
npx skills add https://github.com/nseng-ai/ns --skill skill-management-nseng-ai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-management
Source: https://github.com/nseng-ai/ns/tree/main/skills/internal/skill-system/skill-management
Command: npx skills add https://github.com/nseng-ai/ns --skill skill-management-nseng-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Managing agent skills across nested canonical directories, flat .agents/skills/ and .claude/skills/ symlink overlays, and skills-lock.json is error-prone; this Skill enforces the correct topology and safe npx skills workflows for adding, editing, renaming, promoting, and removing skills. ## Core Features & Use Cases - First-party skill lifecycle: Add, edit, rename, promote, demote, or remove repo-local skills while preserving the canonical skills/<disposition>/<family>/<identity>/ layout and symlink invariants. - GitHub-sourced vendored skills: Install and update third-party skills as real vendored directories without creating canonical directories or clobbering curated lockfile selections. - Safe validation: Avoids the destructive npx skills check command, relying instead on npx skills list --json, readlink checks, and bounded reference searches. - Use Case: When adding a new internal skill, follow the workflow to bootstrap with npx skills add, replace the bootstrap copy with a symlink to the canonical destination, normalize the lock entry, and verify both overlay links before staging. ## Quick Start Ask the agent to add a new first-party skill at an approved destination using npx skills and wire up the .agents and .claude symlinks.

Frequently Asked Questions about skill-management

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

FAQPage Schema
How do I add a new agent skill to a repository with npx skills?

Run npx skills add with the local canonical path and --agent codex claude-code -y, then replace the bootstrap copy in .agents/skills with a symlink to the canonical destination. Normalize the skills-lock.json source entry and verify both overlay symlinks with readlink.

How do I install a skill from GitHub using npx skills?

Use npx skills add <owner>/<repo> --skill <identity> --agent codex claude-code -y. GitHub-sourced skills remain real vendored directories under .agents/skills and must never be replaced with first-party canonical symlinks.

Why should I avoid running npx skills check?

The check subcommand performs a broad remote refresh rather than read-only validation: it mutates vendored overlays and skills-lock.json, may create .pi/skills/, and can fail due to unrelated upstream skills. Use npx skills list --json and readlink checks instead.

Why is my internal skill missing from npx skills list output?

Skills marked with metadata.internal: true are hidden from plain listings. Rerun the command with the INSTALL_INTERNAL_SKILLS=1 environment variable prefix to list or install internal skills.

How do I rename or move a skill without breaking symlinks?

Use git mv to move the canonical directory to the approved new destination, then recreate the .agents symlink targeting ../../<new-destination> and the .claude symlink targeting ../../.agents/skills/<new-identity>. Update only the affected lock key and search for stale references.