scope-validation

Validates plugin content placement against marketplace registry scope declarations.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/karimStekelenburg/k3m-marketplace --skill scope-validation-karimstekelenburg
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scope-validation
Source: https://github.com/karimStekelenburg/k3m-marketplace/tree/main/.claude/skills/scope-validation
Command: npx skills add https://github.com/karimStekelenburg/k3m-marketplace --skill scope-validation-karimstekelenburg

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

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.

Frequently Asked Questions about scope-validation

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

FAQPage Schema
How do I check if a skill belongs in a plugin?▼

Run scope validation before adding the skill. It reads the marketplace registry.yaml, extracts the content's domain and keywords, then matches them against each plugin's scope.keywords and scope.owns entries to identify the correct owner.

What is the registry.yaml scope format for plugins?▼

Each plugin entry declares scope.keywords for fast matching, scope.owns listing responsibilities it handles, and scope.does_not_own listing exclusions with redirects to the owning plugin. The full format is documented in the references/registry-format.md file.

Does does_not_own override keyword matching?▼

Yes, the does_not_own field is authoritative. If plugin A declares it does not own something that belongs to plugin B, the content is assigned to B regardless of how many keywords overlap with plugin A.

What happens when content fits no registered plugin?▼

The skill flags this as a scope gap in the marketplace coverage. It suggests registering a new plugin using the /register command and proposes a scope declaration for the new plugin.

When should scope validation be triggered?▼

Trigger it whenever adding a new skill, command, agent, or hook to a plugin, moving content between plugins, modifying an instruction's scope, or when explicitly asked whether something belongs in a particular plugin.