Skip to content

display.dev skill

Install the display.dev skill in a compatible agent.

On this page

The display.dev skill teaches your agent to publish, browse, inspect, edit, and share artifacts from natural-language prompts like "publish this", "find the quarterly report", or "change this passage".

Install

sh
npx skills add display-dev/skill --skill display-dev

Host support follows the released installer rather than a fixed list on this page. Review any requested configuration changes before approving them. If the installer does not support your host, use the MCP server guide.

Capabilities

Once installed, your agent can:

  • Publish HTML or Markdown. Anonymous or authenticated. Returns the artifact's URL.
  • Browse and inspect artifacts. List published work, search names or source text, read bounded source ranges, and retrieve metadata, retained versions, headings, and open threads.
  • Edit one exact passage. The agent verifies the current version and unique source text, then publishes the replacement as the next version at the same URL.
  • Sign in with an email one-time password, or with single sign-on when your organization requires it.
  • Change visibility and sharing – public, company, or private; invite or remove people by email.
  • Iterate on comments. When reviewers leave comments, the agent searches and reads the relevant source, makes an exact edit when possible, and replies or resolves in the same session. Broader changes still use the confirmed local source.

Remote MCP keeps source access bounded: agents use search and read, not complete-source export. Local CLI workflows can still run dsp export when they genuinely need the complete file.

Without an account

The first publish doesn't need a display.dev account. You get a public preview URL plus a single-use 30-day claim link; open it and sign in to keep the artifact in your organization at the same URL.

Sharing, renaming, single sign-on, and multi-file workflows need an account. The skill walks you through email-code sign-up the first time you ask for one of those.

Authoring for dsp.so

Artifacts served on *.dsp.so get a light/dark theme toggle in the Display.dev bar at the top. The skill tells your agent to branch the artifact's CSS on [data-theme="dark"], so generated artifacts work in both palettes.

Was this page helpful?