Skip to content

plugins: make plugin-declared skills discoverable by the skill tool #514

Closed

Description

@Ashwinhegde19

Summary

Plugin manifests can declare skills, but those skills are not currently merged into Zero's skill discovery. That means an installed plugin can ship a skills: entry in plugin.json, yet the existing skill tool/listing path will not see or load it.

The docs already call this out as a current limitation:

  • AGENTS.md section 3: plugin-declared skills are not yet merged into the loader, so a skills: entry inside a plugin's plugin.json is not visible to the skill tool today.
  • AGENTS.md section 6 repeats the same limitation for plugin-managed skills.

Proposed behavior

Installed, enabled plugins that declare skills in plugin.json should expose those skills through the same discovery path used by regular user skills.

For example, a plugin manifest like:

{
  "id": "github-pr-review",
  "skills": [
    { "path": "./skills/review-checklist/SKILL.md" }
  ]
}

should make review-checklist available to the skill listing/loading flow, using the existing SKILL.md metadata rules.

Suggested scope

  • Merge plugin-declared skills into the skill loader/discovery result.
  • Resolve relative skill paths against the plugin directory.
  • Ignore disabled plugins.
  • Preserve existing duplicate-name behavior or document/handle precedence explicitly.
  • Add tests for plugin skill discovery and relative-path resolution.

Why

This closes a documented feature gap and makes plugins more useful as self-contained capability bundles. Plugin authors can ship tools, hooks, and skills together instead of asking users to install skills separately.

Non-goals

  • Full in-UI plugin manager.
  • Marketplace browsing.
  • Project-scoped skill directories.
  • Redesigning the plugin enable/disable model.

Activity

  1. Vasanthdev2004 commented on Jul 26, 2026

    @Vasanthdev2004
    Collaborator

    This is resolved on current main, so I am closing it. Thanks for the report.

    Plugin-declared skills are now discovered through the same path as user skills: activation exposes each plugin's skill directory as a loader root (resolved against the plugin dir, so manifest-relative paths work), and those roots are merged with the primary skills dir and ~/.agents/skills via skills.LoadFromRoots before the skill tool is registered. Duplicate names are recorded rather than crashing, and disabled plugins are excluded.

    I verified this by running the tests rather than just reading the wiring: TestNewSkillToolSurfacesPluginSkillInList builds the real skill tool over a plugin root, invokes it by skill name, and asserts the plugin skill's body comes back, with a core skill still reachable through the same tool. That plus the sibling multi-root and precedence tests all pass on main.

    If you have a case that still fails, please reopen with the plugin layout and I will take another look.

    Note #566 reported the same defect a day later and is being closed alongside this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions