Brief
proov does not detect skills in powershell for the repos i tested.
Info
- CPU: 11th Gen Intel(R) Core(TM) i7-1165G7 @ 2.80GHz
- OS: Microsoft Windows 11 Home 10.0.26200 26200
- Version: v0.6.9/proov-windows-amd64.exe
Reproduce
- clone a skills repo (phuryn/pm-skills for example)
git clone https://github.com/phuryn/pm-skills
- scan the repo with proov repo or folder scan types
# using repo
.\proov-windows-amd64.exe repo path\to\pm-skills\
# using folder
.\proov-windows-amd64.exe folder path\to\pm-skills\
- Proov outputs the following. the path resolution seems correct, but includes the prefix "\\?\".
Found 0 artifact(s) (0.0s)
──────────────────────────────────────────────────────────
proov · AI Execution Inventory
Scanned: \\?\C:\path\to\pm-skills
──────────────────────────────────────────────────────────
No AI execution artifacts detected.
Next step: Do nothing
Expected Behavior
proov should be detecting these skills and scanning them. the repo i used here contains many SKILL.md files, though some are buried in subdirectories.
Assessment
i think it's unlikely subdirectories are the issue; it probably has something to do with the "\\?\" prefix. i tried running this against a non-existent path to verify whether the path is invalid:
PS C:\path\to\executable> .\proov-windows-amd64.exe repo this/doesnt/exist
Error: path not found: this/doesnt/exist
as you can tell, the system responds differently for a truly non-existent path. this is a windows-specific bug in how the paths are canonicalized and resolved.
Brief
proov does not detect skills in powershell for the repos i tested.
Info
Reproduce
Expected Behavior
proov should be detecting these skills and scanning them. the repo i used here contains many SKILL.md files, though some are buried in subdirectories.
Assessment
i think it's unlikely subdirectories are the issue; it probably has something to do with the "\\?\" prefix. i tried running this against a non-existent path to verify whether the path is invalid:
as you can tell, the system responds differently for a truly non-existent path. this is a windows-specific bug in how the paths are canonicalized and resolved.