Regression: built-in customize-opencode skill exists in core but slash discovery/invocation no longer matches Ctrl+P

[simuxipalacheshi]

Bug report

Built-in skill customize-opencode still exists in core, but recent versions regressed slash discoverability / invocation parity: Ctrl+P can find it, while /customize-opencode and /skill do not expose it consistently.

This appears to be a regression, not a missing install or user config problem.

What I verified locally

• Running binary: opencode 1.15.11
• opencode debug skill shows built-in skill:
  • name: "customize-opencode"
  • location: "<built-in>"
  • full built-in content loaded successfully
• Ctrl+P / command palette can still find and use customize-opencode
• Slash invocation / discovery no longer works consistently

Why this looks like a regression

Historically this built-in skill was slash-invokable. The skill still exists in core, but the slash/autocomplete path appears to have drifted.

There is already precedent for recent Ctrl+P vs slash regressions:

• /exit and /quit slash commands missing in autocomplete (v1.14.42) #26549
• #26606

And prior architecture history showing command palette vs slash divergence:

• #9114

Upstream code evidence

The built-in skill is still registered in core:

• packages/opencode/src/skill/index.ts
  • CUSTOMIZE_OPENCODE_SKILL_NAME = "customize-opencode"
  • built-in registration into skill state before disk discovery

But current TUI autocomplete still filters out skill-sourced commands:

• packages/opencode/src/cli/cmd/tui/component/prompt/autocomplete.tsx

for (const serverCommand of sync.data.command) {
  if (serverCommand.source === "skill") continue
  ...
}

That matches the observed symptom: the built-in skill exists, but slash/autocomplete drops source === "skill" entries.

Expected behavior

If customize-opencode appears in opencode debug skill, slash discovery/invocation should remain consistent with that registration, and Ctrl+P and / should not diverge.

Related issues

• How to user new skill 【customize-opencode】， I cant find it by / or /skill #26660 reported the same visible symptom for customize-opencode
• This new issue is specifically to report the current regression with stronger reproduction evidence and code pointers

[github-actions]

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

• Bug: Custom skills not shown in / autocomplete menu #25117: Reports the same symptom — custom/built-in skills not appearing in the / autocomplete menu, despite being loaded and visible via opencode debug skill
• How to user new skill 【customize-opencode】， I cant find it by / or /skill #26660: Closed issue explicitly mentioned in this report, which had the same visible symptom for customize-opencode not being findable via / or /skill

If the regression you're describing is distinct from these (e.g., it was previously working and a specific version broke it), please clarify how this differs so maintainers can assess it separately.

[simuxipalacheshi]

Additional regression context:

This is not just a generic discovery mismatch.

Historically, this built-in skill was actually usable both by the AI side and by the user via slash invocation. The regression is that after recent OpenCode updates, customize-opencode still exists in core (opencode debug skill confirms it), and Ctrl+P can still find it, but slash discovery / invocation no longer stays in parity with that registration.

So the important point is:

• Previously worked: built-in skill could be slash-invoked / surfaced normally
• Currently broken: built-in skill still exists, but slash path regressed while Ctrl+P path still works

That makes this specifically a regression in built-in skill exposure / slash behavior, not a request for a new feature and not simply a missing local install.

[kommander]

There is /skills which opens a dialog, skills have never been available as slash commands afaik.

Some bot insights:

I don’t think this is a customize-opencode regression.
Skills are currently omitted from TUI / autocomplete by design/code: autocomplete.tsx skips serverCommand.source === "skill". That behavior was introduced in #11547 (5b784871f0), whose PR text explicitly says individual skills are hidden from / autocomplete and accessed via /skills.
There was only a brief earlier window where skills were exposed directly as slash commands: #11390 (81ac41e089) on Jan 31, 2026. A separate /skill:<name> attempt (#11369, 786ae0a584) was reverted the same day by #11484 (53f118c57a).
customize-opencode came later: added in #26617 (10ea59066f, May 9) and enabled by default in #26899 (df386bd651, May 11). So I don’t see evidence that customize-opencode ever shipped in the TUI / autocomplete after it was introduced.