Deleted skills remain in the system prompt, pointing into .claude/skills/.trash/ #50786

Version: opencode 1.18.31 / macOS

What happens

The <available_skills> block in the system prompt lists skills whose <location> points into the skills trash directory. In my current session, 7 of 24 listed skills resolve to .trash/ paths:

<skill>
  <name>import-memory</name>
  <description>Import a memory export from another AI assistant…</description>
  <location>/Users/<user>/.claude/skills/.trash/1789846138850-94368-lVuEBW/import-memory/SKILL.md</location>
</skill>

Affected in my session: docs, import-memory, morning, pdf, pptx, skill-creator, xlsx.

Why it matters

1. Deleted skills are still offered to the model. These were removed, but the model is told they are available and will invoke them via the skill tool. The trash directories still exist on disk today, so the calls may even succeed — silently running a version of a skill that was deleted. Once the trash is reaped, the same calls fail.

2. The paths are volatile, which breaks prompt caching. Each trash entry is .trash/<epoch-ms>-<pid>-<random>/, and re-synced skills move into skills/synced/<uuid>_<uuid>/. Both change whenever the skills directory is touched. I captured two sessions about 70 minutes apart, and the only difference across the entire 29,500-character system prompt was 47 characters of skill path churn:

- /Users/<user>/.claude/skills/.trash/1789846000064-88864-3so93G/docx/SKILL.md
+ /Users/<user>/.claude/skills/synced/f2cda5da-…_bd1e48d8-…/docx/SKILL.md

- /Users/<user>/.claude/skills/.trash/1789846000061-88864-BcyEBk/import-memory/SKILL.md
+ /Users/<user>/.claude/skills/.trash/1789846138850-94368-lVuEBW/import-memory/SKILL.md

That is enough to invalidate the cached system prompt. I run opencode against a local inference server where the system prompt is ~12,800 tokens and a cold prefill costs about two minutes, so an unnecessary invalidation is very visible. It will also defeat provider-side prefix caching for anyone on a hosted model.

Expected

• Skills under .trash/ are excluded from the skills listing.
• Skill <location> values are stable across re-syncs — ideally a canonical path or a name-based identifier rather than a content-addressed or timestamped directory.

Repro

1. Install some skills, then delete a few so they land in ~/.claude/skills/.trash/.
2. Start an opencode session and dump the system prompt.
3. The deleted skills appear in <available_skills> with .trash/… locations.