probe-linked-resources

Detects whether platforms pre-fetch files linked in SKILL.md during activation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill helps determine how platforms handle linked resources and relative paths within a skill's body, ensuring consistent loading behavior during activation.

Core Features & Use Cases

  • Evaluates whether platforms pre-fetch files linked in SKILL.md during activation.
  • Validates accurate resolution of relative paths and distinguishes between markdown-linked references and plain-text mentions.
  • Useful for platform QA, compatibility testing, and debugging of loading behavior across Skill implementations.

Quick Start

Activate the skill and report which linked files were pre-fetched and how each relative path was resolved.

Frequently Asked Questions about probe-linked-resources

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

FAQPage Schema
How do I test if a platform pre-fetches markdown linked files during skill activation?

To test platform pre-fetching, activate a skill containing markdown links in the SKILL.md body and report which linked files the platform pre-fetched. This validates whether linked references load correctly during the activation process.

Why does a relative path fail to resolve correctly in my SKILL.md file?

Relative path resolution fails when paths are not evaluated against the skill's root directory. Testing relative path resolution verifies that paths resolve correctly against the skill's root and distinguishes between markdown-linked references and plain-text path mentions.

What is the difference between markdown link references and plain-text path mentions for platform loading?

Markdown link references trigger platform pre-fetching during activation, while plain-text path mentions do not. Validating this distinction ensures unlinked path mentions do not trigger pre-fetching and confirms accurate reference resolution.

Can I use this skill for platform QA and compatibility testing of link loading behavior?

Yes, you can use this skill for platform QA and compatibility testing of loading behavior across Skill implementations. It evaluates pre-fetching and relative path resolution to debug and ensure consistent platform loading behavior.

What are the limitations of testing unlinked path mentions for pre-fetching behavior?

Testing unlinked path mentions verifies they do not trigger pre-fetching, but limitations arise if platforms handle plain-text path parsing differently. The skill validates that only markdown-linked references load correctly while unlinked mentions remain inert.