Repository navigation
Skills discovery is single-level only — category folders are unsupported and skipped silently / 技能发现只扫描一层:分类目录不被支持,且静默失败 #11898
Replies: 2 comments
|
Cross-referencing two adjacent reports, because these look like the same failure at different layers. #9608 established that one unwatchable root sets This report is the discovery-layer instance of that family — and it is the one layer with no diagnostic at all:
The asymmetry matters for the fix. #9608's remedy is to degrade per root instead of invalidating the union; that presumes each root was at least attempted. A directory that was never a root has no such hook, so the only way to make this case visible is at the shape test itself — one warning naming the path that contained a nested That is why item 1 in the proposal is the cheapest of the three: it does not require |
|
Updating my own thread: I built the plugin described at the end of the original post and released it -
It is a downstream workaround, not a change in |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Summary
@deepseek-ai/dsh-skill-filesystemdiscovers skills from a fixed set of roots, and each root is scanned exactly one level deep. Two consequences follow, and together they make a categorized skill library unusable without per-skill enumeration:SKILL.mdfiles) contributes nothing — and nothing is logged.roots()hard-codes<project>/.dsh/skillsand<project>/.agents/skills;customSkillDirsis host/preset level only. There is no project-scoped way to add roots, so "this project sees category A only" is not expressible at all.1. Reproduction
Expected: three skills. Actual: zero. No warning, no log line.
Pointing
customSkillDirsat/path/to/library/category-aand/path/to/library/category-bdoes work — but that is enumeration, and it applies to the whole host or preset.2. Where it happens
discoverRoot():roots():The project layer is two fixed paths.
customSkillDirsis provider-level. So neither project scope nor category granularity is available, and no combination of the existing knobs produces either.3. What cannot be expressed today
<project>/.dsh/skills: O(n) per project, re-done whenever the library grows, and it conflates "which source" with "which skill".SkillCatalogSnapshotis{ skills, complete }with no reason field, so even a consumer that wanted to explain the gap cannot name the root.4. Proposal
SKILL.mdis skipped, e.g.skill-filesystem: <root>/<dir> contains SKILL.md at depth 2 but is not a skill directory; ignored. Behavior unchanged; makes the failure visible.maxDepthconfig (default1).2makes<category>/<skill>/SKILL.mddiscoverable directly, with no change for existing deployments.<project>/.dsh/skills.yml:customSkillDirs(/path/to/library/*).5. Compatibility notes
maxDepthdefaulting to1preserves current behavior exactly.6. Related threads
<category>/<skill>/SKILL.mdlayout → not discovered, regardless of symlinks")whenToUsenever reaches the modelcompletecarries no reasonThe common thread across all four is that the skill surface fails silently, at three different layers: discovery (this report), observation (
#9608), and rendering (#9375).中文
摘要
dsh-skill-filesystem从一组固定根发现技能,每个根只扫一层。由此产生两个后果,叠加起来使「按分类组织的技能库」在没有逐个枚举的情况下不可用:SKILL.md),整个根不贡献任何技能,且没有任何日志。roots()把<project>/.dsh/skills和<project>/.agents/skills写死;customSkillDirs只有宿主/预设级。不存在项目级追加根的机制,因此「这个项目只看分类 A」无法表达。复现
customSkillDirs: [/path/to/library]→ 期望 3 个技能,实际 0 个,无警告、无日志。把
customSkillDirs指到每个分类目录确实可行,但那是枚举,而且作用于整个宿主或预设。代码位置
discoverRoot()中,目录项要求<child>/SKILL.md;分类目录这一层没有该文件,locator为undefined,被一句continue静默跳过。parseSkillFile返回undefined时同样静默跳过。roots()中,项目层是两个固定路径;customSkillDirs是 provider 级。两个旋钮的任意组合都无法产生「项目级 + 分类粒度」。当前无法表达的三件事
<project>/.dsh/skills里逐技能建链接——每个项目 O(n),库一增长就要重做,而且把「来源」和「技能」两件事混成一件。SkillCatalogSnapshot只有{ skills, complete },没有 reason 字段,消费方即使想解释也说不清是哪个根。建议
SKILL.md时每个根输出一条 warning,例如skill-filesystem: <root>/<dir> contains SKILL.md at depth 2 but is not a skill directory; ignored。行为不变,只让失败可见。maxDepth配置(默认1)。设为2即可直接发现<category>/<skill>/SKILL.md,对现有部署无影响。<project>/.dsh/skills.yml:customSkillDirs支持通配符(/path/to/library/*)。兼容性
maxDepth默认1,现有行为完全不变。相关讨论
whenToUse从不进入模型视野complete不带原因四条讨论的共同点:技能面在发现层(本条)、观测层(#9608)、渲染层(#9375)三个不同层次上都是静默失败。
All reactions