Skip to content

docs(vercel-cli skill): add dashboard path to the domains reference#16631

Draft
privatenumber wants to merge 1 commit into
mainfrom
hirokiosame/skill-domains-dashboard-path
Draft

docs(vercel-cli skill): add dashboard path to the domains reference#16631
privatenumber wants to merge 1 commit into
mainfrom
hirokiosame/skill-domains-dashboard-path

Conversation

@privatenumber

Copy link
Copy Markdown
Contributor

Problem

The vercel-cli skill's domains reference is CLI-only: its "Typical Flow" starts at vercel domains add ... and never mentions that the same flow exists in the dashboard. Agents consuming the skill inherit that framing — Vercel Agent, asked from the dashboard side panel how to add an already-owned domain, answered with vercel domains add code blocks, which a side-panel user has nowhere to run (reported in #feedback-product, 2026-06-12: "It's suggesting CLI commands. I think most people won't know what to do with them").

Trace evidence from the agents-side eval (vercel/agents#1777): every failing trial's single tool call was a read of exactly this reference file, and the answers mirrored its CLI framing. The behavioral fix landed in the agent's prompt (vercel/agents#1778); this PR fixes the knowledge source so the dashboard path is available where the agent actually reads, letting the prompt carry only the generic surface policy.

Changes

@changeset-bot

changeset-bot Bot commented Jun 12, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: e6f116c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 0 packages

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@github-actions

Copy link
Copy Markdown
Contributor

🧪 Unit Test Strategy

Comparing: 3d8df16e6f116c (view diff)

Strategy: No tests needed

✨ No packages affected - skipping tests

Results

  • Unit tests: None
  • E2E tests: Running in parallel in this workflow
  • Type checks: None

This comment is automatically generated based on the affected testing strategy

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant