Eight Versely skills, one npx command

npx skills add AI-XLabs-Innovation/versely-skills pulls generate, slideshow, movie, ugc, music, social, analytics, pipeline into Claude Code, Cursor, Codex. Cloning skills is not a generate.

The command writes eight markdown procedures onto disk. It does not mint a key, call a model, or spend a credit. Pixels start when an agent following those procedures actually hits Versely. The skills page is the product surface. Pair it with the CLI and MCP so the agent has callables as well as runbooks. The in-app agent already has routing of its own; it does not load these files.

The command writes procedures, not pixels

A Versely skill is a folder with a SKILL.md. Frontmatter names it (versely-generate, versely-slideshow, …), describes when to use it, and lists allowed tools — currently Bash and Read. The body is the runbook: endpoint, required fields, polling, error ladder. Generation is asynchronous; poll GET /api/v1/status/:requestId. 401 is a bad key, 402 is insufficient credits (stop, report balance), 403 is a missing scope, 429 means read X-RateLimit-Reset, 500 means retry once after ten seconds.

npx skills add uses Vercel Labs’ skills CLI and writes into whichever agents that CLI knows about. Claude Code, Cursor, and Codex are the named targets. It does not write mcpServers.versely and it does not store ~/.versely/config.json. Clone the repo or run npx and wait for an MP4, and you installed instructions. The billed call comes later, on the same credit balance as the app.

npx @versely/cli setup is the one-pass install: skills, browser sign-in, MCP into every detected agent. Skills-only is valid when VERSELY_API_KEY is already in the environment. MCP-only is the common failure: tools appear, no pre-flight.

The eight

1. generate — versely-generate

One-shot images, clips, lipsync, TTS, sound effects, a simple Suno track. Multi-scene films, carousels, stems, and publishing belong elsewhere. Owns the credit check and the /status/:requestId poll.

2. slideshow — versely-slideshow

A stack of stills, a carousel, a stills-to-video reel. Phrase “carousel” so the matcher does not drift to generate.

3. movie — versely-movie

Scenes, retries per scene, previous-frame chaining. Poll GET /api/v1/movie/:id/status, not /status/:requestId. One prompt, one clip is still generate.

4. ugc — versely-ugc

Talking-head overlay, burned captions, auto-timed speech. Generating the plate is generate; the overlay is ugc.

5. music — versely-music

Extend, mashup, stems, MIDI, personas, covers. A one-line lo-fi bed can stay in generate. Anything past /suno/generate belongs here.

6. social — versely-social

Publish, schedule, list, or delete on connected accounts. Lists accounts first; if none, it stops. It does not generate the asset.

7. analytics — versely-analytics

Metrics on Versely-published posts, a trend analysis, a public trending URL. “How did last week do” is this pack. “Make another” is generate or pipeline.

8. pipeline — versely-content-pipeline

Chains the others, with a budget step first, because a flow that dies at step six has already spent steps one through five. Retry the failed step; intermediate URLs stay valid. Set up a full content pipeline is the in-app form.

Cloning the skills repo is not a generate

Copying markdown onto disk — npx, git clone, a fork in .claude/skills — does not create an image, a clip, a track, or a post. There is no price_matrix on a SKILL.md. Credits start when a procedure calls Versely.

People collapse that. They treat “I installed skills” as “I ran a job,” look for an output, then paste the same prompt into the in-app agent and pay twice. Or they clone in CI, skip auth, and wonder why nothing renders. Cloning is not a catalog row on /developer.

Install is configuration. Generate is a billed side effect. Unused packs are idle instructions, not idle spend. A key with only the generate scope will 403 on slideshow and social even if the skill fired. Pipeline needs the union of the steps it will run.

The in-app chat model is a different knob. Skills do not pin z-ai/glm-5.3 or x-ai/grok-4.6. Treat /chat-models as live; GLM 5.3 is not the default. In a coding agent the host model is Cursor or Claude Code. The renderer is whichever generate row the procedure names.

Pair them with MCP, then talk in jobs

MCP at https://mcp.versely.studio/mcp is capability. Skills are discipline. Capability without discipline retries a 402. Discipline without capability is curl from a runbook.

Restart the agent after install; MCP config is not reloaded in place. versely status prints auth and per-agent not detected / detected, not connected / connected. Phrase the job so one pack’s “use when” clause fits: “carousel,” “chained scenes,” “stems,” “schedule this.” “Make me content” matches generate and almost nothing else. Say the shape, not the filename — eight procedures, zero pixels, until you ask.

FAQ

Does npx skills add spend credits?

No. It copies eight skill packs onto disk. Credits start when a generate, post, analysis, or other Versely call actually runs. Cloning the repo is the same: instructions, not a render.

Do I need MCP as well?

For a terminal agent you use more than once, yes. Skills are the runbook; MCP tools are the typed callables. npx @versely/cli setup installs both. Skills alone can curl if a key is in the environment.

Do I have to use all eight?

The install is all eight. Unused packs are idle markdown. Spend starts when a call runs. An agent with no connected accounts can still load versely-social; the pack’s pre-check is “list accounts, then stop.”

Is this the same as the in-app agent’s chat model?

No. Skills run inside Claude Code, Cursor, Codex, and other detected agents. The in-app agent has its own planner list on /chat-models. Pinning GLM 5.3 or Grok 4.6 there does not install these packs, and installing the packs does not change that default.