What happened
Across one evening I invoked /wayfinder nine times. Three of those passed a GitHub PR URL (and once a PR comment URL) instead of a map or a loose idea. Each time the agent fetched the PR, found it green and mergeable with nothing to decide, and had to ask what the loose idea actually was. The user never saw, in the skill's own words, what the argument should be.
The intro describes the shape (map or loose idea) only implicitly, via the two invocation modes near the bottom of a long document. There is no front-loaded line stating what ARGUMENTS may be.
Suggestion
One sentence at the top of SKILL.md, before the prose, e.g.:
Takes either a map (issue URL/number or map file path) to work through, or a loose idea in words to chart. A PR, commit or finished issue is neither; report its status and ask for the idea.
Optionally, a short "Neither mode fits" exit in the Invocation section so the agent's behaviour on a PR link is specified rather than improvised.
Plugin version 1.2.3 and 1.3.1, Claude Code, local-markdown tracker.
What happened
Across one evening I invoked
/wayfindernine times. Three of those passed a GitHub PR URL (and once a PR comment URL) instead of a map or a loose idea. Each time the agent fetched the PR, found it green and mergeable with nothing to decide, and had to ask what the loose idea actually was. The user never saw, in the skill's own words, what the argument should be.The intro describes the shape (map or loose idea) only implicitly, via the two invocation modes near the bottom of a long document. There is no front-loaded line stating what
ARGUMENTSmay be.Suggestion
One sentence at the top of
SKILL.md, before the prose, e.g.:Optionally, a short "Neither mode fits" exit in the Invocation section so the agent's behaviour on a PR link is specified rather than improvised.
Plugin version 1.2.3 and 1.3.1, Claude Code, local-markdown tracker.