Plugin skill descriptions are omitted from the available-skills list shown to the model

Summary

Skills defined by installed plugins are listed to the model by name only, without the description field from their SKILL.md frontmatter. Built-in skills (dataviz, verify, code-review, etc.) show their full descriptions in the same list. Since skill routing depends on the model matching the user's request against these descriptions, plugin skills are effectively invisible to routing even when their frontmatter descriptions are well-written and specific.

Repro steps

Note: this was first observed on an unreleased internal build of the Datadog plugin (v0.7.15), not yet publicly installable. For an independent repro, use a public plugin instead — steps below use atlassian, which shows the same behavior.

1. Install any plugin that ships skills, e.g. /plugin install atlassian@<marketplace>, and /reload-plugins.
2. Send any message and inspect the <system-reminder> listing of available skills sent to the model that turn.
3. Compare how plugin-sourced skills (atlassian:*, trajectory:*) are listed versus built-in skills (dataviz, verify, etc.).

Expected

Plugin skills appear in the list with their description frontmatter, same as built-in skills:

- ddsetup: First-time initialization of the plugin's Datadog MCP server. ... Relevant when the user wants to view or list dashboards or monitors...

Actual

Plugin skills appear as bare names with no description:

- atlassian:capture-tasks-from-meeting-notes
- atlassian:generate-status-report
- trajectory:incognito

Immediately followed by a built-in skill with its full description intact:

- dataviz: Use this skill whenever you are about to create ANY chart, graph, plot...

This pattern was also observed with an unreleased internal build of the Datadog plugin (datadog:datadog-app, ddconfig, ddsetup, ddtoolsets all appeared as bare names), which is what originally surfaced the issue — but since it reproduces identically on public plugins (atlassian, trajectory), the unreleased build isn't required to investigate or fix it.

Impact

Without a description to match against, the model has no signal to pick between multiple skills from the same plugin and falls back to guessing from the skill name alone. In the internal Datadog testing session that surfaced this, it caused the model to open datadog-app (a project-scaffolding skill) instead of ddsetup (the correct one for "show me a dashboard") on the first attempt — even though ddsetup's actual description explicitly lists "view or list dashboards" as a trigger phrase. This defeats the purpose of writing detailed, trigger-phrase-rich descriptions for plugin skills.

Suggested fix

Confirm whether the skill-listing renderer reads plugin skill descriptions from a different source than SKILL.md frontmatter (e.g., a manifest that doesn't carry per-skill descriptions) and, if so, have it fall back to SKILL.md's description field like built-in skills do.

Environment

• Behavior reproduces on public plugins (atlassian, trajectory) — no special access needed to investigate.
• Originally surfaced via an unreleased internal build of the Datadog plugin (datadog-claude-code v0.7.15), which is not yet publicly installable.
• Reported by a developer of the Datadog Claude Code plugin, 2026-07-14.