It's somewhat confusing that skills are automatically adopted from other harn...
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
It's somewhat confusing that skills are automatically adopted from other harnesses (I see "on device" skills that came from a local Codex install.) At first blush, it *appears* that disabling those skills causes same-name skills installed from a plugin inside Copilot to become inaccessible, but I haven't yet found logging to confirm or disprove that.
---
| Field | Value |
| --- | --- |
| App version | 1.1.8 |
| OS | macOS 26.5.2 |
| Theme | GitHub |
| Path | /recent |
| Tenure | Day 1 |
Contributor guide
Research direction
Start by reproducing the skill list on the /recent path in app version 1.1.8 on macOS, comparing skills adopted from another harness with same-name skills from a Copilot plugin. Check whether disabling one makes the other inaccessible and whether the app provides logging; done means the behavior is explained and the confusing state or missing diagnostic is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, macos
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100