[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BXPFQBDB86SWQ64Y5X26YT":3,"skill-same:01M7BXPFQBDB86SWQ64Y5X26YT":51},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7BXPFQBDB86SWQ64Y5X26YT","ramp-submit-reimbursement",null,"Submit an out-of-pocket reimbursement from a receipt. Use when: 'submit reimbursement',\n'reimburse me', 'I paid out of pocket', 'expense a receipt', 'file reimbursement',\n'OOP expense', 'I bought something for work'. Do NOT use for: approving reimbursements\n(use ramp-approval-dashboard), uploading receipts to card transactions (use ramp-complete-expenses),\nor editing existing reimbursements.","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-submit-reimbursement\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ramp-submit-reimbursement\narea: Reimbursements\nsupported_surfaces: [cli, mcp]\ndescription: |-\n  Submit an out-of-pocket reimbursement from a receipt. Use when: 'submit reimbursement',\n  'reimburse me', 'I paid out of pocket', 'expense a receipt', 'file reimbursement',\n  'OOP expense', 'I bought something for work'. Do NOT use for: approving reimbursements\n  (use ramp-approval-dashboard), uploading receipts to card transactions (use ramp-complete-expenses),\n  or editing existing reimbursements.\n---\n\n## Non-Negotiables\n\n- **Pass `--rationale` on every command** — it is a required field on these agent-tools (a non-empty string, max 1024 chars). With `--json`, supply it as a `\"rationale\"` key in the body. Omitting it returns `HTTP 422 (DEVELOPER_INVALID_SCHEMA)`, in both agent and human modes.\n- Never submit without confirming the details with the user first. Show amount and currency, merchant, memo, fund, and accounting categories before submitting.\n- Receipts must be **base64-encoded** for upload. Accepted types: PNG, JPEG, PDF, HEIC, WEBP.\n- All CLI flags use **underscores**, not hyphens (e.g., `--fund_uuid`, `--page_size`).\n- Reimbursement amounts use major units in the draft's existing currency (for example, `42.50` means EUR 42.50 for a EUR draft, not cents). An amount-only edit preserves the existing currency.\n- After editing, always check `missing_items` in the response. Do not submit until all required items are resolved.\n\n## Workflow\n\n### Step 1: Upload the receipt\n\nThe user must provide a receipt file. Base64-encode and upload it:\n\n```bash\n# Encode the file\nbase64 -i \u002Fpath\u002Fto\u002Freceipt.pdf | tr -d '\\n'\n\n# Upload (no --transaction_uuid — this is for a new reimbursement, not a card transaction)\nramp receipts upload \\\n  --content_type \"application\u002Fpdf\" \\\n  --filename \"receipt.pdf\" \\\n  --file_content_base64 \"{base64_string}\" --rationale \"Upload the receipt\"\n```\n\nResponse returns `receipt_uuid`. Save it for the next step.\n\n### Step 2: Create a draft reimbursement from the receipt\n\n```bash\nramp reimbursements create {receipt_uuid} --rationale \"Create the reimbursement from the receipt\"\n```\n\nResponse returns:\n- `reimbursement_uuid` — the draft reimbursement ID\n- `suggested_memos` — AI-generated memo suggestions based on the receipt\n- `suggested_codings` — suggested accounting category selections\n- `suggested_funds` — suggested spend allocations to charge\n- `missing_items` — what still needs to be filled in before submission\n- `reimbursement_link` — direct link to view in the Ramp app\n\n### Step 3: Fill in required fields\n\nCheck `missing_items` from the create response. Common required fields:\n\n| Missing item | How to fill |\n|---|---|\n| `missing_memo: true` | Edit with `--memo` |\n| `missing_fund: true` | Edit with `--fund_uuid` (pick from `suggested_funds` or list funds) |\n| `missing_tracking_categories` (non-empty) | Edit with `--json` to set category selections |\n| `missing_receipt: true` | Should not happen if you created from a receipt |\n\nUse suggestions from the create response when available:\n\n```bash\n# Set memo and fund from suggestions\nramp reimbursements edit {reimbursement_uuid} \\\n  --memo \"Coffee with client\" \\\n  --fund_uuid \"{suggested_fund_uuid}\" --rationale \"Update the reimbursement for the user\"\n```\n\nIf the receipt amount is wrong, correct it while the reimbursement is still in `DRAFT`. Use the draft's existing currency shown in the tool response:\n\n```bash\n# For a draft whose existing currency is EUR\nramp reimbursements edit {reimbursement_uuid} \\\n  --amount 42.50 --rationale \"Correct the reimbursement amount for the user\"\n```\n\nAmounts must be positive values in the existing draft currency; `--amount` alone does not change the currency. After editing, check `missing_items` as usual and show both the corrected amount and currency in the final confirmation before submitting.\n\nFor tracking categories, use `--json`:\n\n```bash\nramp reimbursements edit {reimbursement_uuid} --json '{\n  \"rationale\": \"Update the reimbursement for the user\",\n  \"reimbursement_uuid\": \"{uuid}\",\n  \"tracking_category_selections\": [\n    {\n      \"category_uuid\": \"{category_uuid}\",\n      \"option_uuid\": \"{option_uuid}\"\n    }\n  ]\n}'\n```\n\nIf no suggestions are available for the fund, list the user's funds:\n\n```bash\nramp funds list --agent --rationale \"List the user's funds\"\n```\n\n**After each edit**, check the response's `missing_items`. Repeat until all required items are resolved (all `false` \u002F empty).\n\n### Step 4: Confirm with the user\n\nPresent the complete reimbursement before submitting:\n\n```\nReady to submit:\n  Amount:    USD 42.50\n  Merchant:  Blue Bottle Coffee\n  Memo:      Coffee with client — discussed Q2 roadmap\n  Fund:      Social bonding & Team outings 2026\n  Category:  70103 - Company Meals\n  Receipt:   attached\n\nSubmit for approval?\n```\n\n### Step 5: Submit\n\n```bash\nramp reimbursements submit {reimbursement_uuid} --rationale \"Submit the reimbursement\"\n```\n\nResponse returns `reimbursement_uuid` and `error_message` (null on success).\n\nAfter submitting, tell the user:\n- The reimbursement has been submitted for approval\n- Link to view it: the `reimbursement_link` from the create\u002Fedit response\n- They'll be notified when it's approved\n\n## Editing After Rejection\n\nIf a reimbursement was rejected and the user wants to fix and resubmit:\n\n```bash\n# Revert to draft\nramp reimbursements resubmit {reimbursement_uuid} --rationale \"Resubmit the reimbursement\"\n\n# Edit as needed\nramp reimbursements edit {reimbursement_uuid} --memo \"Updated memo with details\" --rationale \"Update the reimbursement for the user\"\n\n# Submit again\nramp reimbursements submit {reimbursement_uuid} --rationale \"Submit the reimbursement\"\n```\n\n## Duplicating a Previous Reimbursement\n\n`ramp reimbursements duplicate` exists, but it is not a complete CLI path for a new receipt-backed reimbursement.\nThe duplicate keeps the prior coding context, but it does **not** copy the receipt, and the CLI cannot attach a new receipt to that duplicated draft afterward.\n\nIf the user needs to submit a new reimbursement with a new receipt, the executable CLI path is:\n\n```bash\n# Find a previous reimbursement to reference\nramp reimbursements list --reimbursements_to_retrieve my_reimbursements --page_size 10 --rationale \"List the user's reimbursements\"\n\n# Duplicate exists, but the draft will still be missing a receipt\nramp reimbursements duplicate {previous_reimbursement_uuid} --rationale \"Duplicate the reimbursement\"\n\n# Upload the new receipt\nramp receipts upload --content_type \"image\u002Fjpeg\" --filename \"gym-apr.jpg\" \\\n  --file_content_base64 \"{base64}\" --rationale \"Upload the receipt\"\n\n# Create a fresh reimbursement from that receipt\nramp reimbursements create {receipt_uuid} --rationale \"Create the reimbursement from the receipt\"\n\n# Re-apply memo, fund, and tracking categories, then submit\nramp reimbursements edit {reimbursement_uuid} --memo \"Monthly gym membership\" --rationale \"Update the reimbursement for the user\"\nramp reimbursements submit {reimbursement_uuid} --rationale \"Submit the reimbursement\"\n```\n\nDo not imply that a new receipt can be attached to the duplicated reimbursement via CLI. `receipts attach` is for card transactions only, and `submit` can fail with \"receipt must be specified\" if the duplicate has no receipt.\n\n## Example Session\n\n```\nUser: I bought coffee for a meeting yesterday, here's the receipt ~\u002FDownloads\u002Fbluebottle.jpg\n\nAgent: Let me upload that receipt and create a reimbursement.\n> base64 -i ~\u002FDownloads\u002Fbluebottle.jpg | tr -d '\\n'\n> ramp receipts upload --content_type \"image\u002Fjpeg\" --filename \"bluebottle.jpg\" \\\n>   --file_content_base64 \"{base64}\" --rationale \"Upload the receipt\"\n\nReceipt uploaded (receipt_uuid: `\u003Creceipt_id>`).\n\n> ramp reimbursements create \u003Creceipt_id> --rationale \"Create the reimbursement from the receipt\"\n\nDraft created. The receipt shows Blue Bottle Coffee, $12.50.\nSuggested memos: \"Coffee at Blue Bottle for team meeting\"\nSuggested fund: \"Social bonding & Team outings 2026\"\nMissing: memo, fund, Category (GL account)\n\nLet me fill in the details using the suggestions:\n> ramp reimbursements edit \u003Creimbursement_id> \\\n>   --memo \"Coffee at Blue Bottle for team meeting\" \\\n>   --fund_uuid \"\u003Cfund_id>\" --rationale \"Update the reimbursement for the user\"\n\nAll required items resolved. Ready to submit:\n  Amount:    USD 12.50\n  Merchant:  Blue Bottle Coffee\n  Memo:      Coffee at Blue Bottle for team meeting\n  Fund:      Social bonding & Team outings 2026\n  Category:  70103 - Company Meals\n  Receipt:   attached\n\nSubmit for approval?\n\nUser: yes\n\nAgent: > ramp reimbursements submit \u003Creimbursement_id> --rationale \"User confirmed submitting the USD 12.50 Blue Bottle reimbursement for approval\"\nSubmitted! Your reimbursement is now pending approval.\nView it using the `reimbursement_link` returned by Ramp.\n```\n\n## When NOT to Use\n\n- **Approving reimbursements** — use ramp-approval-dashboard\n- **Uploading receipts to card transactions, or editing their memos\u002Fcategories** — use ramp-complete-expenses\n- **Canceling an approved reimbursement** — tell the user to contact their manager or use the Ramp app\n\n## Gotchas\n\n| Issue | Fix |\n|---|---|\n| `create` requires a `receipt_uuid` | Always upload the receipt first, then create |\n| `duplicate` does not copy receipts | Upload a new receipt separately, or use `create` from a receipt instead |\n| `receipts attach` is for card transactions only | For reimbursements, use `create {receipt_uuid}` to attach at creation time |\n| Submit fails with \"receipt must be specified\" | The reimbursement was created without a receipt (e.g., via `duplicate`). Create a new one from a receipt instead. |\n| `missing_tracking_categories` has entries | Use `--json` with `tracking_category_selections` to set them. Each entry in the missing list shows the `category_uuid` and `category_name` needed. |\n| `suggested_funds` may be empty | Fall back to `ramp funds list` to find available funds |\n| Large receipt files hit shell arg limits | For files >100KB, write base64 to a temp file and read it into the `--file_content_base64` flag |\n| Amount edit fails | Amount must be a positive value and can only be edited while the reimbursement is in `DRAFT`. `--amount` preserves the draft's existing currency, so use major units in that currency, then check `missing_items` and confirm both amount and currency before submitting. |\n","## Non-Negotiables\n\n- **Pass `--rationale` on every command** — it is a required field on these agent-tools (a non-empty string, max 1024 chars). With `--json`, supply it as a `\"rationale\"` key in the body. Omitting it returns `HTTP 422 (DEVELOPER_INVALID_SCHEMA)`, in both agent and human modes.\n- Never submit without confirming the details with the user first. Show amount and currency, merchant, memo, fund, and accounting categories before submitting.\n- Receipts must be **base64-encoded** for upload. Accepted types: PNG, JPEG, PDF, HEIC, WEBP.\n- All CLI flags use **underscores**, not hyphens (e.g., `--fund_uuid`, `--page_size`).\n- Reimbursement amounts use major units in the draft's existing currency (for example, `42.50` means EUR 42.50 for a EUR draft, not cents). An amount-only edit preserves the existing currency.\n- After editing, always check `missing_items` in the response. Do not submit until all required items are resolved.\n\n## Workflow\n\n### Step 1: Upload the receipt\n\nThe user must provide a receipt file. Base64-encode and upload it:\n\n```bash\n# Encode the file\nbase64 -i \u002Fpath\u002Fto\u002Freceipt.pdf | tr -d '\\n'\n\n# Upload (no --transaction_uuid — this is for a new reimbursement, not a card transaction)\nramp receipts upload \\\n  --content_type \"application\u002Fpdf\" \\\n  --filename \"receipt.pdf\" \\\n  --file_content_base64 \"{base64_string}\" --rationale \"Upload the receipt\"\n```\n\nResponse returns `receipt_uuid`. Save it for the next step.\n\n### Step 2: Create a draft reimbursement from the receipt\n\n```bash\nramp reimbursements create {receipt_uuid} --rationale \"Create the reimbursement from the receipt\"\n```\n\nResponse returns:\n- `reimbursement_uuid` — the draft reimbursement ID\n- `suggested_memos` — AI-generated memo suggestions based on the receipt\n- `suggested_codings` — suggested accounting category selections\n- `suggested_funds` — suggested spend allocations to charge\n- `missing_items` — what still needs to be filled in before submission\n- `reimbursement_link` — direct link to view in the Ramp app\n\n### Step 3: Fill in required fields\n\nCheck `missing_items` from the create response. Common required fields:\n\n| Missing item | How to fill |\n|---|---|\n| `missing_memo: true` | Edit with `--memo` |\n| `missing_fund: true` | Edit with `--fund_uuid` (pick from `suggested_funds` or list funds) |\n| `missing_tracking_categories` (non-empty) | Edit with `--json` to set category selections |\n| `missing_receipt: true` | Should not happen if you created from a receipt |\n\nUse suggestions from the create response when available:\n\n```bash\n# Set memo and fund from suggestions\nramp reimbursements edit {reimbursement_uuid} \\\n  --memo \"Coffee with client\" \\\n  --fund_uuid \"{suggested_fund_uuid}\" --rationale \"Update the reimbursement for the user\"\n```\n\nIf the receipt amount is wrong, correct it while the reimbursement is still in `DRAFT`. Use the draft's existing currency shown in the tool response:\n\n```bash\n# For a draft whose existing currency is EUR\nramp reimbursements edit {reimbursement_uuid} \\\n  --amount 42.50 --rationale \"Correct the reimbursement amount for the user\"\n```\n\nAmounts must be positive values in the existing draft currency; `--amount` alone does not change the currency. After editing, check `missing_items` as usual and show both the corrected amount and currency in the final confirmation before submitting.\n\nFor tracking categories, use `--json`:\n\n```bash\nramp reimbursements edit {reimbursement_uuid} --json '{\n  \"rationale\": \"Update the reimbursement for the user\",\n  \"reimbursement_uuid\": \"{uuid}\",\n  \"tracking_category_selections\": [\n    {\n      \"category_uuid\": \"{category_uuid}\",\n      \"option_uuid\": \"{option_uuid}\"\n    }\n  ]\n}'\n```\n\nIf no suggestions are available for the fund, list the user's funds:\n\n```bash\nramp funds list --agent --rationale \"List the user's funds\"\n```\n\n**After each edit**, check the response's `missing_items`. Repeat until all required items are resolved (all `false` \u002F empty).\n\n### Step 4: Confirm with the user\n\nPresent the complete reimbursement before submitting:\n\n```\nReady to submit:\n  Amount:    USD 42.50\n  Merchant:  Blue Bottle Coffee\n  Memo:      Coffee with client — discussed Q2 roadmap\n  Fund:      Social bonding & Team outings 2026\n  Category:  70103 - Company Meals\n  Receipt:   attached\n\nSubmit for approval?\n```\n\n### Step 5: Submit\n\n```bash\nramp reimbursements submit {reimbursement_uuid} --rationale \"Submit the reimbursement\"\n```\n\nResponse returns `reimbursement_uuid` and `error_message` (null on success).\n\nAfter submitting, tell the user:\n- The reimbursement has been submitted for approval\n- Link to view it: the `reimbursement_link` from the create\u002Fedit response\n- They'll be notified when it's approved\n\n## Editing After Rejection\n\nIf a reimbursement was rejected and the user wants to fix and resubmit:\n\n```bash\n# Revert to draft\nramp reimbursements resubmit {reimbursement_uuid} --rationale \"Resubmit the reimbursement\"\n\n# Edit as needed\nramp reimbursements edit {reimbursement_uuid} --memo \"Updated memo with details\" --rationale \"Update the reimbursement for the user\"\n\n# Submit again\nramp reimbursements submit {reimbursement_uuid} --rationale \"Submit the reimbursement\"\n```\n\n## Duplicating a Previous Reimbursement\n\n`ramp reimbursements duplicate` exists, but it is not a complete CLI path for a new receipt-backed reimbursement.\nThe duplicate keeps the prior coding context, but it does **not** copy the receipt, and the CLI cannot attach a new receipt to that duplicated draft afterward.\n\nIf the user needs to submit a new reimbursement with a new receipt, the executable CLI path is:\n\n```bash\n# Find a previous reimbursement to reference\nramp reimbursements list --reimbursements_to_retrieve my_reimbursements --page_size 10 --rationale \"List the user's reimbursements\"\n\n# Duplicate exists, but the draft will still be missing a receipt\nramp reimbursements duplicate {previous_reimbursement_uuid} --rationale \"Duplicate the reimbursement\"\n\n# Upload the new receipt\nramp receipts upload --content_type \"image\u002Fjpeg\" --filename \"gym-apr.jpg\" \\\n  --file_content_base64 \"{base64}\" --rationale \"Upload the receipt\"\n\n# Create a fresh reimbursement from that receipt\nramp reimbursements create {receipt_uuid} --rationale \"Create the reimbursement from the receipt\"\n\n# Re-apply memo, fund, and tracking categories, then submit\nramp reimbursements edit {reimbursement_uuid} --memo \"Monthly gym membership\" --rationale \"Update the reimbursement for the user\"\nramp reimbursements submit {reimbursement_uuid} --rationale \"Submit the reimbursement\"\n```\n\nDo not imply that a new receipt can be attached to the duplicated reimbursement via CLI. `receipts attach` is for card transactions only, and `submit` can fail with \"receipt must be specified\" if the duplicate has no receipt.\n\n## Example Session\n\n```\nUser: I bought coffee for a meeting yesterday, here's the receipt ~\u002FDownloads\u002Fbluebottle.jpg\n\nAgent: Let me upload that receipt and create a reimbursement.\n> base64 -i ~\u002FDownloads\u002Fbluebottle.jpg | tr -d '\\n'\n> ramp receipts upload --content_type \"image\u002Fjpeg\" --filename \"bluebottle.jpg\" \\\n>   --file_content_base64 \"{base64}\" --rationale \"Upload the receipt\"\n\nReceipt uploaded (receipt_uuid: `\u003Creceipt_id>`).\n\n> ramp reimbursements create \u003Creceipt_id> --rationale \"Create the reimbursement from the receipt\"\n\nDraft created. The receipt shows Blue Bottle Coffee, $12.50.\nSuggested memos: \"Coffee at Blue Bottle for team meeting\"\nSuggested fund: \"Social bonding & Team outings 2026\"\nMissing: memo, fund, Category (GL account)\n\nLet me fill in the details using the suggestions:\n> ramp reimbursements edit \u003Creimbursement_id> \\\n>   --memo \"Coffee at Blue Bottle for team meeting\" \\\n>   --fund_uuid \"\u003Cfund_id>\" --rationale \"Update the reimbursement for the user\"\n\nAll required items resolved. Ready to submit:\n  Amount:    USD 12.50\n  Merchant:  Blue Bottle Coffee\n  Memo:      Coffee at Blue Bottle for team meeting\n  Fund:      Social bonding & Team outings 2026\n  Category:  70103 - Company Meals\n  Receipt:   attached\n\nSubmit for approval?\n\nUser: yes\n\nAgent: > ramp reimbursements submit \u003Creimbursement_id> --rationale \"User confirmed submitting the USD 12.50 Blue Bottle reimbursement for approval\"\nSubmitted! Your reimbursement is now pending approval.\nView it using the `reimbursement_link` returned by Ramp.\n```\n\n## When NOT to Use\n\n- **Approving reimbursements** — use ramp-approval-dashboard\n- **Uploading receipts to card transactions, or editing their memos\u002Fcategories** — use ramp-complete-expenses\n- **Canceling an approved reimbursement** — tell the user to contact their manager or use the Ramp app\n\n## Gotchas\n\n| Issue | Fix |\n|---|---|\n| `create` requires a `receipt_uuid` | Always upload the receipt first, then create |\n| `duplicate` does not copy receipts | Upload a new receipt separately, or use `create` from a receipt instead |\n| `receipts attach` is for card transactions only | For reimbursements, use `create {receipt_uuid}` to attach at creation time |\n| Submit fails with \"receipt must be specified\" | The reimbursement was created without a receipt (e.g., via `duplicate`). Create a new one from a receipt instead. |\n| `missing_tracking_categories` has entries | Use `--json` with `tracking_category_selections` to set them. Each entry in the missing list shows the `category_uuid` and `category_name` needed. |\n| `suggested_funds` may be empty | Fall back to `ramp funds list` to find available funds |\n| Large receipt files hit shell arg limits | For files >100KB, write base64 to a temp file and read it into the `--file_content_base64` flag |\n| Amount edit fails | Amount must be a positive value and can only be edited while the reimbursement is in `DRAFT`. `--amount` preserves the draft's existing currency, so use major units in that currency, then check `missing_items` and confirm both amount and currency before submitting. |\n",{"area":24,"name":5,"description":7,"supported_surfaces":25},"Reimbursements",[26,27],"cli","mcp","main","9836d94e88404aabb682086405c2aa9cba7657ac","plugins\u002Framp\u002Fskills\u002Framp-submit-reimbursement",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":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add CognitionAI\u002Fdevin-marketplace --skill ramp-submit-reimbursement",{"tool":43,"command":44},"bunx","bunx skills add CognitionAI\u002Fdevin-marketplace --skill ramp-submit-reimbursement",{"tool":46,"command":47},"pnpm","pnpm dlx skills add CognitionAI\u002Fdevin-marketplace --skill ramp-submit-reimbursement","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Framp\u002Fskills\u002Framp-submit-reimbursement\u002FSKILL.md",true,[],[52,58,65,71,78,85],{"skillNo":53,"name":54,"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":55,"categories":56,"keywords":57,"publishedAt":19},"01M7BYC4AJGM98P2G9JH7QS24Z","business-data","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fwindsor-ai\u002Fskills\u002Fbusiness-data\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":60,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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",[],[]]