Path-triggered skills (paths:) never fire because paths are dropped when loading skills

Open
#748 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
python

Research direction

Start in app_conversation/skill_loader.py and inspect SkillInfo and _convert_skill_info_to_skill(), then check the referenced SDK issue, OpenHands/software-agent-sdk#5723, for the API change this depends on. The issue describes adding paths and constructing a PathTrigger; done means a skill with a matching paths: rule fires when editing a matching file. Reproduce with the provided app/repositories/payment_repository.py scenario.

Written by the indexing model from the issue text.

Description

What happens

A skill with paths: (a path-triggered rule) never fires in OpenHands Enterprise. The agent can edit a matching file and the rule is not loaded. It just behaves like an ordinary on-demand skill.

Live test (0.76.0, enterprise 1.68.1)

  1. A repo has .agents/skills/storage-note/SKILL.md with paths: [app/repositories/**] and the instruction "add # path-rule-A-applied as the first line of any file you edit."
  2. Start a conversation on that repo and ask for a change to app/repositories/payment_repository.py.
  3. The skill is loaded (the server log lists it), but the file is edited without the marker. The rule never fired.

Why

  • The agent server's skills API has no paths field (OpenHands/software-agent-sdk#5723).
  • OHE's own SkillInfo in app_conversation/skill_loader.py has no paths either, and _convert_skill_info_to_skill() only builds keyword or task triggers.

Suggested fix

After the SDK change, add paths to SkillInfo and build a PathTrigger from it in _convert_skill_info_to_skill().

Dominant language
Python
Stars
9
Forks
17
Avg merge
1d 7h
Merged PRs (30d)
396

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from OpenHands/enterprise

All issues in OpenHands/enterprise

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.