check-skill-registration

Verify built-in skills registered in managed sets within src/workspace.rs.

14|3|Updated Feb 8, 2026

Search Tags:#code quality #verification #skills #rust #workspace management #registration

Ready to run

npx skills add https://github.com/jganoff/wsp --skill check-skill-registration

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: check-skill-registration
Source: https://github.com/jganoff/wsp/tree/main/.claude/skills/check-skill-registration
Command: npx skills add https://github.com/jganoff/wsp --skill check-skill-registration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents errors in workspace management commands like wsp rm and wsp rename by ensuring that all built-in skills are correctly registered within the system's managed sets.

Core Features & Use Cases

Verification: Compares skills installed by install_skill() against the managed sets in check_claude_dir().
Error Detection: Identifies missing registrations for skills.
Use Case: After adding a new built-in skill, run this to confirm it's correctly accounted for, preventing potential issues with workspace cleanup.

Quick Start

Run the check-skill-registration skill to verify all built-in skills are registered.

Frequently Asked Questions about check-skill-registration

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

FAQPage Schema

How do I verify built-in skills are registered in Rust workspace management?▼

Verify built-in skills registration by comparing skills installed via `install_skill()` against managed sets in `check_claude_dir()`. This ensures workspace management commands like `wsp rm` and `wsp rename` do not incorrectly flag built-in skills as user-generated content.

Why does `wsp rm` incorrectly flag built-in skills as user-generated content?▼

Built-in skills are flagged as user-generated content when they are not registered within the `managed` and `managed_dirs` sets in `check_claude_dir()`. Extracting skill names from `install_skill()` calls and comparing them confirms proper registration and prevents these errors.

What is the best way to check for missing skill registrations in a Rust workspace?▼

The best way to check for missing registrations is to extract skill names from `install_skill()` calls and compare them against the `managed` and `managed_dirs` sets. This also confirms the parent `skills/` directory exists in `managed_dirs`.

When do I need to run a skill registration verification check?▼

Run a skill registration verification check after adding a new built-in skill. This confirms the new skill is correctly accounted for in the managed sets, preventing potential issues during workspace cleanup operations.

Does workspace management require the `skills/` directory to be in `managed_dirs`?▼

Workspace management requires the parent `skills/` directory to be registered in `managed_dirs`. Confirming its existence ensures the system correctly tracks built-in skills and prevents incorrect flags during workspace cleanup.

Can I detect missing built-in skills in `check_claude_dir()` managed sets?▼

You can detect missing built-in skills by comparing the extracted names from `install_skill()` calls against the `managed` and `managed_dirs` sets in `check_claude_dir()`. This identifies any missing registrations for skills.