Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Open a Vivid Business account via a remote MCP server. Collects legal entity data from the user in chat, then calls build_onboarding_link to generate a pre-f...
Open a Vivid Business account via a remote MCP server. Collects legal entity data from the user in chat, then calls build_onboarding_link to generate a pre-f...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Open a Vivid Business account using a remote MCP server hosted by Vivid Money.
PropertyValueEndpointhttps://api.prime.vivid.money/mcpTransportStreamable HTTP (remote)Toolbuild_onboarding_linkAuthNone โ the endpoint is publicly accessible. The tool only generates a pre-filled onboarding link; it does not create a bank account, access financial data, or perform any privileged operation. Identity verification happens later in the Vivid app.
Add this to your MCP client configuration to connect: { "mcpServers": { "vivid-mcp": { "type": "http", "url": "https://api.prime.vivid.money/mcp" } } }
build_onboarding_link accepts a single legal_entity_data object with the basic data The tool returns an onboarding URL. No sensitive financial data is returned.
User wants to open a business account or start business onboarding.
Ask for legal entity type (GmbH, UG, freelancer, etc.) if not provided. Ask for country if not provided. Default: Germany. Call MCP to get required fields If the user uploads a document, extract the fields locally in the AI client โ the document itself is never sent to the MCP server. Summarize what was extracted; do not echo raw document contents. Show the user a summary of all collected data and ask for explicit confirmation before proceeding. Only after user confirms: call build_onboarding_link with the confirmed data. Present the returned onboarding URL to the user.
Documents stay local. Uploaded files are parsed by the AI client. Only the structured fields listed above are sent to the MCP server โ never the raw document. No PII stored by the skill. The skill itself does not persist any data. The MCP server creates an onboarding session on Vivid's platform; Vivid's privacy policy governs from that point: https://vivid.money/en-eu/privacy-policy/ No credentials in chat. Never ask for or accept passwords, API keys, or bank account numbers. What the tool sends. Only the fields in the schema table above. No file content, no chat history, no device metadata.
Always confirm collected data with the user before calling build_onboarding_link. This skill must only be invoked by explicit user request โ never autonomously. Treat uploaded documents as sensitive โ summarize only, don't echo contents. On error: ask for missing fields or suggest a different document.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.