Skip to content
Skills Library
Security · Analysis

pcap-workflow

/pcap-workflow

Performs safe offline packet-capture triage with TShark summaries, display filters, and clear-text HTTP metadata extraction. Use for PCAP/PCAPNG files, packet captures, Wireshark/TShark analysis, network forensics, 流量包, 抓包分析, 数据包分析, 网络取证, or 离线流量分析.

Author
HG-ha ↗
Repository
Argusai ↗
Licence
GPL-3.0
Last repository change
12.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

GPL-3.0, otwarta.

What it does and when to use it

Performs safe offline packet-capture triage with TShark summaries, display filters, and clear-text HTTP metadata extraction. Use for PCAP/PCAPNG files, packet captures, Wireshark/TShark analysis, network forensics, 流量包, 抓包分析, 数据包分析, 网络取证, or 离线流量分析.

Original author description

Performs safe offline packet-capture triage with TShark summaries, display filters, and clear-text HTTP metadata extraction. Use for PCAP/PCAPNG files, packet captures, Wireshark/TShark analysis, network forensics, 流量包, 抓包分析, 数据包分析, 网络取证, or 离线流量分析.

How it works

  1. PCAP Offline Workflow
Original SKILL.md headings · 70 lines, 423 words
SKILL.md preview
---
name: pcap-workflow
description: Performs safe offline packet-capture triage with TShark summaries, display filters, and clear-text HTTP metadata extraction. Use for PCAP/PCAPNG files, packet captures, Wireshark/TShark analysis, network forensics, 流量包, 抓包分析, 数据包分析, 网络取证, or 离线流量分析.
trigger-keywords:
  - "\\b(pcap|pcapng|packet capture|traffic capture|wireshark|tshark|network forensics)\\b"
  - "流量包|抓包分析|数据包分析|网络取证|离线流量|流量分析"
trigger-tools:
  - pcap_tool_inventory
  - pcap_summary_plan
  - pcap_summary
---

## PCAP Offline Workflow

This workflow analyzes an existing local capture. It never starts live capture,
opens sockets, downloads software, or sends captured data to a remote service.

### Start

1. Confirm the capture is authorized and identify the question to answer.
2. Prefer a Case with `target_type='pcap'` and `domain='network'`; attach the
   original capture as a `pcap` artifact when a durable evidence chain matters.
3. Call `pcap_tool_inventory` or `tshark_status` once.
4. If TShark is missing, stop CLI attempts. The result is
   `blocked=true`, `do_not_retry=true`, and `can_install=false`; ask the user to
   install Wireshark/TShark manually.

### Triage

1. Use `pcap_summary_plan` to review the exact local-only argv and packet cap.
2. Run `pcap_summary` for protocol counts, endpoints, time bounds, byte totals,
   and a bounded packet preview.
3. Create focused follow-up questions from that evidence: unusual peers,
   unexpected ports, protocol concentration, or a narrow time window.
4. Use `pcap_filter_plan` before `pcap_filter`. Prefer precise display filters
   and a small `max_packets`; broaden only when the result is empty for a
   defensible reason.

Examples of useful filter intent (not findings by themselves):

- DNS requests or a specific queried name
- A host pair, port, TCP reset, or retransmission
- TLS handshake metadata
- One protocol in a bounded time range

### HTTP Metadata

1. Use `pcap_http_extract_plan`, then `pcap_http_extract`.
2. Review request methods, hosts, URIs, response codes, content types, and user
   agents.
3. Treat extracted URLs and headers as potentially sensitive. Store decisive
   output as a Case artifact; avoid pasting large traffic excerpts into chat.
4. Correlate a conclusion to frame numbers and capture timestamps.

### Evidence Standard

For each lead, record:

- Capture artifact reference and filter used
- Relevant frame numbers and timestamps
- Source/destination and protocol
- What is observed versus inferred
- Coverage limit (`max_packets`, truncation, encrypted traffic, missing keys)

Do not label an endpoint malicious from protocol or port alone.

### Limits

- TShark is external and not bundled or managed by ArgusAI.
- This workflow does not capture live interfaces and does not require Npcap for
  reading ordinary files, though the local Wireshark package may have
  platform-specific dependencies.
- TLS and QUIC application payloads are opaque unless the user's own TShark
  installation is separately configured with valid decryption keys. These
  tools do not request, discover, or manage keys.
- HTTP extraction covers traffic TShark decodes as HTTP; it is not complete for
  encrypted HTTP/2, HTTP/3, malformed captures, unsupported link types, or
  truncated packets.
- Command output and parsed rows are intentionally capped. A capped result is
  partial coverage, not proof that no relevant traffic exists.

Versions

The database has no other skills named pcap-workflow.

Database snapshot: 13.11.2026 · package version f9f4e5ce4ee8 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100pcap-analysis
    Use when analyzing network packet capture files (.pcap, .pcapng) for DNS errors, TCP connection failures, HTTP proxy issues, or any network-level investigation using tshark on the local workstation
  • 100analyze-network-capture
    Analyze an authorized saved PCAP or PCAPNG with bounded TShark recipes and produce governed frame and stream evidence. Use for packet troubleshooting, protocol inspection, or optional local Termshark review.
  • 90performing-network-traffic-analysis-with-tshark
    Automate network traffic analysis using tshark (Wireshark CLI) and pyshark to compute protocol distribution statistics, detect suspicious flows such as port scans and beaconing, extract IOCs (IPs, domains, URLs), and identify DNS tunneling patterns from PCAP files. Use when…
  • 100wireshark-traffic-analysis
    Investigate pcap/pcapng captures through Wireshark MCP for traffic questions, network troubleshooting, and evidence-backed security analysis. Use when MCP tools are the selected backend; use tshark-cli-analysis for direct terminal execution.
  • 100net
    嵌入式网络调试工具,用于发现接口、抓包、分析 pcap/pcapng、做连通性测试、端口扫描和流量统计。 当用户提到 Wireshark、tshark、Npcap、抓包、网络联调、端口扫描、连通性排查、pcap 分析、 网络接口、ping 测试、traceroute、流量统计、Modbus TCP、EtherNet/IP 等网络协议调试时自动触发, 也兼容 /net 显式调用。即使用户只是说"抓个包看看"、"扫一下端口"、"网络通不通"或"分析一下这个 pcap",…
  • 100packet-capture-analysis-wireshark-tshark
    Use this skill when dissecting network packet traces, protocol headers, and latency spikes using Wireshark and CLI tshark.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.