You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
A "no skills found" error occurs during gh skill update when using hidden directories. #13542
gh skill update --all fails to update a skill that was installed from a curated path (.curated/) in openai/skills. The update command cannot locate the skill in the source repository, even though it was successfully installed earlier.
Affected version
$ gh version
gh version 2.93.0 (2026-05-27)
https://github.com/cli/cli/releases/tag/v2.93.0
Steps to reproduce the behavior
root@2a75804eaf51:/# gh skill install openai/skills skills/.curated/gh-address-comments --agent warp --scope user --allow-hidden-dirs
Using ref main (b0401f07)
! Skills are not verified by GitHub and may contain prompt injections, hidden instructions, or malicious scripts. Always review skill contents before use.
✓ Installed .curated/gh-address-comments (from openai/skills@main) in root/.agents/skills
.curated/gh-address-comments/
(could not read directory)
! Skills may contain prompt injections or malicious scripts.
Review installed content before use:
gh skill preview openai/skills .curated/gh-address-comments@b0401f07213a66414d84a65cb50c1d226f99485a --allow-hidden-dirs
root@2a75804eaf51:/# gh skill update --all
! Skipping gh-address-comments: no skills found in openai/skills
Expected skills in skills/*/SKILL.md, skills/{scope}/*/SKILL.md,
{prefix}/skills/*/SKILL.md, {prefix}/skills/{scope}/*/SKILL.md,
*/SKILL.md, or plugins/*/skills/*/SKILL.md
This repository may be a curated list rather than a skills publisher
All skills are up to date.
root@2a75804eaf51:/# find /root/.agents/ -ls
1066233 4 drwxr-xr-x 3 root root 4096 May 28 16:01 /root/.agents/
1066245 4 -rw-r--r-- 1 root root 426 May 28 16:01 /root/.agents/.skill-lock.json
1066234 4 drwxr-xr-x 3 root root 4096 May 28 16:01 /root/.agents/skills
1066235 4 drwxr-xr-x 5 root root 4096 May 28 16:01 /root/.agents/skills/gh-address-comments
1066236 12 -rw-r--r-- 1 root root 11357 May 28 16:01 /root/.agents/skills/gh-address-comments/LICENSE.txt
1066237 4 -rw-r--r-- 1 root root 1476 May 28 16:01 /root/.agents/skills/gh-address-comments/SKILL.md
1066240 4 drwxr-xr-x 2 root root 4096 May 28 16:01 /root/.agents/skills/gh-address-comments/assets
1066242 4 -rw-r--r-- 1 root root 1838 May 28 16:01 /root/.agents/skills/gh-address-comments/assets/github.png
1066241 4 -rw-r--r-- 1 root root 853 May 28 16:01 /root/.agents/skills/gh-address-comments/assets/github-small.svg
1066243 4 drwxr-xr-x 2 root root 4096 May 28 16:01 /root/.agents/skills/gh-address-comments/scripts
1066244 8 -rw-r--r-- 1 root root 6537 May 28 16:01 /root/.agents/skills/gh-address-comments/scripts/fetch_comments.py
1066238 4 drwxr-xr-x 2 root root 4096 May 28 16:01 /root/.agents/skills/gh-address-comments/agents
1066239 4 -rw-r--r-- 1 root root 303 May 28 16:01 /root/.agents/skills/gh-address-comments/agents/openai.yaml
root@2a75804eaf51:/# cat /root/.agents/.skill-lock.json
{
"version": 3,
"skills": {
".curated/gh-address-comments": {
"source": "openai/skills",
"sourceType": "github",
"sourceUrl": "https://github.com/openai/skills.git",
"skillPath": "skills/.curated/gh-address-comments/SKILL.md",
"skillFolderHash": "042316bece4a9f832145dcff7d5506e99fe3ecf1",
"installedAt": "2026-05-28T16:01:03Z",
"updatedAt": "2026-05-28T16:01:03Z"
}
}
}
Hey @ruzickap, thanks for reporting this! I tossed this to Copilot and it came back with:
The update command calls discovery.DiscoverSkills() which explicitly filters out hidden-directory skills (like those under .curated/), even though install with --allow-hidden-dirs correctly installs them. The update path needs to either respect the --allow-hidden-dirs flag or detect from the lock file that the skill was installed from a hidden directory and adjust discovery accordingly.
I don't know enough about the directory layout for skills to know if hidden directories are permitted but I'm assuming they are since that exists in openai/skills.
Hey @SamMorrowDrums@niik — implemented the "sensible order" approach in #13554 (review notes inline explain the design choices, including why no new flag was needed and the DiscoverSkillByPath fallback). The PR bot flagged the issue for missing help wanted; could you (or @cli/code-reviewers) add the label so review can proceed?
Update: closing #13554 myself to respect the contribution process — I should have waited for triage before opening the PR. Happy to reopen the same change if help wanted lands, or to step back entirely if you'd prefer another contributor on it.
Activity
niik commentedon May 29, 2026
Hey @ruzickap, thanks for reporting this! I tossed this to Copilot and it came back with:
The update command calls discovery.DiscoverSkills() which explicitly filters out hidden-directory skills (like those under .curated/), even though install with --allow-hidden-dirs correctly installs them. The update path needs to either respect the --allow-hidden-dirs flag or detect from the lock file that the skill was installed from a hidden directory and adjust discovery accordingly.
I don't know enough about the directory layout for skills to know if hidden directories are permitted but I'm assuming they are since that exists in openai/skills.
I'm gonna tentatively label this as a bug. @SamMorrowDrums @tommaso-moro would you concur?
SamMorrowDrums commentedon May 30, 2026
Yea, thanks for the report. I think it makes sense to allow the update to check in a sensible order for locations where skill may live in repo!
takumi12311123 commentedon Jun 1, 2026
Hey @SamMorrowDrums @niik — implemented the "sensible order" approach in #13554 (review notes inline explain the design choices, including why no new flag was needed and the
DiscoverSkillByPathfallback). The PR bot flagged the issue for missinghelp wanted; could you (or @cli/code-reviewers) add the label so review can proceed?Update: closing #13554 myself to respect the contribution process — I should have waited for triage before opening the PR. Happy to reopen the same change if
help wantedlands, or to step back entirely if you'd prefer another contributor on it.beanscg commentedon Jun 9, 2026