probe-shadow-beta

Compare API.md contents between two skills to detect cross-skill resource shadowing.

2|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/agent-ecosystem/agent-skill-implementation --skill probe-shadow-beta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: probe-shadow-beta
Source: https://github.com/agent-ecosystem/agent-skill-implementation/tree/main/benchmark-skills/probe-shadow-beta
Command: npx skills add https://github.com/agent-ecosystem/agent-skill-implementation --skill probe-shadow-beta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps validate how platforms distinguish between similarly named reference resources across skills by providing two versions of API content and a tested prompt.

Core Features & Use Cases

  • Read the references/API.md to reveal the canary phrase and content differences between the probe-shadow-alpha and probe-shadow-beta skills.
  • Detect which canary phrase is present to identify the version loaded (beta or alpha) and report observed resource paths.
  • If both skills are active, report whether you can access the other skill's API.md content to verify cross-skill isolation.

Quick Start

When activated, read references/API.md and report its contents along with the detected canary phrase.

Frequently Asked Questions about probe-shadow-beta

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

FAQPage Schema
How do I detect cross-skill resource shadowing in a multi-skill environment?

Detect cross-skill resource shadowing by comparing the API.md contents between probe-shadow-beta and probe-shadow-alpha, verifying correct resource isolation and content resolution when both skills are loaded.

How does API.md content comparison work for resource isolation verification?

API.md content comparison works by reading the references/API.md file to reveal a specific canary phrase, which identifies the loaded version and reports observed resource paths to verify isolation.

Can I verify cross-skill isolation when both probe-shadow-alpha and beta are active?

Yes, when both skills are active, you can verify cross-skill isolation by checking whether you can access the other skill's API.md content and reporting the detected canary phrase.

What do I need to compare API.md contents for resource shadowing detection?

You need the references/API.md file to exist for both skills and the platform must expose the API.md content to the agent during activation to perform resource shadowing detection.

What are the limitations of detecting cross-skill resource shadowing with API.md?

Detection is limited to environments where the platform exposes API.md content during activation; without both skills' references/API.md files present, resource isolation cannot be verified.

What is the best way to identify which skill version is loaded using canary phrases?

Read the references/API.md file and detect which canary phrase is present to identify the loaded version, either beta or alpha, and report the observed resource paths for validation.