Skills Management · recorded 2026-08-29 · applies to 1 tool(s) ✓ Verified

Problem: Skills not visible after install / document-skills install does nothing —— Trove problem library

Verified 2026-08-29skills not visible after install — skills are directory copies: ls ~/.claude/skills/agent-skills first (expect 24 dirs), fully exit and restart the agent, then check permissions/version.

Quick fix

# One-liner: check the directory -> restart the agent -> look again
ls ~/.claude/skills/agent-skills && echo "--- then fully quit and restart the agent session ---"

You should see 24 directories, each containing SKILL.md.

What you will run into

You finish installing by the tutorial (the /plugin install flow or method B), but the agent does not show the skills; or the document-skills subset installs with no effect. You spent ages installing for nothing.

Why this happens

A skill package is essentially directory copying (no binaries), so "installed but invisible" has basically three causes:

CauseSymptom
Wrong directorySkills live somewhere else; the agent never scans them
Agent not restartedSkills are scanned at startup; running sessions do not refresh
Permission/path issueCopy failed or left a half-finished directory

document-skills is a subset of the same skill set, same root causes (network/permission/version incompatibility are the common failure surfaces, per CSDN install Q&A).

A skill package is "directory equals capability": the agent's skill discovery is a startup-time scan of fixed directories (every subdirectory under ~/.claude/skills/ containing a SKILL.md counts as a skill), not a live refresh while running — that's the root cause behind "installed but invisible".

The full chain is: copy the directory (write to disk) -> agent scans at startup (read from disk) -> the skills list renders (runtime in-memory state).

Any broken layer looks like "invisible": copied to the wrong place = the scanned directory simply doesn't contain it; no restart = the in-memory state is still the old one; permission/half-finished directory = the scan fails to read and skips it.

So the diagnostic order is fixed: ls the target directory first (confirm the write layer), then fully quit and restart (refresh the in-memory state), and only then suspect permission/version — reversed order makes you wrongly conclude "installed for nothing".

Step by step

1. Check the skills directory — Required

ls ~/.claude/skills/agent-skills

Should be 24 directories, each with SKILL.md (the shape after a measured copy).

2. Fully quit and restart the agent session — Required

Skills are scanned at startup; running sessions do not refresh - fully quit (not a new window) and start again.

3. Check permissions and version — Required

ls -ld ~/.claude/skills/agent-skills && cat ~ | head -1

Confirm the target directory is writable; confirm the tag matches the recorded version (0.6.7).

How to confirm it works

Directory structure and visibility after restart (measured shape):

ls ~/.claude/skills/agent-skills
-> 24 subdirectories + 24 SKILL.md files

After restarting the agent, the skills show up in the skills list; the document-skills subset works the same way.

Other environments

EnvironmentNotes
Wrong directoryMove to the correct path ~/.claude/skills/agent-skills
Not restartedFully quit and restart the agent session
Permission issueConfirm the target directory is writable
Version issueTag matches recorded version 0.6.7
Not measuredLoading 24 skills in a real Claude Code/Cursor/Codex environment, standalone document-skills subset install, --list browse mode, per-skill verification of all skills, Windows/macOS

Symptom

After installing per the tutorial (/plugin install flow or method B), the agent shows no skills; or the document-skills subset installs with no effect.

Cause

A skill package is essentially directory copying (no binaries): wrong directory, no full quit/restart of the agent, or a permission/path issue during the copy all cause "installed but invisible"; document-skills is a subset of the same skill set with the same root causes (network/permission/version incompatibility are common failure surfaces, per CSDN install Q&A).

Solution

  1. Check the skills directory: ls ~/.claude/skills/agent-skills (should be 24 directories, each with SKILL.md).
  2. Fully quit and restart the agent session, then look again (skills are scanned at startup).
  3. Permission: confirm the target directory is writable; version: confirm the tag matches the recorded version (0.6.7).
Verification Evidence
  • Measured in this marketplace (2026-08-28): after method B's copy, the target directory has 24 directories + 24 SKILL.md files; startup-scan behavior is a general mechanism, not re-measured in a real agent environment - honestly noted.

Not measured (honest note)

  • Loading 24 skills in a real Claude Code/Cursor/Codex environment (requires the matching IDE/account); standalone document-skills subset install; --list browse mode; per-skill verification of all 24 skills; Windows/macOS environments.

Applicable tools (1)

This problem is linked from the tool pages below — reachable from either side.

agent-skills

Source & evidence

Recorded Verified ✓ VerifiedApplies to 1 tool(s)
Entries contain locally measured or reviewable-source solutions; unmeasured items are explicitly labeled.

← Skills Management domain | Problem Catalog Experience | Facing another issue? Go to the Helpdesk