Skip to content

Docs list the Nexus skill as nexus-tracing; it is declared as nexus-trace #187

Description

@rwvo

Summary

docs/how-to/skills-setup.md documents the Nexus skill under the name nexus-tracing, but the skill declares itself as nexus-trace. An agent given the documented name will not find the skill.

Evidence

Declared name — nexus/skill/SKILL.md:2:

name: nexus-trace

Documented name — docs/how-to/skills-setup.md:31:

| `nexus-tracing` | Nexus | GPU execution inspection, HSA packet tracing, assembly extraction |

nexus-tracing occurs exactly once in the repository, and only in that table.

Scope

This is the only mismatch of the six skills. Every other row agrees with its SKILL.md:

Documented in skills-setup.md Declared in <tool>/skill/SKILL.md Match
metrix-profiling metrix-profiling yes
test-kerncap test-kerncap yes
linex-profiling linex-profiling yes
nexus-tracing nexus-trace no
accordo-validation accordo-validation yes

Impact

The docs table is the discovery surface for agent skills — it is what a user or agent reads to learn what to invoke. A name that does not resolve fails silently: the agent looks for a skill that does not exist rather than reporting a typo.

Suggested fix

Change the table row to nexus-trace, matching the declaration. The alternative — renaming the skill to nexus-tracing — would be a behavior change for anyone already invoking it by its real name, so correcting the docs looks like the lower-risk direction.

Notes

Found while editing that table for an unrelated change. Not fixed in that PR, to keep an unrelated correction out of its diff.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions