Skip to content

Plugin skills fail to load: plugin.json nested inside plugin/ subdirectory instead of repo root #11

@mjansen401

Description

@mjansen401

Bug Report: han@testdouble-skills-internal Skills Not Loading

Summary

The han plugin installs and enables successfully, but none of its skills (/investigate, /research, /code-review, etc.) are discoverable or invocable. Claude Code's /reload-plugins confirms the problem: 17 plugins · 0 skills · 20 agents — agents load correctly, skills load as zero.

Root Cause

The plugin's plugin.json manifest is nested one directory too deep.

han's current structure:

<package-root>/
  plugin/
    .claude-plugin/
      plugin.json   ← Claude Code cannot find this
    skills/
      investigate/SKILL.md
      research/SKILL.md
      ...

Expected structure (matches working plugins, e.g. cheers-for-peers):

<package-root>/
  .claude-plugin/
    plugin.json   ← Claude Code looks here
  skills/
    investigate/SKILL.md
    research/SKILL.md
    ...

Evidence

  • cheers-for-peers plugin (working): .claude-plugin/plugin.json at package root; skills appear in session.
  • han plugin (broken): .claude-plugin/plugin.json inside plugin/ subdirectory; 0 skills registered.
  • All cached han versions (1fc79064e6a8, 659fb37adf0c, 87047035744b, 2a39f8177bba) have the same nested structure, so this has never worked.
  • The plugin.json itself is correct ("skills": "./skills"); the issue is purely the location of the file.

Fix

Move .claude-plugin/plugin.json (and the skills/ directory) from plugin/ up to the package root, or update the build/publish process that creates the extra plugin/ nesting layer.

Environment

  • Claude Code version: tested 2026-05-21
  • Plugin version: 2a39f8177bba (latest installed)
  • OS: macOS Darwin 25.4.0

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions