Project .opencode/skills not discovered in TUI sessions (only in run/debug skill)

[ngoc-minh-do]

Description

In interactive TUI sessions, project skills under .opencode/skills/<name>/SKILL.md are never discovered, so the model cannot load them. Headless commands on the same machine, repo, and directory see them fine. A freshly launched TUI process reproduces it, so it is not stale state. The config workaround "skills": { "paths": [".opencode/skills"] } is ignored by the TUI but honored headless.

Steps to reproduce

1. git init demo && cd demo
2. mkdir -p .opencode/skills/demo and add .opencode/skills/demo/SKILL.md with frontmatter name: demo + description: Demo skill.
3. Ensure at least one external skill exists, e.g. ~/.agents/skills/context7-mcp/SKILL.md
4. opencode debug skill lists demo; opencode run "hi" --print-logs 2>&1 | grep "init count" shows message=init count=3
5. Launch opencode (TUI), invoke ->Skill "demo" -> Skill "demo" not found; the TUI process logs message=init count=2
6. Restart the TUI fresh with "skills": { "paths": [".opencode/skills"] } in the project config -> still count=2

Plugins

@tarquinen/opencode-dcp@latest (only plugin; also tested without)

OpenCode version

1.18.27 (installer binary from https://github.com/anomalyco/opencode, dev)

Operating System

Debian GNU/Linux 13 (trixie)

Terminal

VS Code integrated terminal (xterm-256color)

Screenshot and/or share link

Not yet provided (can generate a /share link if needed)

[github-actions]

This issue might be a duplicate of existing issues. Please check:

• New global skills not available for model to use #32181: Skills visible in opencode debug skill but not available to the model/TUI — similar symptom where skills are discovered in debug/headless mode but not accessible in the interactive TUI session.

[sizzlecar]

I can’t reproduce this on 1.18.27: the same project reports count=3 in both TUI and debug skill. Does it still happen in a brand-new session, and what directory does the TUI log for creating instance?

[ngoc-minh-do]

Clarifying the resolution: the fix was user-side only, not a code fix.

Root cause of our report: the skill's frontmatter description contained unquoted colon + space sequences (e.g. ...homelab: Docker Compose..., USE FOR: deploy...). On the full-TUI/model-facing path this skill was silently dropped (no parse error logged, init count=2), while opencode debug skill still listed it (count=3). That mismatch matches the pattern described in #32181 (and #6858 family).

After rewriting the description without : , a fresh TUI boot logged init count=3 and the skill now loads in-session. This confirms it was the frontmatter, not a TUI-only discovery bug.

Important: the underlying opencode issue — the model-facing registry and debug skill using different frontmatter validation so a malformed skill is silently excluded from sessions while still appearing in debug output — is not fixed in code. Any skill with an unquoted colon + space in a frontmatter value will still hit it.

@StarpTech / maintainers: suggest treating this as a duplicate of #32181 rather than resolved, since the validation divergence remains.