Description

Plugins can declare skill directories in their manifest ("skills": ["./skills"]), but the plugin loader never reads this field. Skills bundled with plugins are silently ignored. The extension's tools and hooks load fine, but the skill that tells the agent when and how to use them never appears in the session.

Steps to Reproduce

1. Create a plugin with a "skills" entry in the omp manifest and a valid SKILL.md in the declared directory
2. Install and enable the plugin
3. Start an omp session
4. The plugin's skill does not appear in the agent's available skills

Expected Behavior

Plugin-declared skills should be discovered and loaded into the session, just like tools, hooks, commands, and extensions are.

Error Output

No error. The skill is silently ignored. The only sign is that skill-based triggers don't activate the expected workflow.

Platform

macOS

omp version

13.14.2

Bun version

1.3.10

Provider

Not provider-specific

Area

Extensions / Plugins

Additional context

resolvePluginPaths() in loader.ts only accepts "tools" | "hooks" | "commands" | "extensions", not "skills". No capability provider exists to scan plugin skill directories. emitResourcesDiscover in runner.ts appears to be the intended mechanism but is never called. A possible fix: add "skills" to the manifest type, widen the key union, and register a capability provider following the claude-plugins.ts pattern.