probe-cross-scope

Test cross-scope dependency resolution by installing a project-level skill that attempts to invoke a user-level skill, allowing you to observe platform behavior and validate scope awareness during the interaction.

When a project-level skill invokes a missing user-level skill, the platform exercises robust failure handling, providing scope reporting and invocation tracing to observe the unavailable dependency behavior.

Yes, a project-level skill can invoke a user-level skill to test cross-scope behavior, validating whether the platform correctly exposes scope information and handles the dependency resolution.

Scope reporting works by exposing whether a skill operates at the project-level or user-level during interactions, ensuring the platform accurately traces invocations and reports scope awareness.

Cross-scope skill invocation fails when the user-level skill is not installed because the platform's dependency resolution cannot locate the referenced skill, triggering failure-mode observation and robust error handling.

You need platform-scoped installation awareness to test cross-scope skill behavior, ensuring the environment correctly distinguishes between project-level and user-level scopes during invocation tracing and failure handling.