[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BW8BYZ0EFGWH2ARCFEJVT3":3,"skill-same:01M7BW8BYZ0EFGWH2ARCFEJVT3":77},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M7BW8BYZ0EFGWH2ARCFEJVT3","dt-obs-network-flows",null,"Network flow analysis in Dynatrace across three sources: OneAgent flows (host\u002Fprocess\u002Fpod-to-peer connections in the `default_network_flows` Grail bucket), NetFlow\u002FIPFIX\u002FsFlow (via an OpenTelemetry Collector), and cloud flow logs (AWS VPC \u002F Transit Gateway; Azure and GCP planned). Use to analyze traffic between entities, find top talkers by bandwidth, map communication dependencies, investigate connection health (resets, timeouts, retransmissions, RTT), and resolve peers to monitored entities. Routes each question to the right source; source-specific DQL lives in the reference files. Trigger: \"network flows\", \"top talkers\", \"traffic between hosts\", \"connection resets\", \"TCP retransmissions\", \"RTT\", \"pod connections\", \"network dependencies\", \"NetFlow\", \"IPFIX\", \"sFlow\", \"VPC flow logs\", \"cloud network traffic\". Do NOT use for host NIC throughput or packet drops (use dt-obs-hosts), service request rate or latency (use dt-obs-services), or synthetic\u002Fuptime monitoring (use dt-obs-ext-monitors).","CognitionAI\u002Fdevin-marketplace","CognitionAI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F163493330?v=4","01M7BVSRD98NC4FG8T3EZS6V5M","Cognition","01M7BVSRDX111C2XPWJ0E6MY26",29,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-network-flows\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dt-obs-network-flows\ndescription: >-\n  Network flow analysis in Dynatrace across three sources: OneAgent flows\n  (host\u002Fprocess\u002Fpod-to-peer connections in the `default_network_flows` Grail\n  bucket), NetFlow\u002FIPFIX\u002FsFlow (via an OpenTelemetry Collector), and cloud flow\n  logs (AWS VPC \u002F Transit Gateway; Azure and GCP planned). Use to analyze traffic\n  between entities, find top talkers by bandwidth, map communication dependencies,\n  investigate connection health (resets, timeouts, retransmissions, RTT), and\n  resolve peers to monitored entities. Routes each question to the right source;\n  source-specific DQL lives in the reference files.\n  Trigger: \"network flows\", \"top talkers\", \"traffic between hosts\", \"connection\n  resets\", \"TCP retransmissions\", \"RTT\", \"pod connections\", \"network dependencies\",\n  \"NetFlow\", \"IPFIX\", \"sFlow\", \"VPC flow logs\", \"cloud network traffic\".\n  Do NOT use for host NIC throughput or packet drops (use dt-obs-hosts), service\n  request rate or latency (use dt-obs-services), or synthetic\u002Fuptime monitoring\n  (use dt-obs-ext-monitors).\nlicense: Apache-2.0\n---\n\n# Network Flows Skill\n\nAnalyze network traffic in Dynatrace across three flow data sources. This skill covers the **use cases** network flows enable and routes each question to the right source and reference file. The detailed, source-specific DQL lives in the reference files.\n\n## What Network Flows Tell You\n\nNetwork flow data answers questions that metrics and traces cannot:\n\n- **Who talks to whom** — communication dependencies between hosts, processes, pods, services, and external endpoints\n- **Top talkers** — which entities generate the most traffic, by bytes or connection count\n- **Connection health** — resets, timeouts, retransmissions, and round-trip time (RTT) per conversation\n- **Traffic composition** — protocol (TCP\u002FUDP), destination ports, direction (client vs server)\n- **Peer resolution** — mapping raw IP:port peers back to monitored entities (host, process, pod, service) or flagging them as external\n\n---\n\n## The Three Flow Sources\n\nChoose the source based on **where the traffic is** and **what is capturing it**. When more than one applies, prefer the source with the richest entity context (usually OneAgent).\n\n| Source | Captured by | Data location | Entity context | Use when |\n|---|---|---|---|---|\n| **OneAgent flows** | OneAgent network agent on the host | **events** in the `default_network_flows` Grail bucket | Rich — the capturing entity (client or server) resolved to host \u002F process \u002F pod smartscape IDs; the remote peer as IP:port | Traffic to\u002Ffrom OneAgent-monitored hosts, processes, or Kubernetes pods. **The default and most detailed source.** |\n| **NetFlow \u002F IPFIX \u002F sFlow** | Network devices (switches, routers), ingested via an OpenTelemetry Collector | **logs** (`otel.scope.name == \"otelcol\u002Fnetflowreceiver\"`; recommend routing to a dedicated bucket) | Device\u002Finterface level — raw IPs, exporter, interfaces; no smartscape entities | Traffic seen by network hardware. Covers east-west and north-south flows at the network layer. |\n| **Cloud flow logs** | Cloud provider (AWS VPC \u002F TGW; Azure, GCP not yet documented) | **logs** (`log.type == \"aws.vpc\"` \u002F `\"aws.tgw\"`; recommend routing to a dedicated bucket) | Cloud resource level — VPC \u002F subnet \u002F AZ \u002F ENI, TGW attachment; raw IPs, no smartscape entities | Traffic within\u002Facross cloud networks, including managed services and resources without an agent. |\n\n### Routing logic\n\n1. **Is the traffic to\u002Ffrom a OneAgent-monitored host, process, or pod?** → OneAgent flows. See [references\u002Foneagent-flows\u002Foneagent-flows.md](references\u002Foneagent-flows\u002Foneagent-flows.md).\n2. **Is it device-level or from unmonitored hosts?** → NetFlow. See [references\u002Fnetflow\u002Fnetflow.md](references\u002Fnetflow\u002Fnetflow.md).\n3. **Is it cloud-network \u002F managed-service traffic?** → Cloud flow logs (per provider). AWS: [references\u002Fcloud-flows\u002Faws\u002Faws.md](references\u002Fcloud-flows\u002Faws\u002Faws.md).\n\n> The three sources overlap. A pod-to-pod flow may appear in both OneAgent flows (with full pod context) and cloud flow logs (as ENI-to-ENI). Lead with the source that carries the entity context the user needs, and mention the alternative only if the primary source has no data.\n\n---\n\n## Related Network Data in Dynatrace\n\nNetwork flows are one part of Dynatrace's network observability. Route to these when the question is not about flows:\n\n| The user wants… | Use |\n|---|---|\n| Host NIC throughput, link utilization, packet drops\u002Ferrors | [dt-obs-hosts](..\u002Fdt-obs-hosts\u002FSKILL.md) → `references\u002Fhost-metrics.md` (Network Monitoring section) |\n| Process-level network I\u002FO and TCP connection quality metrics | [dt-obs-hosts](..\u002Fdt-obs-hosts\u002FSKILL.md) → `references\u002Fprocess-monitoring.md` |\n| Kubernetes pod connections and cluster network topology | [dt-obs-kubernetes](..\u002Fdt-obs-kubernetes\u002FSKILL.md) |\n| Service request rate, latency, error rate | [dt-obs-services](..\u002Fdt-obs-services\u002FSKILL.md) |\n| External \u002F synthetic uptime and network-availability monitors | [dt-obs-ext-monitors](..\u002Fdt-obs-ext-monitors\u002FSKILL.md) |\n| Network devices — switches, routers, firewalls (SNMP\u002Fmonitoring) | `dt-obs-network-devices` *(planned — not yet available)* |\n\n> A future macro **`dt-obs-network`** skill may connect all network concepts (devices, hosts\u002Fprocess\u002Fpod metrics, flows, availability monitors, cloud network monitoring). Until it exists, this skill carries the flow-specific cross-links above.\n\n---\n\n## Reference Files\n\n- [references\u002Foneagent-flows\u002Foneagent-flows.md](references\u002Foneagent-flows\u002Foneagent-flows.md) — **Validated.** Data model, field reference, and DQL for the `default_network_flows` bucket: top talkers, traffic maps, protocol\u002Fport breakdowns, connection health (resets\u002Ftimeouts\u002Fretransmissions\u002FRTT), bandwidth in bps, and which side of a flow is the peer.\n- [references\u002Fpeer-resolution\u002Fpeer-resolution.md](references\u002Fpeer-resolution\u002Fpeer-resolution.md) — **Validated.** Shared Smartscape lookups that resolve a raw flow IP (and optional port) to a monitored host, process, Kubernetes pod, or service (host → pod → service → external). Used by both OneAgent flows and NetFlow.\n- [references\u002Foneagent-flows\u002Fconfiguration.md](references\u002Foneagent-flows\u002Fconfiguration.md) — Enabling and tuning `builtin:network-connection-monitoring` (the setting that produces OneAgent flow data).\n- [references\u002Fnetflow\u002Fnetflow.md](references\u002Fnetflow\u002Fnetflow.md) — **Validated.** NetFlow\u002FIPFIX\u002FsFlow ingested via an OpenTelemetry Collector into `logs`: data model, direction semantics (unidirectional, no client\u002Fserver role), and DQL for top conversations\u002Ftalkers\u002Fports, protocol breakdowns, traffic-over-time, and per-exporter\u002Fper-interface views.\n- [references\u002Fnetflow\u002Fconfiguration.md](references\u002Fnetflow\u002Fconfiguration.md) — OTel Collector `netflow`-receiver ingestion path and the dedicated-bucket routing recommendation for netflow logs.\n- [references\u002Fcloud-flows\u002Faws\u002Faws.md](references\u002Fcloud-flows\u002Faws\u002Faws.md) — **Validated (AWS).** AWS VPC Flow Logs and Transit Gateway flow logs ingested into `logs`: `aws.vpc`\u002F`aws.tgw` field model (incl. `pkt_srcaddr` vs `srcaddr`, `log_status` filtering), and DQL for top conversations\u002Ftalkers\u002Fports, rejected-traffic (security), egress `traffic_path`, per-VPC\u002Fsubnet\u002FAZ, inter-VPC, traffic-over-time, and TGW packet-loss. Also AWS entity resolution — ENI\u002Finstance by id or IP-in-`aws.object` — for agentless resources the shared peer lookups miss.\n- [references\u002Fcloud-flows\u002Faws\u002Fconfiguration.md](references\u002Fcloud-flows\u002Faws\u002Fconfiguration.md) — Amazon Data Firehose ingestion path for AWS flow logs and the dedicated-bucket routing recommendation.\n\n  *(Azure NSG\u002FVNet and GCP VPC flow logs are not yet documented; add them as sibling `cloud-flows\u002F\u003Cprovider>\u002F` folders when tenant data is available.)*\n","# Network Flows Skill\n\nAnalyze network traffic in Dynatrace across three flow data sources. This skill covers the **use cases** network flows enable and routes each question to the right source and reference file. The detailed, source-specific DQL lives in the reference files.\n\n## What Network Flows Tell You\n\nNetwork flow data answers questions that metrics and traces cannot:\n\n- **Who talks to whom** — communication dependencies between hosts, processes, pods, services, and external endpoints\n- **Top talkers** — which entities generate the most traffic, by bytes or connection count\n- **Connection health** — resets, timeouts, retransmissions, and round-trip time (RTT) per conversation\n- **Traffic composition** — protocol (TCP\u002FUDP), destination ports, direction (client vs server)\n- **Peer resolution** — mapping raw IP:port peers back to monitored entities (host, process, pod, service) or flagging them as external\n\n---\n\n## The Three Flow Sources\n\nChoose the source based on **where the traffic is** and **what is capturing it**. When more than one applies, prefer the source with the richest entity context (usually OneAgent).\n\n| Source | Captured by | Data location | Entity context | Use when |\n|---|---|---|---|---|\n| **OneAgent flows** | OneAgent network agent on the host | **events** in the `default_network_flows` Grail bucket | Rich — the capturing entity (client or server) resolved to host \u002F process \u002F pod smartscape IDs; the remote peer as IP:port | Traffic to\u002Ffrom OneAgent-monitored hosts, processes, or Kubernetes pods. **The default and most detailed source.** |\n| **NetFlow \u002F IPFIX \u002F sFlow** | Network devices (switches, routers), ingested via an OpenTelemetry Collector | **logs** (`otel.scope.name == \"otelcol\u002Fnetflowreceiver\"`; recommend routing to a dedicated bucket) | Device\u002Finterface level — raw IPs, exporter, interfaces; no smartscape entities | Traffic seen by network hardware. Covers east-west and north-south flows at the network layer. |\n| **Cloud flow logs** | Cloud provider (AWS VPC \u002F TGW; Azure, GCP not yet documented) | **logs** (`log.type == \"aws.vpc\"` \u002F `\"aws.tgw\"`; recommend routing to a dedicated bucket) | Cloud resource level — VPC \u002F subnet \u002F AZ \u002F ENI, TGW attachment; raw IPs, no smartscape entities | Traffic within\u002Facross cloud networks, including managed services and resources without an agent. |\n\n### Routing logic\n\n1. **Is the traffic to\u002Ffrom a OneAgent-monitored host, process, or pod?** → OneAgent flows. See [references\u002Foneagent-flows\u002Foneagent-flows.md](references\u002Foneagent-flows\u002Foneagent-flows.md).\n2. **Is it device-level or from unmonitored hosts?** → NetFlow. See [references\u002Fnetflow\u002Fnetflow.md](references\u002Fnetflow\u002Fnetflow.md).\n3. **Is it cloud-network \u002F managed-service traffic?** → Cloud flow logs (per provider). AWS: [references\u002Fcloud-flows\u002Faws\u002Faws.md](references\u002Fcloud-flows\u002Faws\u002Faws.md).\n\n> The three sources overlap. A pod-to-pod flow may appear in both OneAgent flows (with full pod context) and cloud flow logs (as ENI-to-ENI). Lead with the source that carries the entity context the user needs, and mention the alternative only if the primary source has no data.\n\n---\n\n## Related Network Data in Dynatrace\n\nNetwork flows are one part of Dynatrace's network observability. Route to these when the question is not about flows:\n\n| The user wants… | Use |\n|---|---|\n| Host NIC throughput, link utilization, packet drops\u002Ferrors | [dt-obs-hosts](..\u002Fdt-obs-hosts\u002FSKILL.md) → `references\u002Fhost-metrics.md` (Network Monitoring section) |\n| Process-level network I\u002FO and TCP connection quality metrics | [dt-obs-hosts](..\u002Fdt-obs-hosts\u002FSKILL.md) → `references\u002Fprocess-monitoring.md` |\n| Kubernetes pod connections and cluster network topology | [dt-obs-kubernetes](..\u002Fdt-obs-kubernetes\u002FSKILL.md) |\n| Service request rate, latency, error rate | [dt-obs-services](..\u002Fdt-obs-services\u002FSKILL.md) |\n| External \u002F synthetic uptime and network-availability monitors | [dt-obs-ext-monitors](..\u002Fdt-obs-ext-monitors\u002FSKILL.md) |\n| Network devices — switches, routers, firewalls (SNMP\u002Fmonitoring) | `dt-obs-network-devices` *(planned — not yet available)* |\n\n> A future macro **`dt-obs-network`** skill may connect all network concepts (devices, hosts\u002Fprocess\u002Fpod metrics, flows, availability monitors, cloud network monitoring). Until it exists, this skill carries the flow-specific cross-links above.\n\n---\n\n## Reference Files\n\n- [references\u002Foneagent-flows\u002Foneagent-flows.md](references\u002Foneagent-flows\u002Foneagent-flows.md) — **Validated.** Data model, field reference, and DQL for the `default_network_flows` bucket: top talkers, traffic maps, protocol\u002Fport breakdowns, connection health (resets\u002Ftimeouts\u002Fretransmissions\u002FRTT), bandwidth in bps, and which side of a flow is the peer.\n- [references\u002Fpeer-resolution\u002Fpeer-resolution.md](references\u002Fpeer-resolution\u002Fpeer-resolution.md) — **Validated.** Shared Smartscape lookups that resolve a raw flow IP (and optional port) to a monitored host, process, Kubernetes pod, or service (host → pod → service → external). Used by both OneAgent flows and NetFlow.\n- [references\u002Foneagent-flows\u002Fconfiguration.md](references\u002Foneagent-flows\u002Fconfiguration.md) — Enabling and tuning `builtin:network-connection-monitoring` (the setting that produces OneAgent flow data).\n- [references\u002Fnetflow\u002Fnetflow.md](references\u002Fnetflow\u002Fnetflow.md) — **Validated.** NetFlow\u002FIPFIX\u002FsFlow ingested via an OpenTelemetry Collector into `logs`: data model, direction semantics (unidirectional, no client\u002Fserver role), and DQL for top conversations\u002Ftalkers\u002Fports, protocol breakdowns, traffic-over-time, and per-exporter\u002Fper-interface views.\n- [references\u002Fnetflow\u002Fconfiguration.md](references\u002Fnetflow\u002Fconfiguration.md) — OTel Collector `netflow`-receiver ingestion path and the dedicated-bucket routing recommendation for netflow logs.\n- [references\u002Fcloud-flows\u002Faws\u002Faws.md](references\u002Fcloud-flows\u002Faws\u002Faws.md) — **Validated (AWS).** AWS VPC Flow Logs and Transit Gateway flow logs ingested into `logs`: `aws.vpc`\u002F`aws.tgw` field model (incl. `pkt_srcaddr` vs `srcaddr`, `log_status` filtering), and DQL for top conversations\u002Ftalkers\u002Fports, rejected-traffic (security), egress `traffic_path`, per-VPC\u002Fsubnet\u002FAZ, inter-VPC, traffic-over-time, and TGW packet-loss. Also AWS entity resolution — ENI\u002Finstance by id or IP-in-`aws.object` — for agentless resources the shared peer lookups miss.\n- [references\u002Fcloud-flows\u002Faws\u002Fconfiguration.md](references\u002Fcloud-flows\u002Faws\u002Fconfiguration.md) — Amazon Data Firehose ingestion path for AWS flow logs and the dedicated-bucket routing recommendation.\n\n  *(Azure NSG\u002FVNet and GCP VPC flow logs are not yet documented; add them as sibling `cloud-flows\u002F\u003Cprovider>\u002F` folders when tenant data is available.)*\n",{"name":5,"license":15,"description":7},"main","9836d94e88404aabb682086405c2aa9cba7657ac","plugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-network-flows",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":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add CognitionAI\u002Fdevin-marketplace --skill dt-obs-network-flows",{"tool":39,"command":40},"bunx","bunx skills add CognitionAI\u002Fdevin-marketplace --skill dt-obs-network-flows",{"tool":42,"command":43},"pnpm","pnpm dlx skills add CognitionAI\u002Fdevin-marketplace --skill dt-obs-network-flows","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-network-flows\u002FSKILL.md",true,[47,53,57,61,65,69,73],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fcloud-flows\u002Faws\u002Faws.md","REFERENCE","参考文档",22493,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-network-flows\u002Freferences\u002Fcloud-flows\u002Faws\u002Faws.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fcloud-flows\u002Faws\u002Fconfiguration.md",4448,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-network-flows\u002Freferences\u002Fcloud-flows\u002Faws\u002Fconfiguration.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fnetflow\u002Fconfiguration.md",3742,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-network-flows\u002Freferences\u002Fnetflow\u002Fconfiguration.md",{"path":62,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fnetflow\u002Fnetflow.md",11438,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-network-flows\u002Freferences\u002Fnetflow\u002Fnetflow.md",{"path":66,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Foneagent-flows\u002Fconfiguration.md",3288,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-network-flows\u002Freferences\u002Foneagent-flows\u002Fconfiguration.md",{"path":70,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Foneagent-flows\u002Foneagent-flows.md",15027,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-network-flows\u002Freferences\u002Foneagent-flows\u002Foneagent-flows.md",{"path":74,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fpeer-resolution\u002Fpeer-resolution.md",3989,"https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fdynatrace\u002Fskills\u002Fdt-obs-network-flows\u002Freferences\u002Fpeer-resolution\u002Fpeer-resolution.md",[78,85,92,98,105,112],{"skillNo":79,"name":80,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7BYC4AJGM98P2G9JH7QS24Z","business-data","MIT","https:\u002F\u002Fgithub.com\u002FCognitionAI\u002Fdevin-marketplace\u002Fblob\u002Fmain\u002Fplugins\u002Fwindsor-ai\u002Fskills\u002Fbusiness-data\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":81,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":87,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"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":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"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",[],[]]