skill-reachabilitylisted

# Hidden and plugin skill reachability ## Problem An agent reports a skill as missing or non-existent. The skill is installed, current, and works when the operator types `/name`. The agent's report is wrong, and it is wrong in a way that costs the user a working tool and costs the agent credibility. The failure is not one bug. **Three independent mechanisms produce the identical symptom**, and checking only the first leaves two live. ## Context / Trigger conditions - The Skill tool returns a refusal for a name the user has just used successfully. - A skill is named in `CLAUDE.md`, a README, or a handoff, and is absent from the available-skills listing the agent was given. - A recursive search under `~/.claude/plugins` returns nothing for a plugin skill. - The user says "it's a plugin skill" / "it's a Pocock skill" after the agent said it did not exist. - A skill was reachable in one project and is not in another. ## Root causes, all three ### 1. `disable-model-invocation: true` The skill's own frontmatter. It removes the skill from auto-discovery **and makes the Skill tool refuse it**. Only the operator can fire it, by typing `/name`. This is the common case: in one measured install, **20 of 35** plugin skills carried it. ```sh grep -c 'disable-model-invocation: true' ~/.claude/skills/<name>/SKILL.md ``` `1` means operator-only. `0` means model-invocable. ### 2. Plugin skills sit seven levels deep Plugin skills are **not** under `~/.claude/skills/`. They live