What problem does it solve? When maintaining a multi-plugin marketplace, skills, commands, agents, and hooks can easily end up in the wrong plugin, creating organizational debt. This Skill checks new or moved content against each plugin's declared scope so every component lands where it belongs. ## Core Features & Use Cases - Scope-Based Placement Validation: Compares content against each plugin's scope.keywords, scope.owns, and scope.does_not_own entries in the marketplace registry.yaml. - Two-Stage Matching: Uses fast keyword matching first, then semantic judgment against ownership statements, with does_not_own treated as authoritative. - Gap Detection: Flags content that fits no registered plugin and proposes a new plugin registration with a suggested scope declaration. - Use Case: Before adding a new hook-development skill to a plugin, run this validation to confirm the target plugin actually owns hook development rather than marketplace maintenance. ## Quick Start Ask Claude to validate whether the new skill you are about to add belongs in this plugin before creating it.