[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BXNR3KJ04PGE6QN0PBY4CF":3,"skill-same:01M7BXNR3KJ04PGE6QN0PBY4CF":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M7BXNR3KJ04PGE6QN0PBY4CF","ramp-setup-x402-wallet",null,"Set up and fund a Ramp x402 wallet from a Ramp Checking account. Use when an owner or admin of a company's Ramp account asks to enable, provision, fund, or prepare x402 payments. For an already-funded wallet and a specific x402 purchase, use ramp-make-x402-payment instead.","CognitionAI\u002Fdevin-marketplace","CognitionAI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F163493330?v=4","01M7BVSRD98NC4FG8T3EZS6V5M","Cognition","01M7BVSRDX111C2XPWJ0E6MY26",29,"MIT","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Framp\u002Fskills\u002Framp-setup-x402-wallet\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ramp-setup-x402-wallet\narea: Agentic Commerce\nsupported_surfaces: [browser, cli, mcp]\ndescription: >-\n  Set up and fund a Ramp x402 wallet from a Ramp Checking account. Use when an\n  owner or admin of a company's Ramp account asks to enable, provision, fund,\n  or prepare x402 payments. For an already-funded wallet and a specific x402\n  purchase, use ramp-make-x402-payment instead.\ncompatibility: Requires a user who is an owner or admin of the company's Ramp account with Ramp Checking access, an up-to-date Ramp CLI or Ramp MCP connection, Python 3, and browser access for OAuth and any required withdrawal approval.\n---\n\n# Set up a Ramp x402 wallet\n\nProvision the business's Ramp-managed Solana wallet and fund it from a Ramp\nChecking account. Ask one question at a time and never guess an account, amount,\npermission, or approval state.\n\n## Safety rules\n\n- Provisioning and funding are separate mutations. Get explicit confirmation\n  immediately before each one.\n- Never ask for passwords, one-time codes, banking credentials, private keys, or\n  wallet signing material. The user completes Ramp sign-in and approvals in\n  Ramp-controlled browser pages.\n- Every Ramp agent-tool call needs a non-empty `rationale`.\n- Generate each rationale from the user's actual request or immediately preceding\n  confirmation. Keep it concise and action-specific; do not reuse a canned\n  rationale sentence.\n- Use only an account UUID returned by `treasury accounts`; never infer or reuse\n  an identifier from another source.\n- Funding is an irreversible transfer from Ramp Checking. Use a new idempotency\n  key for every new transfer. A repeated funding call with the same key does not\n  replay the original result; reconcile an uncertain call before proceeding.\n\n## 1. Update and connect Ramp\n\n### Ramp CLI\n\nInspect the installed CLI:\n\n```bash\nramp --version\nramp update --help\n```\n\nIf the CLI is missing, stop and help the user install it through the trusted\ninstructions at https:\u002F\u002Fagents.ramp.com\u002Fdocs\u002Fcli\u002Foverview. If an update is\navailable, explain that it changes the local CLI installation and ask permission\nbefore running:\n\n```bash\nramp update\n```\n\nAuthenticate in the user-controlled browser and verify the session:\n\n```bash\nramp auth login\nramp auth status\n```\n\nRefresh the generated tool specification, then inspect the live CLI catalog:\n\n```bash\nramp tools refresh\nramp tools list\n```\n\nConfirm that the refreshed CLI exposes `treasury accounts`, `x402 create`, and\n`x402 fund`. Tool presence does not override account permissions; the calls\nbelow remain the source of truth for access.\n\n### Ramp MCP\n\nHave the user update or reconnect the Ramp MCP connector using their MCP\nclient's connection settings, complete Ramp OAuth in the browser, and refresh\nthe client's tool list. Confirm that the connected tool list includes the Ramp\nequivalents of:\n\n- List Ramp Checking accounts (`treasury accounts`)\n- Provision an x402 wallet (`x402 create`)\n- Fund an x402 wallet (`x402 fund`)\n\nIf any required tool is absent, disabled, or returns an authorization,\npermission, scope, or availability error, stop. Tell the user to contact\n[agents@ramp.com](mailto:agents@ramp.com) or visit\n[agents.ramp.com](https:\u002F\u002Fagents.ramp.com\u002F), then reconnect Ramp and try again.\nDo not expose internal rollout names or recommend broader permissions as a\nworkaround.\n\n## 2. Provision the x402 wallet\n\nExplain that Ramp will create a business x402 wallet on Solana and manage its\nsigning securely. Ask:\n\n```text\nAre you an owner or admin of the company's Ramp account, and do you confirm\nthat I should provision the company's Ramp x402 wallet?\n```\n\nOnly after the user confirms their company-level role and provisioning, call the\nRamp MCP tool or run:\n\n```bash\nRATIONALE=\"\u003Cconcise provisioning rationale from the user's confirmation>\"\nramp x402 create --confirmed \\\n  --rationale \"$RATIONALE\"\n```\n\nRecord the returned wallet address and require `status` to be `sign_ready`.\nRepeated calls return the same wallet, but still require confirmation. If Ramp\nreports that provisioning is unavailable or the business setup is incomplete,\nstop and relay the actionable error without retrying.\n\n## 3. Choose a Ramp Checking account and amount\n\nList every Ramp Checking account visible to the user:\n\n```bash\nRATIONALE=\"\u003Cconcise account-listing rationale from the user's request>\"\nramp treasury accounts --agent \\\n  --rationale \"$RATIONALE\"\n```\n\nBefore an amount is selected, present candidate funding sources first and list\naccounts that fail provider, currency, or status requirements separately with the\nexact reason. Show only each account's `name`, `status`, `available_balance`,\n`currency`, and `provider`; never show account numbers or unrelated fields.\n\nAn eligible funding source must be:\n\n- A Ramp Checking account returned by this call\n- Active\n- Denominated in USD\n- Provided by Increase\n- Funded with an `available_balance` at least as large as the requested amount\n\nIf there is no Ramp Checking account, stop and say:\n\n```text\nFunding a Ramp x402 wallet requires a Ramp Checking account. Please open a Ramp\nChecking account in Ramp, then return here to continue setup.\n```\n\nIf eligible accounts exist, let the user select the exact account and USD\namount of at least $1. Never choose for them. After the user names an amount,\nre-sort the accounts: show accounts with sufficient balance first, and list every\nother account separately with `insufficient available balance` or its applicable\nprovider, currency, or status reason. Reject amounts below $1 or above the\nselected account's available balance before confirmation. Show a funding preview:\n\n```text\nFrom: \u003CRamp Checking account name>\nAvailable balance: \u003Cformatted USD balance>\nTo: Ramp x402 wallet \u003Cwallet address>\nAmount: \u003Cformatted USD amount>\nSettlement: may take up to 15 minutes; I will monitor it automatically\n```\n\nAsk for explicit confirmation of those exact details, including the source,\namount, and funding action. Do not fund before that confirmation.\n\n## 4. Fund the wallet\n\nAfter confirmation, generate one UUID locally for this transfer:\n\n```bash\nIDEMPOTENCY_KEY=\"$(python3 -c 'import uuid; print(uuid.uuid4())')\"\nRATIONALE=\"\u003Cconcise funding rationale from the user's exact confirmation>\"\n```\n\nCall the Ramp MCP funding tool with the selected account UUID, exact amount, and\nidempotency key, or run:\n\n```bash\nramp x402 fund \"\u003Csource_wallet_account_uuid>\" \\\n  --amount \"\u003Cconfirmed_usd_amount>\" \\\n  --idempotency_key \"$IDEMPOTENCY_KEY\" \\\n  --rationale \"$RATIONALE\"\n```\n\nKeep the returned `transfer_uuid`, `status`, source, destination, amount, and\ncurrency. Do not report the wallet as funded merely because the transfer was\ncreated.\n\nIf the funding call times out or its response is lost, do not call `x402 fund`\nagain with the same idempotency key. Search all available pages from\n`treasury transfers` and match an entry whose `uuid` equals `IDEMPOTENCY_KEY`;\nthe funding service uses that UUID as the transfer UUID. If found, continue with\nthat transfer's status. If the exact UUID cannot be deterministically\nreconciled, report the uncertain outcome and stop. Do not retry or create\nanother transfer until Ramp confirms whether the original transfer exists.\n\n## 5. Complete any Ramp Checking approval\n\nUse the returned transfer status and the selected Ramp Checking account's\nactivity in Ramp to determine whether its withdrawal needs approval. If Ramp\nshows a pending approval, tell the user the exact account and amount. For a\nbrowser-capable harness, open:\n\n```text\nhttps:\u002F\u002Fapp.ramp.com\u002Fbusiness-accounts\u002F\u003Csource_wallet_account_uuid>\u002Fpending-approvals\n```\n\nReplace `\u003Csource_wallet_account_uuid>` only with the selected account UUID\nreturned by `treasury accounts`. This is account-specific; do not add a\n`business_id` or invent another identifier. Ask the assigned approver to review\nthe withdrawal there. Do not approve on the user's behalf or imply that access\nto the funding tool is approval authority.\n\nWait for the user to confirm that the withdrawal was approved. Then inspect the\ntransfer again with the Ramp Checking transfer-history tool:\n\n```bash\nRATIONALE=\"\u003Cconcise transfer-status rationale from the user's confirmed funding>\"\nramp treasury transfers --agent \\\n  --rationale \"$RATIONALE\"\n```\n\nMatch the funding result's `transfer_uuid` to the transfer history entry's\n`uuid`. If the transfer is still requested, processing, held, or otherwise\nnon-terminal, report that state, wait 15 seconds, and call `treasury transfers`\nagain. Continue polling every 15 seconds for at most 15 minutes (60 checks)\nwithout requiring another user prompt. Only notify the user when the status\nchanges or settlement completes; do not claim the funds are available while the\ntransfer is non-terminal. If the polling window expires, report the exact\ntransfer UUID and current status, then stop and let the user request another\nmonitoring window. If it is rejected, canceled, reversed, blocked, or in error,\nreport the status and stop.\n\n## 6. Confirm setup\n\nWhen the exact transfer is completed, tell the user:\n\n- The x402 wallet address\n- The Ramp Checking account name used\n- The funded USD amount\n- The completed transfer UUID and status\n- That the wallet is ready for an x402 payment\n\nHand off explicitly to `ramp-make-x402-payment`. Suggest discovering services at\n[x402scan.com](https:\u002F\u002Fwww.x402scan.com\u002F), while making clear that a listing is\nnot an approval or guarantee of compatibility: check the service's x402\nchallenge before any payment.\n\nEnd by asking: `If you have feedback on this setup process, tell me now and I can submit it using the Ramp CLI feedback tool.` If the user provides feedback, pass the complete feedback string as one argv value through the runtime's process API; never interpolate it into shell source. For example:\n\n```python\nimport subprocess\n\nsubprocess.run([\"ramp\", \"feedback\", feedback_text], check=True)\n```\n\nHere, `feedback_text` is the user's complete feedback as runtime data, including\nquotes, command substitutions, semicolons, and newlines. Report whether the\nsubmission succeeded.\n","# Set up a Ramp x402 wallet\n\nProvision the business's Ramp-managed Solana wallet and fund it from a Ramp\nChecking account. Ask one question at a time and never guess an account, amount,\npermission, or approval state.\n\n## Safety rules\n\n- Provisioning and funding are separate mutations. Get explicit confirmation\n  immediately before each one.\n- Never ask for passwords, one-time codes, banking credentials, private keys, or\n  wallet signing material. The user completes Ramp sign-in and approvals in\n  Ramp-controlled browser pages.\n- Every Ramp agent-tool call needs a non-empty `rationale`.\n- Generate each rationale from the user's actual request or immediately preceding\n  confirmation. Keep it concise and action-specific; do not reuse a canned\n  rationale sentence.\n- Use only an account UUID returned by `treasury accounts`; never infer or reuse\n  an identifier from another source.\n- Funding is an irreversible transfer from Ramp Checking. Use a new idempotency\n  key for every new transfer. A repeated funding call with the same key does not\n  replay the original result; reconcile an uncertain call before proceeding.\n\n## 1. Update and connect Ramp\n\n### Ramp CLI\n\nInspect the installed CLI:\n\n```bash\nramp --version\nramp update --help\n```\n\nIf the CLI is missing, stop and help the user install it through the trusted\ninstructions at https:\u002F\u002Fagents.ramp.com\u002Fdocs\u002Fcli\u002Foverview. If an update is\navailable, explain that it changes the local CLI installation and ask permission\nbefore running:\n\n```bash\nramp update\n```\n\nAuthenticate in the user-controlled browser and verify the session:\n\n```bash\nramp auth login\nramp auth status\n```\n\nRefresh the generated tool specification, then inspect the live CLI catalog:\n\n```bash\nramp tools refresh\nramp tools list\n```\n\nConfirm that the refreshed CLI exposes `treasury accounts`, `x402 create`, and\n`x402 fund`. Tool presence does not override account permissions; the calls\nbelow remain the source of truth for access.\n\n### Ramp MCP\n\nHave the user update or reconnect the Ramp MCP connector using their MCP\nclient's connection settings, complete Ramp OAuth in the browser, and refresh\nthe client's tool list. Confirm that the connected tool list includes the Ramp\nequivalents of:\n\n- List Ramp Checking accounts (`treasury accounts`)\n- Provision an x402 wallet (`x402 create`)\n- Fund an x402 wallet (`x402 fund`)\n\nIf any required tool is absent, disabled, or returns an authorization,\npermission, scope, or availability error, stop. Tell the user to contact\n[agents@ramp.com](mailto:agents@ramp.com) or visit\n[agents.ramp.com](https:\u002F\u002Fagents.ramp.com\u002F), then reconnect Ramp and try again.\nDo not expose internal rollout names or recommend broader permissions as a\nworkaround.\n\n## 2. Provision the x402 wallet\n\nExplain that Ramp will create a business x402 wallet on Solana and manage its\nsigning securely. Ask:\n\n```text\nAre you an owner or admin of the company's Ramp account, and do you confirm\nthat I should provision the company's Ramp x402 wallet?\n```\n\nOnly after the user confirms their company-level role and provisioning, call the\nRamp MCP tool or run:\n\n```bash\nRATIONALE=\"\u003Cconcise provisioning rationale from the user's confirmation>\"\nramp x402 create --confirmed \\\n  --rationale \"$RATIONALE\"\n```\n\nRecord the returned wallet address and require `status` to be `sign_ready`.\nRepeated calls return the same wallet, but still require confirmation. If Ramp\nreports that provisioning is unavailable or the business setup is incomplete,\nstop and relay the actionable error without retrying.\n\n## 3. Choose a Ramp Checking account and amount\n\nList every Ramp Checking account visible to the user:\n\n```bash\nRATIONALE=\"\u003Cconcise account-listing rationale from the user's request>\"\nramp treasury accounts --agent \\\n  --rationale \"$RATIONALE\"\n```\n\nBefore an amount is selected, present candidate funding sources first and list\naccounts that fail provider, currency, or status requirements separately with the\nexact reason. Show only each account's `name`, `status`, `available_balance`,\n`currency`, and `provider`; never show account numbers or unrelated fields.\n\nAn eligible funding source must be:\n\n- A Ramp Checking account returned by this call\n- Active\n- Denominated in USD\n- Provided by Increase\n- Funded with an `available_balance` at least as large as the requested amount\n\nIf there is no Ramp Checking account, stop and say:\n\n```text\nFunding a Ramp x402 wallet requires a Ramp Checking account. Please open a Ramp\nChecking account in Ramp, then return here to continue setup.\n```\n\nIf eligible accounts exist, let the user select the exact account and USD\namount of at least $1. Never choose for them. After the user names an amount,\nre-sort the accounts: show accounts with sufficient balance first, and list every\nother account separately with `insufficient available balance` or its applicable\nprovider, currency, or status reason. Reject amounts below $1 or above the\nselected account's available balance before confirmation. Show a funding preview:\n\n```text\nFrom: \u003CRamp Checking account name>\nAvailable balance: \u003Cformatted USD balance>\nTo: Ramp x402 wallet \u003Cwallet address>\nAmount: \u003Cformatted USD amount>\nSettlement: may take up to 15 minutes; I will monitor it automatically\n```\n\nAsk for explicit confirmation of those exact details, including the source,\namount, and funding action. Do not fund before that confirmation.\n\n## 4. Fund the wallet\n\nAfter confirmation, generate one UUID locally for this transfer:\n\n```bash\nIDEMPOTENCY_KEY=\"$(python3 -c 'import uuid; print(uuid.uuid4())')\"\nRATIONALE=\"\u003Cconcise funding rationale from the user's exact confirmation>\"\n```\n\nCall the Ramp MCP funding tool with the selected account UUID, exact amount, and\nidempotency key, or run:\n\n```bash\nramp x402 fund \"\u003Csource_wallet_account_uuid>\" \\\n  --amount \"\u003Cconfirmed_usd_amount>\" \\\n  --idempotency_key \"$IDEMPOTENCY_KEY\" \\\n  --rationale \"$RATIONALE\"\n```\n\nKeep the returned `transfer_uuid`, `status`, source, destination, amount, and\ncurrency. Do not report the wallet as funded merely because the transfer was\ncreated.\n\nIf the funding call times out or its response is lost, do not call `x402 fund`\nagain with the same idempotency key. Search all available pages from\n`treasury transfers` and match an entry whose `uuid` equals `IDEMPOTENCY_KEY`;\nthe funding service uses that UUID as the transfer UUID. If found, continue with\nthat transfer's status. If the exact UUID cannot be deterministically\nreconciled, report the uncertain outcome and stop. Do not retry or create\nanother transfer until Ramp confirms whether the original transfer exists.\n\n## 5. Complete any Ramp Checking approval\n\nUse the returned transfer status and the selected Ramp Checking account's\nactivity in Ramp to determine whether its withdrawal needs approval. If Ramp\nshows a pending approval, tell the user the exact account and amount. For a\nbrowser-capable harness, open:\n\n```text\nhttps:\u002F\u002Fapp.ramp.com\u002Fbusiness-accounts\u002F\u003Csource_wallet_account_uuid>\u002Fpending-approvals\n```\n\nReplace `\u003Csource_wallet_account_uuid>` only with the selected account UUID\nreturned by `treasury accounts`. This is account-specific; do not add a\n`business_id` or invent another identifier. Ask the assigned approver to review\nthe withdrawal there. Do not approve on the user's behalf or imply that access\nto the funding tool is approval authority.\n\nWait for the user to confirm that the withdrawal was approved. Then inspect the\ntransfer again with the Ramp Checking transfer-history tool:\n\n```bash\nRATIONALE=\"\u003Cconcise transfer-status rationale from the user's confirmed funding>\"\nramp treasury transfers --agent \\\n  --rationale \"$RATIONALE\"\n```\n\nMatch the funding result's `transfer_uuid` to the transfer history entry's\n`uuid`. If the transfer is still requested, processing, held, or otherwise\nnon-terminal, report that state, wait 15 seconds, and call `treasury transfers`\nagain. Continue polling every 15 seconds for at most 15 minutes (60 checks)\nwithout requiring another user prompt. Only notify the user when the status\nchanges or settlement completes; do not claim the funds are available while the\ntransfer is non-terminal. If the polling window expires, report the exact\ntransfer UUID and current status, then stop and let the user request another\nmonitoring window. If it is rejected, canceled, reversed, blocked, or in error,\nreport the status and stop.\n\n## 6. Confirm setup\n\nWhen the exact transfer is completed, tell the user:\n\n- The x402 wallet address\n- The Ramp Checking account name used\n- The funded USD amount\n- The completed transfer UUID and status\n- That the wallet is ready for an x402 payment\n\nHand off explicitly to `ramp-make-x402-payment`. Suggest discovering services at\n[x402scan.com](https:\u002F\u002Fwww.x402scan.com\u002F), while making clear that a listing is\nnot an approval or guarantee of compatibility: check the service's x402\nchallenge before any payment.\n\nEnd by asking: `If you have feedback on this setup process, tell me now and I can submit it using the Ramp CLI feedback tool.` If the user provides feedback, pass the complete feedback string as one argv value through the runtime's process API; never interpolate it into shell source. For example:\n\n```python\nimport subprocess\n\nsubprocess.run([\"ramp\", \"feedback\", feedback_text], check=True)\n```\n\nHere, `feedback_text` is the user's complete feedback as runtime data, including\nquotes, command substitutions, semicolons, and newlines. Report whether the\nsubmission succeeded.\n",{"area":24,"name":5,"description":7,"compatibility":25,"supported_surfaces":26},"Agentic Commerce","Requires a user who is an owner or admin of the company's Ramp account with Ramp Checking access, an up-to-date Ramp CLI or Ramp MCP connection, Python 3, and browser access for OAuth and any required withdrawal approval.",[27,28,29],"browser","cli","mcp","main","9836d94e88404aabb682086405c2aa9cba7657ac","plugins\u002Framp\u002Fskills\u002Framp-setup-x402-wallet",156,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace","https:\u002F\u002Fgithub.com\u002FCognitionAI","https:\u002F\u002Fcognition.ai\u002F","Makers of Devin, the AI software engineer.","2026-11-13 07:08:23",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add CognitionAI\u002Fdevin-marketplace --skill ramp-setup-x402-wallet",{"tool":45,"command":46},"bunx","bunx skills add CognitionAI\u002Fdevin-marketplace --skill ramp-setup-x402-wallet",{"tool":48,"command":49},"pnpm","pnpm dlx skills add CognitionAI\u002Fdevin-marketplace --skill ramp-setup-x402-wallet","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Framp\u002Fskills\u002Framp-setup-x402-wallet\u002FSKILL.md",true,[],[54,60,67,73,80,87],{"skillNo":55,"name":56,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7BYC4AJGM98P2G9JH7QS24Z","business-data","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fwindsor-ai\u002Fskills\u002Fbusiness-data\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M7BYBZ0CD4CBCPZHRZ551BNK","workflow","Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of \"workflow\", \"durable functions\", \"resumable\", \"workflow sdk\", \"queue\", \"event\", \"push\", \"subscribe\", or step-based orchestration.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\u002Fupstream\u002FSKILL.md",[],[],{"skillNo":68,"name":62,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M7BYB1XSZHKHD8JZTQJ62JN0","Vercel Workflow SDK expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause\u002Fresume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fworkflow\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M7BYASGMK935J33E21N5WTW0","verification","Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fverification\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M7BY9WJERKSKEH9HK6E71GW2","vercel-storage","Vercel storage expert guidance — Blob, Global Config (formerly Edge Config), and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-storage\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M7BY9N034894YV2J9DCRZHYS","vercel-services","Configure and troubleshoot Vercel Services for multiple frontends and backends in one project. Use when composing a polyglot or multi-service application on one Vercel deployment; defining the `services` key, service-targeted rewrites, or service bindings in `vercel.json`; or running all services with `vercel dev`.","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fvercel\u002Fskills\u002Fvercel-services\u002FSKILL.md",[],[]]