[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BWZ6D3T72QH4HABAMDGPQJ":3,"skill-same:01M7BWZ6D3T72QH4HABAMDGPQJ":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},"01M7BWZ6D3T72QH4HABAMDGPQJ","meticulous-use-session-data",null,"Download and use structured Meticulous session data (user flows + network mocks) for testing code changes locally. Use when you need to understand what user interactions and API calls a test covers, or when you want network mocks for writing tests.","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-use-session-data\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: meticulous-use-session-data\ndescription: Download and use structured Meticulous session data (user flows + network mocks) for testing code changes locally. Use when you need to understand what user interactions and API calls a test covers, or when you want network mocks for writing tests.\nuser-invocable: true\n---\n\nUse this workflow to get structured session data from Meticulous — the recorded user flows and network mocks that cover your code changes.\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\n## Step 1 — Find relevant sessions and download their data\n\nRun the following command from the root of the git repository:\n\n```bash\nmeticulous local relevant-sessions --format=multi-file --minimum-times-to-cover-each-line=1\n```\n\nThis will:\n\n1. Identify which recorded sessions exercise the code paths changed on your current branch.\n2. Download each session's data as a structured directory tree to `.meticulous\u002Fsessions\u002F`.\n\n**Options:**\n\n| Option                               | Type         | Default                | Description                                                                                                                       |\n| ------------------------------------ | ------------ | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------- |\n| `--format`                           | `multi-file` | —                      | Set to `multi-file` to download each relevant session's data as a structured directory tree                                       |\n| `--minimum-times-to-cover-each-line` | number       | —                      | Select at least this many sessions to cover each edited line, choosing the most diverse subset when more candidates are available |\n| `--include-superfluous-sessions`     | boolean      | `false`                | Also include sessions that do test some changes but were superfluous given `--minimum-times-to-cover-each-line`                   |\n| `--outputDir`                        | string       | `.meticulous\u002Fsessions` | Output directory for multi-file format                                                                                            |\n| `--showMaybeRelevant`                | boolean      | `false`                | Also show sessions that may be affected                                                                                           |\n| `--startingPointSha`                 | string       | —                      | Only consider changes since this commit SHA                                                                                       |\n\n## Step 2 — Understand the output structure\n\nThe downloaded data is organized as follows:\n\n```\n.meticulous\u002Fsessions\u002F\n  manifest.json                       # List of all sessions with summary metadata\n  sessions\u002F\n    \u003Csanitized-session-id>\u002F           # Special characters in session IDs are replaced for filesystem safety\n      summary.json                    # Session overview: URL, viewport, duration, event count\n      user-events.json                # Sequence of user interactions (clicks, typing, navigation)\n      network-requests\u002F\n        summary.json                  # All network requests: method, URL, status (no bodies)\n        \u003Corder>.json                  # Individual request\u002Fresponse pairs (with bodies)\n      storage\u002F\n        cookies.json                  # Initial cookie state\n        local-storage.json            # Initial localStorage state\n        session-storage.json          # Initial sessionStorage (if present)\n        indexed-db.json               # Initial IndexedDB (if present)\n      url-history.json                # Page navigation history with timestamps\n      context.json                    # Feature flags, user ID, custom context (if present)\n      websockets\u002F                     # WebSocket data (if present)\n        summary.json                  # WebSocket connections overview\n        \u003Cconnection-id>.json          # Events for each connection\n```\n\n## Step 3 — Navigate the data\n\n1. **Start with `manifest.json`** to see all available sessions. Each entry includes the session ID, start URL, event count, duration, and network request count. Pick the session(s) relevant to your task.\n\n2. **Read `summary.json`** inside a session directory for a quick overview of that session — the starting URL, viewport size, total duration, and number of events.\n\n3. **Read `user-events.json`** to understand the user flow. Each event has:\n   - `type`: the interaction type (e.g., `click`, `input`, `scroll`)\n   - `selector`: the CSS selector of the target element\n   - `timestampMs`: when the event occurred\n   - `coordinates`: click position (if applicable)\n\n4. **Browse `network-requests\u002Fsummary.json`** to see all API calls made during the session. Each entry shows the HTTP method, URL, status code, content type, and response time — without response bodies, so it's quick to scan.\n\n5. **Read individual `network-requests\u002F\u003Corder>.json`** files for the full request\u002Fresponse data of specific API calls. Use these as mock data when writing tests. The `order` field in the summary corresponds to the filename.\n\n6. **Check `storage\u002F`** files if you need to understand the initial application state (cookies, localStorage, etc.).\n\n## Step 4 — Use the data for testing\n\nCommon use cases:\n\n### Understanding user flows\n\nRead `user-events.json` to see the exact sequence of user interactions. This tells you what the user clicked, typed, and navigated, which helps you understand what your code change needs to support.\n\n### Creating network mocks\n\nUse the network request files to create mock responses for your tests:\n\n1. Read `network-requests\u002Fsummary.json` to find the relevant API endpoints.\n2. Read the individual `network-requests\u002F\u003Corder>.json` files for the full request\u002Fresponse pairs.\n3. Use the `response.content.text` field as mock response data in your tests.\n\n### Verifying coverage\n\nCross-reference the user events and network requests with your code changes to verify that the session covers the code paths you've modified.\n\n## Alternative: Download specific sessions\n\nIf you already know which session IDs you need, you can download them directly:\n\n```bash\n# CLI\nmeticulous download session --sessionId=\u003Cid> --format=multi-file\n\n# MCP (returns the same structured data inline instead of writing it to disk)\nget_session_data(sessionId=\"\u003Cid>\")\n```\n\nThe CLI writes to `.meticulous\u002Fsessions\u002F` by default; use `--outputDir` to change the output location.\n\n## Final step — Report feedback to Meticulous\n\nOnce you've finished using the session data, submit one brief feedback note to the Meticulous team: did the session data cover the flows you needed, and what information was missing or would have made the task easier?\n\n```bash\n# CLI\nmeticulous agent submit-feedback --message=\"\u003Cone or two sentences>\" --outcome=\u003Chelped|neutral|hindered> --skill=meticulous-use-session-data\n\n# MCP\nsubmit_feedback(message=\"\u003Cone or two sentences>\", outcome=\"\u003Chelped|neutral|hindered>\", skill=\"meticulous-use-session-data\")\n```\n","Use this workflow to get structured session data from Meticulous — the recorded user flows and network mocks that cover your code changes.\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\n## Step 1 — Find relevant sessions and download their data\n\nRun the following command from the root of the git repository:\n\n```bash\nmeticulous local relevant-sessions --format=multi-file --minimum-times-to-cover-each-line=1\n```\n\nThis will:\n\n1. Identify which recorded sessions exercise the code paths changed on your current branch.\n2. Download each session's data as a structured directory tree to `.meticulous\u002Fsessions\u002F`.\n\n**Options:**\n\n| Option                               | Type         | Default                | Description                                                                                                                       |\n| ------------------------------------ | ------------ | ---------------------- | --------------------------------------------------------------------------------------------------------------------------------- |\n| `--format`                           | `multi-file` | —                      | Set to `multi-file` to download each relevant session's data as a structured directory tree                                       |\n| `--minimum-times-to-cover-each-line` | number       | —                      | Select at least this many sessions to cover each edited line, choosing the most diverse subset when more candidates are available |\n| `--include-superfluous-sessions`     | boolean      | `false`                | Also include sessions that do test some changes but were superfluous given `--minimum-times-to-cover-each-line`                   |\n| `--outputDir`                        | string       | `.meticulous\u002Fsessions` | Output directory for multi-file format                                                                                            |\n| `--showMaybeRelevant`                | boolean      | `false`                | Also show sessions that may be affected                                                                                           |\n| `--startingPointSha`                 | string       | —                      | Only consider changes since this commit SHA                                                                                       |\n\n## Step 2 — Understand the output structure\n\nThe downloaded data is organized as follows:\n\n```\n.meticulous\u002Fsessions\u002F\n  manifest.json                       # List of all sessions with summary metadata\n  sessions\u002F\n    \u003Csanitized-session-id>\u002F           # Special characters in session IDs are replaced for filesystem safety\n      summary.json                    # Session overview: URL, viewport, duration, event count\n      user-events.json                # Sequence of user interactions (clicks, typing, navigation)\n      network-requests\u002F\n        summary.json                  # All network requests: method, URL, status (no bodies)\n        \u003Corder>.json                  # Individual request\u002Fresponse pairs (with bodies)\n      storage\u002F\n        cookies.json                  # Initial cookie state\n        local-storage.json            # Initial localStorage state\n        session-storage.json          # Initial sessionStorage (if present)\n        indexed-db.json               # Initial IndexedDB (if present)\n      url-history.json                # Page navigation history with timestamps\n      context.json                    # Feature flags, user ID, custom context (if present)\n      websockets\u002F                     # WebSocket data (if present)\n        summary.json                  # WebSocket connections overview\n        \u003Cconnection-id>.json          # Events for each connection\n```\n\n## Step 3 — Navigate the data\n\n1. **Start with `manifest.json`** to see all available sessions. Each entry includes the session ID, start URL, event count, duration, and network request count. Pick the session(s) relevant to your task.\n\n2. **Read `summary.json`** inside a session directory for a quick overview of that session — the starting URL, viewport size, total duration, and number of events.\n\n3. **Read `user-events.json`** to understand the user flow. Each event has:\n   - `type`: the interaction type (e.g., `click`, `input`, `scroll`)\n   - `selector`: the CSS selector of the target element\n   - `timestampMs`: when the event occurred\n   - `coordinates`: click position (if applicable)\n\n4. **Browse `network-requests\u002Fsummary.json`** to see all API calls made during the session. Each entry shows the HTTP method, URL, status code, content type, and response time — without response bodies, so it's quick to scan.\n\n5. **Read individual `network-requests\u002F\u003Corder>.json`** files for the full request\u002Fresponse data of specific API calls. Use these as mock data when writing tests. The `order` field in the summary corresponds to the filename.\n\n6. **Check `storage\u002F`** files if you need to understand the initial application state (cookies, localStorage, etc.).\n\n## Step 4 — Use the data for testing\n\nCommon use cases:\n\n### Understanding user flows\n\nRead `user-events.json` to see the exact sequence of user interactions. This tells you what the user clicked, typed, and navigated, which helps you understand what your code change needs to support.\n\n### Creating network mocks\n\nUse the network request files to create mock responses for your tests:\n\n1. Read `network-requests\u002Fsummary.json` to find the relevant API endpoints.\n2. Read the individual `network-requests\u002F\u003Corder>.json` files for the full request\u002Fresponse pairs.\n3. Use the `response.content.text` field as mock response data in your tests.\n\n### Verifying coverage\n\nCross-reference the user events and network requests with your code changes to verify that the session covers the code paths you've modified.\n\n## Alternative: Download specific sessions\n\nIf you already know which session IDs you need, you can download them directly:\n\n```bash\n# CLI\nmeticulous download session --sessionId=\u003Cid> --format=multi-file\n\n# MCP (returns the same structured data inline instead of writing it to disk)\nget_session_data(sessionId=\"\u003Cid>\")\n```\n\nThe CLI writes to `.meticulous\u002Fsessions\u002F` by default; use `--outputDir` to change the output location.\n\n## Final step — Report feedback to Meticulous\n\nOnce you've finished using the session data, submit one brief feedback note to the Meticulous team: did the session data cover the flows you needed, and what information was missing or would have made the task easier?\n\n```bash\n# CLI\nmeticulous agent submit-feedback --message=\"\u003Cone or two sentences>\" --outcome=\u003Chelped|neutral|hindered> --skill=meticulous-use-session-data\n\n# MCP\nsubmit_feedback(message=\"\u003Cone or two sentences>\", outcome=\"\u003Chelped|neutral|hindered>\", skill=\"meticulous-use-session-data\")\n```\n",{"name":5,"description":7,"user-invocable":24},true,"main","9836d94e88404aabb682086405c2aa9cba7657ac","plugins\u002Fmeticulous\u002Fskills\u002Fmeticulous-use-session-data",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-use-session-data",{"tool":40,"command":41},"bunx","bunx skills add CognitionAI\u002Fdevin-marketplace --skill meticulous-use-session-data",{"tool":43,"command":44},"pnpm","pnpm dlx skills add CognitionAI\u002Fdevin-marketplace --skill meticulous-use-session-data","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fmeticulous\u002Fskills\u002Fmeticulous-use-session-data\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",[],[]]