scoped-skill

Scoped scanning limits skill discovery to intended files and directories, ensuring only relevant resources are loaded. It validates discovery behavior by verifying SKILL.md frontmatter and recognizing optional directories like scripts and references.

You can test partial-scoped versus full-scan workflows by running the provided processor script in a controlled fixture environment. This compares discovery behavior across skills and validates how resources are loaded under different scanning scopes.

Yes, scoped scanning recognizes optional directories such as scripts and references during the discovery pipeline. It detects and leverages these components to exercise resource awareness and validate the loading behavior.

Skill discovery may scan unintended files if scoped scanning is not properly configured. Using a controlled testing fixture helps diagnose discovery scope issues by comparing partial-scoped versus full-scan workflows to isolate the problem.

Yes, you can use this fixture in automated tests to validate the presence of a valid SKILL.md frontmatter with name and description. It provides a controlled environment to verify discovery pipeline behavior and exercise component recognition.

The best way to debug agent skill discovery scope issues is to use a controlled fixture that compares partial-scoped versus full-scan workflows. This helps diagnose discovery behavior and validates that only intended files are scanned during loading.