Repository navigation
fix(app-control): drive misses a plugin control skill at a manifest-declared path #10084
Description
Context
/app-control:drive step 2 looks for a plugin's control skill only in that plugin's skills/*/SKILL.md and commands/**/*.md. A plugin manifest can also point skills or commands at other paths: its commands key replaces the default commands/ scan and can name a source file, and its skills key adds paths (manifest-reference#commands, Component path forms). A listed plugin that ships control-<app> at such a path is neither read nor stopped, so drive falls through to its no-control-skill fallback. The fresh-context verifier found this on PR #9615.
Proposed work
- Have step 2 read the folder's
.claude-plugin/plugin.jsonskillsandcommandskeys and search the paths they name, alongside or in place of the defaults as upstream defines, by pointer to the manifest reference rather than restating it. - Add an eval case or headless check where a listed plugin declares
control-<app>at a non-default path.
Acceptance criteria
- A listed plugin whose manifest points
commandsorskillsat a non-default path that holdscontrol-<app>is found and read from disk, with no Skill-tool call. - Drive's text points at the manifest reference sections and restates no upstream path rule.
References
- PR feat(app-control): find plugin-shipped control skills in /app-control:drive #9615 (drive reads plugin control skills from disk); owner decisions D22 and D26.
plugins/app-control/skills/drive/SKILL.mdstep 2.
Activity
github-actions commentedon Oct 25, 2026
Proposed work class: work-class: scoped
Basis: automated intake triage; the lanes App applied this class.
Size: Small
Complexity: Low
Uncertainty: Known
Flags: none
Blocked by: none
Understood:
/app-control:drivestep 2 searches only the defaultskills/andcommands/paths. It misses acontrol-<app>skill that a plugin manifest declares at another path. The fix is to have step 2 read the manifest'sskillsandcommandskeys and link to the manifest reference. It also adds an eval or headless check for a non-default path. The acceptance criteria are clear. I found no likely duplicates among the open issues.Automated triage, applied by the lanes App.