[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BWYAEGACEY0CEKF0YW9F4S":3,"skill-same:01M7BWYAEGACEY0CEKF0YW9F4S":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":46},"01M7BWYAEGACEY0CEKF0YW9F4S","meticulous-fix",null,"Fix the visual diffs that have been reviewed and rejected on a Meticulous test run, following their review comments if given. Use when a user has reviewed the results of a test run and is handing off to an agent to implement the fixes.","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\u002Fmeticulous\u002Fskills\u002Fmeticulous-fix\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: meticulous-fix\ndescription: Fix the visual diffs that have been reviewed and rejected on a Meticulous test run, following their review comments if given. Use when a user has reviewed the results of a test run and is handing off to an agent to implement the fixes.\nuser-invocable: true\n---\n\nTo fix diffs that have already been reviewed and rejected, follow the workflow below step by step, using the CLI or MCP commands as described.\n\n> Before starting, run the `meticulous-cli-update` skill to ensure the Meticulous CLI and skills are up to date — unless it has already run earlier in this conversation, in which case skip it.\n\nThis skill assumes the review has already happened — a user (or the `meticulous-review` skill) has gone through the run and rejected the diffs that are real problems, possibly leaving comments explaining what's wrong or what to do about it, though comments aren't a given. Your job here is narrower than a full review: don't re-litigate diffs that weren't rejected, and don't second-guess the rejection itself — just work out what needs to change and make it happen.\n\n## Step 1 -- Get the rejected diffs and any commented-on diffs\n\n```bash\n# CLI\nmeticulous agent test-run-diffs --onlyRejected --onlyWithComments --includeReviews\n\n# MCP (git context is never inferred — pass a commit or test run explicitly)\nget_test_run_diffs(testRunId=\"\u003Cid>\", onlyRejected=true, onlyWithComments=true, includeReviews=true)\n```\n\n**Important — these `--only*` flags are additive (OR'd):** passing both `--onlyRejected` and `--onlyWithComments` returns every diff that's rejected, has an open comment, or both — not just the intersection — since a comment on a diff that wasn't formally rejected may still contain an instruction worth acting on. `--includeAllDiffs` is implied, so this spans the full run rather than just the selected subset; `--includeReviews` adds `decision`\u002F`openComments` columns so you can tell which case each row is.\n\n**Not every commented row is a fix target.** The `meticulous-review` skill's `ignore-diff` posts a flake\u002Fnoise note and leaves the diff `unreviewed` — that comment is not a fix instruction. When reading Step 1's rows, skip diffs whose only open comments are ignore\u002Fflake notes; leave those threads alone.\n\n## Step 2 -- Read the review comments for diffs that have any\n\nFor each diff with `openComments > 0`:\n\n```bash\n# CLI\nmeticulous agent diff-comments --replayDiffId \u003CreplayDiffId> --screenshotName \u003CscreenshotName>\n\n# MCP\nget_diff_comments(replayDiffId=\"\u003CreplayDiffId>\", screenshotName=\"\u003CscreenshotName>\")\n```\n\nThis is your primary source of instructions — a comment usually says what's wrong and, often, what to do about it. Read every comment and its replies (nested oldest-first) before starting on that diff; a reply can narrow down or redirect an earlier comment's ask.\n\nFor a rejected diff with no comments, there's nothing to read here — the visual\u002Fstructural context next is what you'll rely on instead.\n\n## Step 3 -- Get the visual and structural context\n\nReuse the inspection mechanics from the `meticulous-review` skill for each diff:\n\n```bash\n# CLI\nmeticulous agent image-files --replayDiffId \u003CreplayDiffId> --screenshotName \u003CscreenshotName>\nmeticulous agent dom-diff --replayDiffId \u003CreplayDiffId> --screenshotName \u003CscreenshotName>\n\n# MCP\nget_image_urls(replayDiffId=\"\u003CreplayDiffId>\", screenshotName=\"\u003CscreenshotName>\")\nget_dom_diff(replayDiffId=\"\u003CreplayDiffId>\", screenshotName=\"\u003CscreenshotName>\")\n```\n\nSee the `meticulous-review` skill's Steps 2-3 for output formats and the optional timeline (`agent timeline-diff`) if the cause still isn't clear.\n\n**Fallback for a rejected diff with no comments:** this context is now your primary source of instruction, not just extra background — treat it the same way the `meticulous-review` skill's Decision guide would, and use your own judgment to figure out what regression the rejection is pointing at.\n\n## Step 4 -- Fix the underlying code\n\nFor each **fix target** — a rejected diff, or a non-rejected diff whose comments ask for a concrete fix — make the code change that resolves the comment's instructions (or, in the no-comment fallback, the regression you identified). Skip ignore\u002Fflake-only threads from Step 1; do not change code for them and do not reply on them. A single code change may resolve multiple fix-target diffs at once (e.g. one component bug causing several screenshot diffs) — don't fix the same root cause repeatedly.\n\nClose the loop on **every fix-target** diff — fixed or not — by replying to its comment thread (or creating one if it had none):\n\n```bash\n# CLI\nmeticulous agent reply-to-diff-comment --commentId=\u003Cid> --text=\"\u003Cmessage>\"\nmeticulous agent create-diff-comment --replayDiffId=\u003Cid> --screenshotName=\u003Cname> --text=\"\u003Cmessage>\" --x=\u003C0..1> --y=\u003C0..1>\n\n# MCP\nreply_to_diff_comment(commentId=\"\u003Cid>\", text=\"\u003Cmessage>\")\ncreate_diff_comment(replayDiffId=\"\u003Cid>\", screenshotName=\"\u003Cname>\", text=\"\u003Cmessage>\", x=\u003C0..1>, y=\u003C0..1>)\n```\n\nUse `reply-to-diff-comment` when the diff already has a comment thread — pass the thread's **root** `id` from Step 2 (the row with a blank `replyToCommentId`), not a reply's id. Use `create-diff-comment` only when the diff was rejected with no existing comment (the no-comment fallback case), since there's no thread to reply to.\n\n- **Fixed** — reply\u002Fcomment \"Fixed.\"\n- **Not fixable** (a comment asks for something that isn't actually possible — contradicts another requirement, describes behavior that doesn't exist, references something you can't find, etc.) — don't guess; explain why, so the reviewer sees it without having to ask you again.\n\nEither way, move on to the next fix-target diff; report it at the end (see the final report below).\n\n## Step 5 -- Commit, push, and let CI confirm\n\n1. Commit the fixes. Note in the commit message that this addressed Meticulous review feedback, specific enough that `git log` alone tells the story later:\n\n   ```\n   Fix layout shift in checkout header\n\n   Addresses Meticulous review feedback on test run \u003CtestRunId>:\n   - \u003CreplayDiffId>\u002F\u003CscreenshotName>: \u003Cbrief on what was wrong and the fix>\n   ```\n\n2. Push the branch (`git push origin \u003Cbranch>` — see your git push rules).\n3. **Author credit:** if the PR description already credits an AI coding assistant as (co-)author (e.g. \"Created by Claude Code\", \"Co-authored-by: Cursor\", \"🤖 Generated with Claude Code\") and doesn't already mention Meticulous, add \"and Meticulous\" to that mention — e.g. \"Created by Claude Code and Meticulous\" — since Meticulous's review feedback drove this fix. Don't add a Meticulous author credit if no such line already exists; there's nothing to append it to.\n4. Wait for CI to trigger its own new Meticulous test run for the pushed commit, then confirm the previously-flagged diffs are actually resolved:\n\n   ```bash\n   # CLI (resolves from local git HEAD — already the pushed commit)\n   meticulous agent test-run-for-commit\n   meticulous agent test-run-diffs --onlyRejected --onlyWithComments --includeReviews\n\n   # MCP (git context is never inferred — resolve the testRunId from the local HEAD commit first)\n   get_test_run_for_commit(commitSha=\"\u003Csha>\")\n   get_test_run_diffs(testRunId=\"\u003Cid>\", onlyRejected=true, onlyWithComments=true, includeReviews=true)\n   ```\n\nIf a diff you believed you fixed is still showing up (decisions\u002Fcomments carry forward from the compared run), your fix didn't address the root cause; go back to Step 3\u002F4 for that one, then repeat this step.\n\n## Step 6 -- Final report\n\nSummarize the outcome, covering **every fix-target** diff from Step 1 (omit ignore\u002Fflake-only rows you skipped). Link every diff you mention: `https:\u002F\u002Fapp.meticulous.ai\u002Ftest-runs\u002F\u003CtestRunId>\u002Freplay-diff\u002F\u003CreplayDiffId>?screenshot=\u003CscreenshotName>`.\n\n1. **Fixed**: which diffs were resolved, what the underlying code change was, and which comment(s) it addressed, if any.\n2. **Not fixed** (if any): which diffs couldn't be addressed, and why — e.g. the comment's ask wasn't possible, was ambiguous, or conflicted with something else. Note that you left this explanation as a reply\u002Fcomment on the diff (Step 4) — don't just leave it in the report where only this conversation sees it. Be specific enough that a human reviewer can pick this back up without re-deriving what you already found.\n\nPost this report as a comment on the PR itself, in addition to delivering it here (e.g. `gh pr comment \u003Cnumber> --body \"...\"` for GitHub, `glab mr note \u003Cid> --message \"...\"` for GitLab, or a `POST \u002F2.0\u002Frepositories\u002F{workspace}\u002F{repo_slug}\u002Fpullrequests\u002F{id}\u002Fcomments` call with body `{\"content\": {\"raw\": \"...\"}}` for Bitbucket).\n\n## Step 7 -- Report feedback to Meticulous\n\nAs the last step, submit one brief feedback note to the Meticulous team: did the rejections\u002Fcomments give you enough to work with, was anything ambiguous, and what would have made the handoff easier?\n\n```bash\n# CLI\nmeticulous agent submit-feedback --message=\"\u003Cone or two sentences>\" --outcome=\u003Chelped|neutral|hindered> --testRunId=\u003Cid> --skill=meticulous-fix\n\n# MCP\nsubmit_feedback(message=\"\u003Cone or two sentences>\", outcome=\"\u003Chelped|neutral|hindered>\", testRunId=\"\u003Cid>\", skill=\"meticulous-fix\")\n```\n","To fix diffs that have already been reviewed and rejected, follow the workflow below step by step, using the CLI or MCP commands as described.\n\n> Before starting, run the `meticulous-cli-update` skill to ensure the Meticulous CLI and skills are up to date — unless it has already run earlier in this conversation, in which case skip it.\n\nThis skill assumes the review has already happened — a user (or the `meticulous-review` skill) has gone through the run and rejected the diffs that are real problems, possibly leaving comments explaining what's wrong or what to do about it, though comments aren't a given. Your job here is narrower than a full review: don't re-litigate diffs that weren't rejected, and don't second-guess the rejection itself — just work out what needs to change and make it happen.\n\n## Step 1 -- Get the rejected diffs and any commented-on diffs\n\n```bash\n# CLI\nmeticulous agent test-run-diffs --onlyRejected --onlyWithComments --includeReviews\n\n# MCP (git context is never inferred — pass a commit or test run explicitly)\nget_test_run_diffs(testRunId=\"\u003Cid>\", onlyRejected=true, onlyWithComments=true, includeReviews=true)\n```\n\n**Important — these `--only*` flags are additive (OR'd):** passing both `--onlyRejected` and `--onlyWithComments` returns every diff that's rejected, has an open comment, or both — not just the intersection — since a comment on a diff that wasn't formally rejected may still contain an instruction worth acting on. `--includeAllDiffs` is implied, so this spans the full run rather than just the selected subset; `--includeReviews` adds `decision`\u002F`openComments` columns so you can tell which case each row is.\n\n**Not every commented row is a fix target.** The `meticulous-review` skill's `ignore-diff` posts a flake\u002Fnoise note and leaves the diff `unreviewed` — that comment is not a fix instruction. When reading Step 1's rows, skip diffs whose only open comments are ignore\u002Fflake notes; leave those threads alone.\n\n## Step 2 -- Read the review comments for diffs that have any\n\nFor each diff with `openComments > 0`:\n\n```bash\n# CLI\nmeticulous agent diff-comments --replayDiffId \u003CreplayDiffId> --screenshotName \u003CscreenshotName>\n\n# MCP\nget_diff_comments(replayDiffId=\"\u003CreplayDiffId>\", screenshotName=\"\u003CscreenshotName>\")\n```\n\nThis is your primary source of instructions — a comment usually says what's wrong and, often, what to do about it. Read every comment and its replies (nested oldest-first) before starting on that diff; a reply can narrow down or redirect an earlier comment's ask.\n\nFor a rejected diff with no comments, there's nothing to read here — the visual\u002Fstructural context next is what you'll rely on instead.\n\n## Step 3 -- Get the visual and structural context\n\nReuse the inspection mechanics from the `meticulous-review` skill for each diff:\n\n```bash\n# CLI\nmeticulous agent image-files --replayDiffId \u003CreplayDiffId> --screenshotName \u003CscreenshotName>\nmeticulous agent dom-diff --replayDiffId \u003CreplayDiffId> --screenshotName \u003CscreenshotName>\n\n# MCP\nget_image_urls(replayDiffId=\"\u003CreplayDiffId>\", screenshotName=\"\u003CscreenshotName>\")\nget_dom_diff(replayDiffId=\"\u003CreplayDiffId>\", screenshotName=\"\u003CscreenshotName>\")\n```\n\nSee the `meticulous-review` skill's Steps 2-3 for output formats and the optional timeline (`agent timeline-diff`) if the cause still isn't clear.\n\n**Fallback for a rejected diff with no comments:** this context is now your primary source of instruction, not just extra background — treat it the same way the `meticulous-review` skill's Decision guide would, and use your own judgment to figure out what regression the rejection is pointing at.\n\n## Step 4 -- Fix the underlying code\n\nFor each **fix target** — a rejected diff, or a non-rejected diff whose comments ask for a concrete fix — make the code change that resolves the comment's instructions (or, in the no-comment fallback, the regression you identified). Skip ignore\u002Fflake-only threads from Step 1; do not change code for them and do not reply on them. A single code change may resolve multiple fix-target diffs at once (e.g. one component bug causing several screenshot diffs) — don't fix the same root cause repeatedly.\n\nClose the loop on **every fix-target** diff — fixed or not — by replying to its comment thread (or creating one if it had none):\n\n```bash\n# CLI\nmeticulous agent reply-to-diff-comment --commentId=\u003Cid> --text=\"\u003Cmessage>\"\nmeticulous agent create-diff-comment --replayDiffId=\u003Cid> --screenshotName=\u003Cname> --text=\"\u003Cmessage>\" --x=\u003C0..1> --y=\u003C0..1>\n\n# MCP\nreply_to_diff_comment(commentId=\"\u003Cid>\", text=\"\u003Cmessage>\")\ncreate_diff_comment(replayDiffId=\"\u003Cid>\", screenshotName=\"\u003Cname>\", text=\"\u003Cmessage>\", x=\u003C0..1>, y=\u003C0..1>)\n```\n\nUse `reply-to-diff-comment` when the diff already has a comment thread — pass the thread's **root** `id` from Step 2 (the row with a blank `replyToCommentId`), not a reply's id. Use `create-diff-comment` only when the diff was rejected with no existing comment (the no-comment fallback case), since there's no thread to reply to.\n\n- **Fixed** — reply\u002Fcomment \"Fixed.\"\n- **Not fixable** (a comment asks for something that isn't actually possible — contradicts another requirement, describes behavior that doesn't exist, references something you can't find, etc.) — don't guess; explain why, so the reviewer sees it without having to ask you again.\n\nEither way, move on to the next fix-target diff; report it at the end (see the final report below).\n\n## Step 5 -- Commit, push, and let CI confirm\n\n1. Commit the fixes. Note in the commit message that this addressed Meticulous review feedback, specific enough that `git log` alone tells the story later:\n\n   ```\n   Fix layout shift in checkout header\n\n   Addresses Meticulous review feedback on test run \u003CtestRunId>:\n   - \u003CreplayDiffId>\u002F\u003CscreenshotName>: \u003Cbrief on what was wrong and the fix>\n   ```\n\n2. Push the branch (`git push origin \u003Cbranch>` — see your git push rules).\n3. **Author credit:** if the PR description already credits an AI coding assistant as (co-)author (e.g. \"Created by Claude Code\", \"Co-authored-by: Cursor\", \"🤖 Generated with Claude Code\") and doesn't already mention Meticulous, add \"and Meticulous\" to that mention — e.g. \"Created by Claude Code and Meticulous\" — since Meticulous's review feedback drove this fix. Don't add a Meticulous author credit if no such line already exists; there's nothing to append it to.\n4. Wait for CI to trigger its own new Meticulous test run for the pushed commit, then confirm the previously-flagged diffs are actually resolved:\n\n   ```bash\n   # CLI (resolves from local git HEAD — already the pushed commit)\n   meticulous agent test-run-for-commit\n   meticulous agent test-run-diffs --onlyRejected --onlyWithComments --includeReviews\n\n   # MCP (git context is never inferred — resolve the testRunId from the local HEAD commit first)\n   get_test_run_for_commit(commitSha=\"\u003Csha>\")\n   get_test_run_diffs(testRunId=\"\u003Cid>\", onlyRejected=true, onlyWithComments=true, includeReviews=true)\n   ```\n\nIf a diff you believed you fixed is still showing up (decisions\u002Fcomments carry forward from the compared run), your fix didn't address the root cause; go back to Step 3\u002F4 for that one, then repeat this step.\n\n## Step 6 -- Final report\n\nSummarize the outcome, covering **every fix-target** diff from Step 1 (omit ignore\u002Fflake-only rows you skipped). Link every diff you mention: `https:\u002F\u002Fapp.meticulous.ai\u002Ftest-runs\u002F\u003CtestRunId>\u002Freplay-diff\u002F\u003CreplayDiffId>?screenshot=\u003CscreenshotName>`.\n\n1. **Fixed**: which diffs were resolved, what the underlying code change was, and which comment(s) it addressed, if any.\n2. **Not fixed** (if any): which diffs couldn't be addressed, and why — e.g. the comment's ask wasn't possible, was ambiguous, or conflicted with something else. Note that you left this explanation as a reply\u002Fcomment on the diff (Step 4) — don't just leave it in the report where only this conversation sees it. Be specific enough that a human reviewer can pick this back up without re-deriving what you already found.\n\nPost this report as a comment on the PR itself, in addition to delivering it here (e.g. `gh pr comment \u003Cnumber> --body \"...\"` for GitHub, `glab mr note \u003Cid> --message \"...\"` for GitLab, or a `POST \u002F2.0\u002Frepositories\u002F{workspace}\u002F{repo_slug}\u002Fpullrequests\u002F{id}\u002Fcomments` call with body `{\"content\": {\"raw\": \"...\"}}` for Bitbucket).\n\n## Step 7 -- Report feedback to Meticulous\n\nAs the last step, submit one brief feedback note to the Meticulous team: did the rejections\u002Fcomments give you enough to work with, was anything ambiguous, and what would have made the handoff easier?\n\n```bash\n# CLI\nmeticulous agent submit-feedback --message=\"\u003Cone or two sentences>\" --outcome=\u003Chelped|neutral|hindered> --testRunId=\u003Cid> --skill=meticulous-fix\n\n# MCP\nsubmit_feedback(message=\"\u003Cone or two sentences>\", outcome=\"\u003Chelped|neutral|hindered>\", testRunId=\"\u003Cid>\", skill=\"meticulous-fix\")\n```\n",{"name":5,"description":7,"user-invocable":24},true,"main","9836d94e88404aabb682086405c2aa9cba7657ac","plugins\u002Fmeticulous\u002Fskills\u002Fmeticulous-fix",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":35,"prompt":45,"zipAvailable":24},[36,39,42],{"tool":37,"command":38},"npx","npx skills add CognitionAI\u002Fdevin-marketplace --skill meticulous-fix",{"tool":40,"command":41},"bunx","bunx skills add CognitionAI\u002Fdevin-marketplace --skill meticulous-fix",{"tool":43,"command":44},"pnpm","pnpm dlx skills add CognitionAI\u002Fdevin-marketplace --skill meticulous-fix","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fmeticulous\u002Fskills\u002Fmeticulous-fix\u002FSKILL.md",[],[48,54,61,67,74,81],{"skillNo":49,"name":50,"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":51,"categories":52,"keywords":53,"publishedAt":19},"01M7BYC4AJGM98P2G9JH7QS24Z","business-data","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fwindsor-ai\u002Fskills\u002Fbusiness-data\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"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":62,"name":56,"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},"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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",[],[]]