Skip to content

display.dev skill

One-command install for Claude Code, Cursor, Codex, OpenCode, and Hermes via npx skills add.

On this page

The display.dev skill teaches your AI assistant how to publish, share, and sign in to display.dev from natural-language prompts ("publish this", "share with the org", "make a private link"). It's a thin packaging layer on top of the dsp CLI — installing the skill gives the assistant the right intent triggers and a small set of bash helpers; everything authenticated still flows through dsp.

Install

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

The command works the same across Claude Code, Cursor, Codex, OpenCode, and Hermes — the skill ships parallel mounts each installer recognizes. Once installed, asking your assistant any of "publish this", "share this with the org", "post this online", "make a private link", "share with [email]" routes through display.dev.

Two-tier helpers

The skill ships two layers of helpers so the first publish doesn't require Node:

  • Tier 1 — anonymous publish and OTP sign-up. Pure bash + curl, no Node dependency. Works on any system. Publishing without a credential lands the file on a 30-day claimable URL; signing in writes ~/.displaydev/config.json and converts the link to a permanent one.
  • Tier 2 — everything authenticated, plus share, SSO login, and any subcommand that takes extra flags. Falls through to dsp if installed, or npx -y @displaydev/cli if not. Single-file publishes only today; multi-file uploads are a separate spec.

You don't pick the tier — the helpers detect which path applies from the argument shape and the presence of a credential.

Attribution

Skill-launched requests carry an X-Client-Source header (default display-dev-skill@<version>) so we can tell which distribution channel a publish came from. If you're wrapping dsp yourself, pass --client-source <name> or set DISPLAYDEV_CLIENT_SOURCE=<name> to record your own channel — see CLI reference.

When to use the skill vs the CLI directly

  • Use the skill if your work runs through an AI assistant (Claude Code, Cursor, Codex, OpenCode, Hermes). The skill is the cheapest way to wire publishing into prompts you're already writing.
  • Use the CLI directly in CI pipelines, scripts, or any context where you're typing commands yourself. The skill adds nothing on top of dsp for that workflow.

Installing both is fine — the skill calls dsp under the hood whenever it can.

Was this page helpful?