Bug description
Repo-local Claude Code skills (.claude/skills/*/SKILL.md, symlinked from .agents/skills/) are visible to the Claude CLI directly (/reload-skills reports them as available) but never appear in T3 Code's skill picker for that project.
This looks like the same root cause as #3040, for a different provider: T3 Code's per-provider skill cache doesn't include repo-local skills at all, only global/plugin skills.
Evidence
~/.t3/caches/claudeAgent.json lists exactly 7 skills, all global/plugin-installed (find-skills, i-have-adhd, orca-cli, orca-linear, orchestration, sanity-best-practices, sanity-migration). It does not include either of the two project-local skills that exist in the repo (craft-eager-loading, merge-to-stage), even though:
- The cache file's mtime is after the project skill files were last written to disk (cache regenerated later, so it isn't a stale/one-time-scan timing issue).
- The Claude CLI (
/reload-skills) reports these two skills as available in the same project directory at the same time.
So the Claude provider cache appears to only capture global/plugin skill sources, never scanning the project's own .claude/skills (or its .agents/skills symlink target).
Steps to reproduce
- Add a project-local skill:
.agents/skills/<name>/SKILL.md, with .claude/skills symlinked to .agents/skills per the Agent Skills convention.
- Open the project in the Claude CLI directly; confirm the skill is discovered (
/reload-skills or asking Claude to list available skills).
- Open the same project in T3 Code and open the skill picker (
$/@).
- Expected: the project-local skill appears alongside global/plugin skills.
- Actual: only global/plugin skills appear; project-local skills are absent from
~/.t3/caches/claudeAgent.json and the picker.
Related
Happy to share the (redacted) cache file contents or repo structure if useful for triage.
Bug description
Repo-local Claude Code skills (
.claude/skills/*/SKILL.md, symlinked from.agents/skills/) are visible to the Claude CLI directly (/reload-skillsreports them as available) but never appear in T3 Code's skill picker for that project.This looks like the same root cause as #3040, for a different provider: T3 Code's per-provider skill cache doesn't include repo-local skills at all, only global/plugin skills.
Evidence
~/.t3/caches/claudeAgent.jsonlists exactly 7 skills, all global/plugin-installed (find-skills,i-have-adhd,orca-cli,orca-linear,orchestration,sanity-best-practices,sanity-migration). It does not include either of the two project-local skills that exist in the repo (craft-eager-loading,merge-to-stage), even though:/reload-skills) reports these two skills as available in the same project directory at the same time.So the Claude provider cache appears to only capture global/plugin skill sources, never scanning the project's own
.claude/skills(or its.agents/skillssymlink target).Steps to reproduce
.agents/skills/<name>/SKILL.md, with.claude/skillssymlinked to.agents/skillsper the Agent Skills convention./reload-skillsor asking Claude to list available skills).$/@).~/.t3/caches/claudeAgent.jsonand the picker.Related
$skill picker #3040 (same failure mode, Codex provider +.agents/skills)Happy to share the (redacted) cache file contents or repo structure if useful for triage.