[Bug]: add-skill plugin/skill is broken?

[rbren]

Operating System

macOS

Installation Method

npm (npx @openhands/agent-canvas or npm install -g @openhands/agent-canvas)

Agent Canvas Version

1.2.0

Bug Description

add-skill skill was triggered, but the agent couldn't find the script that it's told to use, fetch_skill.py

Steps to Reproduce

Tell the agent to add a skill

Actual Behavior

Agent flails around

Expected Behavior

Agent knows exactly what to do

Relevant Logs

Screenshots

No response

Additional Context

No response

[rbren]

Update: the agent added it to the current workspace instead of making it global 🤦

[VascoSch92]

I see the problem. I think you would like to have the possibility to decide if the skill is global (in .agents) or local (in workspace).

I think this can be done into the skill saying the agent to understand and in the case ask if the skill is global or local.

I'm moving the issue into the extension repo.

[NataliaBorova]

Diagnosis

The issue is that the skill content uses <this-skill-path>/scripts/fetch_skill.py as a placeholder, but the agent does not resolve this placeholder automatically.

Root cause: The skill file uses <this-skill-path> which is not a valid variable that gets resolved by the agent runtime.

Workaround: The skill should use the absolute path or a relative path from the skill directory. The skill metadata already provides resources.skill_root pointing to the correct location.

Suggested fix: Replace <this-skill-path> with the actual skill path in the SKILL.md file:

/home/openhands/.openhands/cache/skills/public-skills/skills/add-skill/scripts/fetch_skill.py

Or use a relative path since the skill location is known.

[VascoSch92]

Hey @NataliaBorova

could you open a fix for that? And also test it to show that it works? :-)

This would be great.