Path-triggered skills (paths:) never fire because paths are dropped when loading skills
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
- Domain
- ai-infra-agents, backend
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)
- A repo has
.agents/skills/storage-note/SKILL.mdwithpaths: [app/repositories/**]and the instruction "add# path-rule-A-appliedas the first line of any file you edit." - Start a conversation on that repo and ask for a change to
app/repositories/payment_repository.py. - 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
pathsfield (OpenHands/software-agent-sdk#5723). - OHE's own
SkillInfoinapp_conversation/skill_loader.pyhas nopathseither, 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OpenHands/enterprise
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
OpenHands/enterprise#1269 ·
Maintainers usually reply within 1 day
-
type: test
Difficulty 1/5 Under an hour Newbie friendliness 84/100
OpenHands/enterprise#816 ·
Maintainers usually reply within 1 day
-
type: test
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
OpenHands/enterprise#814 ·
Maintainers usually reply within 1 day
-
type: test
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
OpenHands/enterprise#810 ·
Maintainers usually reply within 1 day
-
type: test
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
OpenHands/enterprise#811 ·
Maintainers usually reply within 1 day
All issues in OpenHands/enterprise
Similar issues
-
[Bug]: reme CLI crashes when the running server used a relative config pathPossibly taken @nurlanmnn claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
agentscope-ai/ReMe#770 ·
Maintainers usually reply within 1 day
-
Pi: paused model calls are reported as "not signed in" when the model's provider comes from an extensionPossibly taken @balcsida claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
microsoft/TokenEconomizer#288 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 67/100
sickn33/agentic-awesome-skills#2437 ·
Maintainers usually reply within 1 day
-
site-bug triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ethereum/consensus-specs#5846 ·
Maintainers usually reply within 1 day