Skip to content

/vaybel:find-trend tshirt --lifecycle rising

→ Coastal Grandma Revival · rising · 4 keywords

/vaybel:launch-product "washed trail tee"

→ design ✓ · 5 mockups ✓ · ready to list

Vaybel Skills

Find a trend, launch the product, optimize the listing, make the content — from your coding agent, through the public Vaybel MCP server.
  1. Add the marketplace and install the plugin in Claude Code:

    /plugin marketplace add vaybel/skills
    /plugin install vaybel@vaybel
  2. Set VAYBEL_PAT once in your agent settings, and reuse it for both the Vaybel MCP server and these skills. Create a PAT in Vaybel at Dashboard → Settings → API & MCP — create a free account first if you do not have one.

  3. Run a workflow:

    /vaybel:launch-product "washed trail running poster art on a heavyweight tee"

Prefer a clone, or installing into Codex or Cursor? See Install.

Each skill maps to one Vaybel dashboard workflow, so what the agent does and what you would have done by hand stay the same shape.

The four workflow skills chain in the order you would run them in the app:

Analyze Insightsread-only — tells you which one to run next

Vaybel Skills follow the code-execution-with-MCP pattern. A skill is not a pile of tool calls for the model to sequence — it is a SKILL.md that tells the agent when to run the workflow, plus a TypeScript runner that does the sequencing, waiting, and error handling deterministically.

SKILL.md→run.ts→servers/vaybel→client.ts→mcp.vaybel.com

One tool call, not twenty

The runner handles credit checks, generation polling, and retries. The agent gets back a short summary with dashboard links instead of raw MCP payloads.

Public MCP only

No private REST APIs, no Vaybel CLI dependency. Everything the skills do, you can do with the same public MCP surface.

One shared secret

VAYBEL_PAT authenticates both the MCP server and the skills. Tokens are never requested in chat.

Portable across agents

Ships Claude Code, Codex, and Cursor plugin manifests from the same skills/ directory.