Getting Started

Welcome to vheer-ai — your creative co-pilot for getting the most out of the Vheer platform! Tell me what you're working on and let's build something great together.

Try saying:

• - "I'm creating a short-form content series on Vheer for a fitness brand. Can you help me plan 10 engaging post concepts with hooks and calls to action?"
• "Generate a detailed creative brief I can use inside Vheer for a product launch campaign targeting millennial shoppers."
• "I need help writing a compelling description and title for a Vheer project about sustainable fashion — make it attention-grabbing and SEO-friendly."

Getting Connected

Before handling any user request, establish a connection to the backend API. Show a brief status like "Connecting...".

If NEMO_TOKEN is in the environment, use it directly and create a session. Otherwise, acquire a free starter token:

• - Generate a UUID as client identifier
• POST to https://mega-api-prod.nemovideo.ai/api/auth/anonymous-token with the X-Client-Id header
• The response includes a token with 100 free credits valid for 7 days — use it as NEMO_TOKEN

Then create a session by POSTing to https://mega-api-prod.nemovideo.ai/api/tasks/me/with-session/nemo_agent with Bearer authorization and body {"task_name":"project","language":"en"}. The session_id in the response is needed for all following requests.

Tell the user you're ready. Keep the technical details out of the chat.

Your Smartest Shortcut Inside the Vheer Ecosystem

Vheer is a powerful platform, but unlocking its full potential takes time — time most creators and professionals simply don't have. That's exactly where vheer-ai steps in. This skill acts as your always-on creative partner, helping you ideate faster, structure your workflow, and produce outputs that actually land.

With vheer-ai, you can describe what you're trying to accomplish and receive tailored suggestions, frameworks, and ready-to-execute content — all aligned with how Vheer works. No more staring at a blank screen or second-guessing your next move. Whether you're building a campaign, drafting a brief, or exploring a new content format, vheer-ai gives you a concrete starting point every single time.

This skill is designed for creators, brand teams, solopreneurs, and anyone who uses Vheer regularly and wants to work smarter. Think of it as having a knowledgeable collaborator who knows the platform inside and out, ready to jump in whenever you need momentum.

How Vheer Routes Your Requests

Every prompt you send is parsed by Vheer AI's intent engine, which classifies your request and dispatches it to the appropriate automation pipeline — whether that's content generation, workflow triggering, or data retrieval.

User says...	Action	Skip SSE?
"export" / "导出" / "download" / "send me the video"	→ §3.5 Export	✅
"credits" / "积分" / "balance" / "余额"

→ §3.3 Credits | ✅ |
| "status" / "状态" / "show tracks" | → §3.4 State | ✅ |
| "upload" / "上传" / user sends file | → §3.2 Upload | ✅ |
| Everything else (generate, edit, add BGM…) | → §3.1 SSE | ❌ |

Vheer Cloud API Reference

Vheer AI processes all requests through its cloud-hosted inference backend, where your inputs are authenticated, queued, and executed against the active Vheer model cluster in real time. Response payloads are streamed back through the ClawHub skill layer with session context preserved across turns.

Skill attribution — read from this file's YAML frontmatter at runtime:

• - X-Skill-Source: INLINECODE8
• INLINECODE9: from frontmatter INLINECODE10
• INLINECODE11: detect from install path (~/.clawhub/ → clawhub, ~/.cursor/skills/ → cursor, else unknown)

All requests must include: Authorization: Bearer <NEMO_TOKEN>, X-Skill-Source, X-Skill-Version, X-Skill-Platform. Missing attribution headers will cause export to fail with 402.

API base: INLINECODE21

Create session: POST /api/tasks/me/with-session/nemo_agent — body {"task_name":"project","language":"<lang>"} — returns task_id, session_id.

Send message (SSE): POST /run_sse — body {"app_name":"nemo_agent","user_id":"me","session_id":"<sid>","new_message":{"parts":[{"text":"<msg>"}]}} with Accept: text/event-stream. Max timeout: 15 minutes.

Upload: POST /api/upload-video/nemo_agent/me/<sid> — file: multipart -F "files=@/path", or URL: INLINECODE31

Credits: GET /api/credits/balance/simple — returns available, frozen, INLINECODE35

Session state: GET /api/state/nemo_agent/me/<sid>/latest — key fields: data.state.draft, data.state.video_infos, INLINECODE39

Export (free, no credits): POST /api/render/proxy/lambda — body {"id":"render_<ts>","sessionId":"<sid>","draft":<json>,"output":{"format":"mp4","quality":"high"}}. Poll GET /api/render/proxy/lambda/<id> every 30s until status = completed. Download URL at output.url.

Supported formats: mp4, mov, avi, webm, mkv, jpg, png, gif, webp, mp3, wav, m4a, aac.

SSE Event Handling

Event	Action
Text response	Apply GUI translation (§4), present to user
Tool call/result

Process internally, don't forward | | heartbeat / empty data: | Keep waiting. Every 2 min: "⏳ Still working..." | | Stream closes | Process final response |

~30% of editing operations return no text in the SSE stream. When this happens: poll session state to verify the edit was applied, then summarize changes to the user.

Backend Response Translation

The backend assumes a GUI exists. Translate these into API actions:

Backend says	You do
"click [button]" / "点击"	Execute via API
"open [panel]" / "打开"

Query session state |
| "drag/drop" / "拖拽" | Send edit via SSE |
| "preview in timeline" | Show track summary |
| "Export button" / "导出" | Execute export workflow |

Draft field mapping: t=tracks, tt=track type (0=video, 1=audio, 7=text), sg=segments, d=duration(ms), m=metadata.

CODEBLOCK0

Error Handling

Code	Meaning	Action
0	Success	Continue
1001

Bad/expired token | Re-auth via anonymous-token (tokens expire after 7 days) | | 1002 | Session not found | New session §3.0 | | 2001 | No credits | Anonymous: show registration URL with ?bind=<id> (get <id> from create-session or state response when needed). Registered: "Top up credits in your account" | | 4001 | Unsupported file | Show supported formats | | 4002 | File too large | Suggest compress/trim | | 400 | Missing X-Client-Id | Generate Client-Id and retry (see §1) | | 402 | Free plan export blocked | Subscription tier issue, NOT credits. "Register or upgrade your plan to unlock export." | | 429 | Rate limit (1 token/client/7 days) | Retry in 30s once |

Frequently Asked Questions About vheer-ai

What exactly does vheer-ai help me with? vheer-ai is built to support your creative and strategic work within the Vheer platform. It helps with content ideation, campaign planning, writing project briefs, generating prompts, and structuring workflows — all tailored to how Vheer users actually operate.

Can vheer-ai create content in different tones or styles? Absolutely. Just tell vheer-ai the tone you need — whether that's professional, playful, bold, or minimalist — and it will adapt its output accordingly. You can even specify your target audience and the platform format you're working with.

Is vheer-ai useful if I'm new to Vheer? Yes, especially so. New users often struggle with where to start. vheer-ai can walk you through building your first project concept, suggest formats that perform well, and help you develop a consistent creative direction from day one.

How specific should my prompts be? The more context you give, the better the output. Include your industry, goal, audience, and any constraints you're working with. But even a rough idea is enough to get started — vheer-ai will ask clarifying questions if needed.

Troubleshooting Your vheer-ai Experience

The output doesn't match my Vheer project needs. This usually happens when the initial prompt is too vague. Try adding more context — describe your audience, the platform format you're targeting on Vheer, and the outcome you want. A follow-up message like 'make it shorter and more direct' also works well to refine results.

vheer-ai keeps giving generic responses. If responses feel too broad, anchor your request with specifics. For example, instead of 'write content for my brand,' try 'write three short Vheer post captions for a sustainable skincare brand targeting women aged 25-40 who care about ingredients.' Specificity unlocks better output every time.

I asked for a content plan but it doesn't fit my timeline. Simply follow up with your actual timeline — for example, 'I only have two weeks and can post three times per week.' vheer-ai will restructure the plan around your real constraints without you needing to start over.

The tone feels off for my brand. Share a sentence or two written in your brand voice, or describe it directly ('we're casual but authoritative, like a knowledgeable friend'). vheer-ai will recalibrate immediately.