[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B64ZP34R9YB52AWBA6NWPT":3,"skill-same:01M7B64ZP34R9YB52AWBA6NWPT":79},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":15,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":13,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":48,"install":49,"resources":62},"01M7B64ZP34R9YB52AWBA6NWPT","detecting-network-anomalies-with-zeek",null,"Deploy and configure Zeek (formerly Bro) to passively analyze network traffic, generate structured connection\u002FDNS\u002FHTTP\u002FSSL\u002Ffile logs, detect anomalous behavior, and write custom scripts for organization-specific threats. Use for passive monitoring at network choke points, feeding SIEM\u002Fthreat hunting with protocol metadata, or retrospective log analysis during incident response; not a substitute for inline IDS\u002FIPS or host agents.","vikasvardhanv\u002Fjerry_skills","vikasvardhanv","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99010657?v=4","01M7B2B0VN78W7529RQX5BR6DZ","01M7B2B0WDNTXJHRK3QNPNWRP6",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fdetecting-network-anomalies-with-zeek\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fdetecting-network-anomalies-with-zeek\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: detecting-network-anomalies-with-zeek\ndescription: Deploy and configure Zeek (formerly Bro) to passively analyze network traffic, generate structured connection\u002FDNS\u002FHTTP\u002FSSL\u002Ffile logs, detect anomalous behavior, and write custom scripts for organization-specific threats. Use for passive monitoring at network choke points, feeding SIEM\u002Fthreat hunting with protocol metadata, or retrospective log analysis during incident response; not a substitute for inline IDS\u002FIPS or host agents.\ndomain: cybersecurity\nsubdomain: network-security\ntags:\n- network-security\n- zeek\n- network-monitoring\n- anomaly-detection\n- threat-hunting\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.IR-01\n- DE.CM-01\n- ID.AM-03\n- PR.DS-02\nmitre_attack:\n- T1046\n- T1040\n- T1557\n- T1071\n---\n# Detecting Network Anomalies with Zeek\n\n## When to Use\n\n- Deploying passive network security monitoring at key network choke points for continuous visibility\n- Generating structured connection, DNS, HTTP, SSL, and file transfer logs for SIEM ingestion and threat hunting\n- Writing custom Zeek scripts to detect organization-specific threats, policy violations, or beaconing behavior\n- Performing retrospective analysis on network metadata to investigate security incidents\n- Complementing IDS solutions with protocol-level metadata analysis that signature-based tools may miss\n\n**Do not use** as a replacement for inline IDS\u002FIPS that can actively block traffic, for monitoring encrypted payloads without TLS inspection, or on endpoints where host-based agents are more appropriate.\n\n## Prerequisites\n\n- Zeek 6.0+ installed from source or package manager (`zeek --version`)\n- Network interface configured on a span port, network tap, or virtual switch mirror for passive capture\n- Sufficient disk storage for log files (estimate 1-5 GB\u002Fday per 100 Mbps of monitored traffic)\n- Familiarity with Zeek's scripting language for writing custom detections\n- Log aggregation system (Splunk, Elastic, Graylog) for centralized analysis\n\n## Workflow\n\n### Step 1: Install and Configure Zeek\n\n```bash\n# Install Zeek on Ubuntu\u002FDebian\nsudo apt install -y zeek\n\n# Or install from source for latest version\ngit clone --recursive https:\u002F\u002Fgithub.com\u002Fzeek\u002Fzeek\ncd zeek && .\u002Fconfigure --prefix=\u002Fopt\u002Fzeek && make -j$(nproc) && sudo make install\nexport PATH=\u002Fopt\u002Fzeek\u002Fbin:$PATH\n\n# Configure the monitoring interface\nsudo vi \u002Fopt\u002Fzeek\u002Fetc\u002Fnode.cfg\n```\n\n```ini\n# \u002Fopt\u002Fzeek\u002Fetc\u002Fnode.cfg\n[zeek]\ntype=standalone\nhost=localhost\ninterface=eth1\n```\n\n```bash\n# Configure local network definitions\nsudo vi \u002Fopt\u002Fzeek\u002Fetc\u002Fnetworks.cfg\n```\n\n```\n# \u002Fopt\u002Fzeek\u002Fetc\u002Fnetworks.cfg\n10.0.0.0\u002F8       Internal\n172.16.0.0\u002F12    Internal\n192.168.0.0\u002F16   Internal\n```\n\n```bash\n# Disable NIC offloading for accurate packet capture\nsudo ethtool -K eth1 rx off tx off gro off lro off tso off gso off\n\n# Deploy Zeek\nsudo zeekctl deploy\n\n# Verify Zeek is running\nsudo zeekctl status\n```\n\n### Step 2: Understand and Navigate Zeek Logs\n\n```bash\n# Zeek generates structured log files in \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002F\nls \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002F\n\n# Key log files:\n# conn.log       - All network connections (TCP, UDP, ICMP)\n# dns.log        - DNS queries and responses\n# http.log       - HTTP requests and responses\n# ssl.log        - SSL\u002FTLS handshake details\n# files.log      - File transfers observed on the network\n# notice.log     - Alerts from Zeek detection scripts\n# weird.log      - Protocol anomalies and errors\n# x509.log       - X.509 certificate details\n# smtp.log       - SMTP email transactions\n# ssh.log        - SSH connection details\n\n# View connection log with zeek-cut for column selection\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fconn.log | zeek-cut ts id.orig_h id.orig_p id.resp_h id.resp_p proto service duration orig_bytes resp_bytes\n\n# View DNS log\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fdns.log | zeek-cut ts id.orig_h query qtype_name answers\n\n# View HTTP log\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fhttp.log | zeek-cut ts id.orig_h host uri method status_code user_agent\n```\n\n### Step 3: Write Custom Detection Scripts\n\n```bash\n# Create a custom detection script directory\nsudo mkdir -p \u002Fopt\u002Fzeek\u002Fshare\u002Fzeek\u002Fsite\u002Fcustom-detections\n```\n\nCreate a script for detecting DNS tunneling:\n\n```zeek\n# \u002Fopt\u002Fzeek\u002Fshare\u002Fzeek\u002Fsite\u002Fcustom-detections\u002Fdns-tunneling.zeek\n@load base\u002Fframeworks\u002Fnotice\n\nmodule DNSTunneling;\n\nexport {\n    redef enum Notice::Type += {\n        DNS_Tunneling_Detected,\n        DNS_Long_Query\n    };\n\n    # Threshold: number of unique queries per source in time window\n    const query_threshold: count = 200 &redef;\n    const time_window: interval = 5min &redef;\n    const max_query_length: count = 50 &redef;\n}\n\n# Track query counts per source IP\nglobal dns_query_counts: table[addr] of count &create_expire=5min &default=0;\n\nevent dns_request(c: connection, msg: dns_msg, query: string, qtype: count, qclass: count)\n{\n    local src = c$id$orig_h;\n\n    # Check for unusually long domain queries (base64-encoded data)\n    if ( |query| > max_query_length )\n    {\n        NOTICE([\n            $note=DNS_Long_Query,\n            $msg=fmt(\"Unusually long DNS query from %s: %s (%d chars)\", src, query, |query|),\n            $src=src,\n            $identifier=cat(src, query)\n        ]);\n    }\n\n    # Track query volume per source\n    dns_query_counts[src] += 1;\n\n    if ( dns_query_counts[src] == query_threshold )\n    {\n        NOTICE([\n            $note=DNS_Tunneling_Detected,\n            $msg=fmt(\"Possible DNS tunneling: %s sent %d queries in %s\", src, query_threshold, time_window),\n            $src=src,\n            $identifier=cat(src)\n        ]);\n    }\n}\n```\n\nCreate a script for detecting beaconing:\n\n```zeek\n# \u002Fopt\u002Fzeek\u002Fshare\u002Fzeek\u002Fsite\u002Fcustom-detections\u002Fbeacon-detection.zeek\n@load base\u002Fframeworks\u002Fnotice\n@load base\u002Fframeworks\u002Fsumstats\n\nmodule BeaconDetection;\n\nexport {\n    redef enum Notice::Type += {\n        Possible_Beaconing\n    };\n\n    const beacon_threshold: count = 50 &redef;\n    const observation_window: interval = 1hr &redef;\n}\n\nevent zeek_init()\n{\n    local r1 = SumStats::Reducer(\n        $stream=\"beacon.connections\",\n        $apply=set(SumStats::SUM)\n    );\n\n    SumStats::create([\n        $name=\"detect-beaconing\",\n        $epoch=observation_window,\n        $reducers=set(r1),\n        $threshold_val(key: SumStats::Key, result: SumStats::Result) = {\n            return result[\"beacon.connections\"]$sum;\n        },\n        $threshold=beacon_threshold + 0.0,\n        $threshold_crossed(key: SumStats::Key, result: SumStats::Result) = {\n            NOTICE([\n                $note=Possible_Beaconing,\n                $msg=fmt(\"Possible beaconing: %s made %d connections in %s\",\n                         key$str, result[\"beacon.connections\"]$sum, observation_window),\n                $identifier=key$str\n            ]);\n        }\n    ]);\n}\n\nevent connection_state_remove(c: connection)\n{\n    if ( c$id$resp_h !in Site::local_nets )\n    {\n        local key = fmt(\"%s->%s:%d\", c$id$orig_h, c$id$resp_h, c$id$resp_p);\n        SumStats::observe(\"beacon.connections\", [$str=key], [$num=1]);\n    }\n}\n```\n\n### Step 4: Load Custom Scripts and Deploy\n\n```bash\n# Add custom scripts to local.zeek\nsudo tee -a \u002Fopt\u002Fzeek\u002Fshare\u002Fzeek\u002Fsite\u002Flocal.zeek \u003C\u003C 'EOF'\n\n# Custom detection scripts\n@load custom-detections\u002Fdns-tunneling.zeek\n@load custom-detections\u002Fbeacon-detection.zeek\n\n# Enable additional protocol analyzers\n@load protocols\u002Fftp\u002Fsoftware\n@load protocols\u002Fhttp\u002Fsoftware\n@load protocols\u002Fsmtp\u002Fsoftware\n@load protocols\u002Fssh\u002Fdetect-bruteforcing\n@load protocols\u002Fssl\u002Fvalidate-certs\n@load protocols\u002Fssl\u002Flog-hostcerts-only\n@load protocols\u002Fdns\u002Fdetect-external-names\n\n# Enable file extraction\n@load frameworks\u002Ffiles\u002Fextract-all-files\n\n# Enable Intel framework for threat intelligence\n@load frameworks\u002Fintel\u002Fseen\n@load frameworks\u002Fintel\u002Fdo_notice\nEOF\n\n# Reload Zeek configuration\nsudo zeekctl deploy\n\n# Verify scripts loaded without errors\nsudo zeekctl diag\n```\n\n### Step 5: Threat Hunting Queries on Zeek Logs\n\n```bash\n# Find long-duration connections (possible C2)\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fconn.log | zeek-cut ts id.orig_h id.resp_h id.resp_p duration | \\\n  awk '$5 > 3600 {print $0}' | sort -t$'\\t' -k5 -rn | head -20\n\n# Find connections with high data transfer volumes\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fconn.log | zeek-cut ts id.orig_h id.resp_h orig_bytes resp_bytes | \\\n  awk '$4 > 100000000 || $5 > 100000000 {print $0}'\n\n# Identify rare user agents (potential malware)\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fhttp.log | zeek-cut user_agent | sort | uniq -c | sort -n | head -20\n\n# Find self-signed or expired certificates\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fssl.log | zeek-cut ts id.orig_h id.resp_h server_name validation_status | \\\n  grep -v \"ok\"\n\n# Detect DNS queries to newly registered domains (DGA patterns)\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fdns.log | zeek-cut ts id.orig_h query | \\\n  awk -F'\\t' '{n=split($3,a,\".\"); if(length(a[n-1]) > 10) print $0}'\n\n# Find SSH brute force attempts\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fssh.log | zeek-cut ts id.orig_h id.resp_h auth_success | \\\n  grep \"F\" | awk '{print $2}' | sort | uniq -c | sort -rn | head -10\n\n# Identify unusual port usage\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fconn.log | zeek-cut id.resp_p proto service | \\\n  sort | uniq -c | sort -rn | head -50\n```\n\n### Step 6: Integrate with SIEM and Set Up Alerting\n\n```bash\n# Configure JSON log output for SIEM ingestion\nsudo tee \u002Fopt\u002Fzeek\u002Fshare\u002Fzeek\u002Fsite\u002Fjson-logs.zeek \u003C\u003C 'EOF'\n@load policy\u002Ftuning\u002Fjson-logs.zeek\nredef LogAscii::use_json = T;\nEOF\n\n# Forward logs to Elastic via Filebeat\n# \u002Fetc\u002Ffilebeat\u002Ffilebeat.yml\nsudo tee \u002Fetc\u002Ffilebeat\u002Ffilebeat.yml \u003C\u003C 'EOF'\nfilebeat.inputs:\n  - type: log\n    enabled: true\n    paths:\n      - \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002F*.log\n    json.keys_under_root: true\n    json.add_error_key: true\n    fields:\n      source: zeek\n    fields_under_root: true\n\noutput.elasticsearch:\n  hosts: [\"https:\u002F\u002Felastic-siem:9200\"]\n  index: \"zeek-%{+yyyy.MM.dd}\"\n  username: \"elastic\"\n  password: \"${ES_PASSWORD}\"\nEOF\n\nsudo systemctl enable --now filebeat\n\n# Set up log rotation\nsudo tee \u002Fetc\u002Fcron.d\u002Fzeek-logrotate \u003C\u003C 'EOF'\n0 0 * * * root \u002Fopt\u002Fzeek\u002Fbin\u002Fzeekctl cron\nEOF\n\n# Monitor Zeek health\nsudo zeekctl status\nsudo zeekctl netstats\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **Network Security Monitor** | Passive analysis tool that observes network traffic and generates structured metadata logs without altering or blocking traffic flow |\n| **Zeek Script** | Event-driven scripts written in Zeek's domain-specific language that process network events and generate notices, logs, and metrics |\n| **Connection Log (conn.log)** | Core Zeek log recording every observed connection with source\u002Fdestination IPs, ports, protocol, duration, and byte counts |\n| **Notice Framework** | Zeek subsystem for generating alerts when detection scripts identify suspicious activity, outputting to notice.log |\n| **SumStats Framework** | Statistical analysis framework in Zeek for tracking metrics over time windows, enabling threshold-based detection of anomalies |\n| **Intel Framework** | Zeek module for matching observed network indicators against threat intelligence feeds and generating alerts on matches |\n\n## Tools & Systems\n\n- **Zeek 6.0+**: Open-source network security monitor generating comprehensive protocol-level logs from passive traffic analysis\n- **zeek-cut**: Zeek utility for extracting specific columns from tab-separated Zeek log files for quick analysis\n- **zeekctl**: Zeek management tool for deploying, monitoring, and managing Zeek instances across single or clustered deployments\n- **RITA (Real Intelligence Threat Analytics)**: Open-source tool that analyzes Zeek logs for beaconing, DNS tunneling, and other threat indicators\n- **Filebeat**: Elastic agent for shipping Zeek JSON logs to Elasticsearch for centralized analysis and visualization\n\n## Common Scenarios\n\n### Scenario: Detecting Command-and-Control Beaconing in Enterprise Traffic\n\n**Context**: A threat intelligence report indicates that a specific threat actor uses HTTPS beaconing with 60-second intervals to compromised hosts. The SOC team needs to analyze Zeek logs to identify any hosts exhibiting this pattern across the enterprise network carrying 2 Gbps of traffic.\n\n**Approach**:\n1. Deploy Zeek on a network tap at the internet egress point with AF_PACKET for high-throughput capture\n2. Enable the custom beacon detection script with thresholds tuned for 60-second intervals over 1-hour observation windows\n3. Query conn.log for connections to external IPs with consistent duration and inter-connection timing: filter connections where the standard deviation of inter-arrival times is less than 5 seconds\n4. Cross-reference suspicious destination IPs against threat intelligence feeds loaded into Zeek's Intel framework\n5. Examine ssl.log for the associated TLS certificates -- check for self-signed certificates, unusual issuer names, or certificates with short validity periods\n6. Generate a notice for each identified beaconing source and feed into the SIEM for SOC triage\n\n**Pitfalls**:\n- Not tuning beacon detection thresholds for the environment, resulting in false positives from legitimate update services (Windows Update, AV updates)\n- Failing to exclude CDN and cloud service provider IP ranges that naturally receive many repeat connections\n- Running Zeek without sufficient CPU cores, causing packet drops on high-throughput links\n- Not enabling JSON log output, making SIEM integration unnecessarily complex with custom parsers\n\n## Output Format\n\n```\n## Zeek Network Anomaly Detection Report\n\n**Sensor**: zeek-sensor-01 (10.10.1.250)\n**Monitoring Interface**: eth1 (span port from Core-SW1)\n**Analysis Period**: 2024-03-15 00:00 to 2024-03-16 00:00 UTC\n**Total Connections Logged**: 2,847,392\n\n### Anomalies Detected\n\n| Notice Type | Source | Destination | Details |\n|-------------|--------|-------------|---------|\n| DNS_Tunneling_Detected | 10.10.3.45 | 8.8.8.8 | 847 queries to suspect-domain.xyz in 5 min |\n| Possible_Beaconing | 10.10.5.12 | 203.0.113.50:443 | 62 connections with 59.8s avg interval |\n| SSL::Invalid_Server_Cert | 10.10.8.22 | 198.51.100.33:443 | Self-signed cert, CN=localhost |\n| SSH::Password_Guessing | 45.33.32.156 | 10.10.20.11:22 | 487 failed attempts in 30 min |\n\n### Recommendations\n1. Isolate 10.10.3.45 and investigate for DNS tunneling malware\n2. Block 203.0.113.50 at firewall and forensically image 10.10.5.12\n3. Investigate self-signed TLS certificate on 198.51.100.33\n4. Block 45.33.32.156 and enforce SSH key-only authentication\n```\n","# Detecting Network Anomalies with Zeek\n\n## When to Use\n\n- Deploying passive network security monitoring at key network choke points for continuous visibility\n- Generating structured connection, DNS, HTTP, SSL, and file transfer logs for SIEM ingestion and threat hunting\n- Writing custom Zeek scripts to detect organization-specific threats, policy violations, or beaconing behavior\n- Performing retrospective analysis on network metadata to investigate security incidents\n- Complementing IDS solutions with protocol-level metadata analysis that signature-based tools may miss\n\n**Do not use** as a replacement for inline IDS\u002FIPS that can actively block traffic, for monitoring encrypted payloads without TLS inspection, or on endpoints where host-based agents are more appropriate.\n\n## Prerequisites\n\n- Zeek 6.0+ installed from source or package manager (`zeek --version`)\n- Network interface configured on a span port, network tap, or virtual switch mirror for passive capture\n- Sufficient disk storage for log files (estimate 1-5 GB\u002Fday per 100 Mbps of monitored traffic)\n- Familiarity with Zeek's scripting language for writing custom detections\n- Log aggregation system (Splunk, Elastic, Graylog) for centralized analysis\n\n## Workflow\n\n### Step 1: Install and Configure Zeek\n\n```bash\n# Install Zeek on Ubuntu\u002FDebian\nsudo apt install -y zeek\n\n# Or install from source for latest version\ngit clone --recursive https:\u002F\u002Fgithub.com\u002Fzeek\u002Fzeek\ncd zeek && .\u002Fconfigure --prefix=\u002Fopt\u002Fzeek && make -j$(nproc) && sudo make install\nexport PATH=\u002Fopt\u002Fzeek\u002Fbin:$PATH\n\n# Configure the monitoring interface\nsudo vi \u002Fopt\u002Fzeek\u002Fetc\u002Fnode.cfg\n```\n\n```ini\n# \u002Fopt\u002Fzeek\u002Fetc\u002Fnode.cfg\n[zeek]\ntype=standalone\nhost=localhost\ninterface=eth1\n```\n\n```bash\n# Configure local network definitions\nsudo vi \u002Fopt\u002Fzeek\u002Fetc\u002Fnetworks.cfg\n```\n\n```\n# \u002Fopt\u002Fzeek\u002Fetc\u002Fnetworks.cfg\n10.0.0.0\u002F8       Internal\n172.16.0.0\u002F12    Internal\n192.168.0.0\u002F16   Internal\n```\n\n```bash\n# Disable NIC offloading for accurate packet capture\nsudo ethtool -K eth1 rx off tx off gro off lro off tso off gso off\n\n# Deploy Zeek\nsudo zeekctl deploy\n\n# Verify Zeek is running\nsudo zeekctl status\n```\n\n### Step 2: Understand and Navigate Zeek Logs\n\n```bash\n# Zeek generates structured log files in \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002F\nls \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002F\n\n# Key log files:\n# conn.log       - All network connections (TCP, UDP, ICMP)\n# dns.log        - DNS queries and responses\n# http.log       - HTTP requests and responses\n# ssl.log        - SSL\u002FTLS handshake details\n# files.log      - File transfers observed on the network\n# notice.log     - Alerts from Zeek detection scripts\n# weird.log      - Protocol anomalies and errors\n# x509.log       - X.509 certificate details\n# smtp.log       - SMTP email transactions\n# ssh.log        - SSH connection details\n\n# View connection log with zeek-cut for column selection\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fconn.log | zeek-cut ts id.orig_h id.orig_p id.resp_h id.resp_p proto service duration orig_bytes resp_bytes\n\n# View DNS log\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fdns.log | zeek-cut ts id.orig_h query qtype_name answers\n\n# View HTTP log\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fhttp.log | zeek-cut ts id.orig_h host uri method status_code user_agent\n```\n\n### Step 3: Write Custom Detection Scripts\n\n```bash\n# Create a custom detection script directory\nsudo mkdir -p \u002Fopt\u002Fzeek\u002Fshare\u002Fzeek\u002Fsite\u002Fcustom-detections\n```\n\nCreate a script for detecting DNS tunneling:\n\n```zeek\n# \u002Fopt\u002Fzeek\u002Fshare\u002Fzeek\u002Fsite\u002Fcustom-detections\u002Fdns-tunneling.zeek\n@load base\u002Fframeworks\u002Fnotice\n\nmodule DNSTunneling;\n\nexport {\n    redef enum Notice::Type += {\n        DNS_Tunneling_Detected,\n        DNS_Long_Query\n    };\n\n    # Threshold: number of unique queries per source in time window\n    const query_threshold: count = 200 &redef;\n    const time_window: interval = 5min &redef;\n    const max_query_length: count = 50 &redef;\n}\n\n# Track query counts per source IP\nglobal dns_query_counts: table[addr] of count &create_expire=5min &default=0;\n\nevent dns_request(c: connection, msg: dns_msg, query: string, qtype: count, qclass: count)\n{\n    local src = c$id$orig_h;\n\n    # Check for unusually long domain queries (base64-encoded data)\n    if ( |query| > max_query_length )\n    {\n        NOTICE([\n            $note=DNS_Long_Query,\n            $msg=fmt(\"Unusually long DNS query from %s: %s (%d chars)\", src, query, |query|),\n            $src=src,\n            $identifier=cat(src, query)\n        ]);\n    }\n\n    # Track query volume per source\n    dns_query_counts[src] += 1;\n\n    if ( dns_query_counts[src] == query_threshold )\n    {\n        NOTICE([\n            $note=DNS_Tunneling_Detected,\n            $msg=fmt(\"Possible DNS tunneling: %s sent %d queries in %s\", src, query_threshold, time_window),\n            $src=src,\n            $identifier=cat(src)\n        ]);\n    }\n}\n```\n\nCreate a script for detecting beaconing:\n\n```zeek\n# \u002Fopt\u002Fzeek\u002Fshare\u002Fzeek\u002Fsite\u002Fcustom-detections\u002Fbeacon-detection.zeek\n@load base\u002Fframeworks\u002Fnotice\n@load base\u002Fframeworks\u002Fsumstats\n\nmodule BeaconDetection;\n\nexport {\n    redef enum Notice::Type += {\n        Possible_Beaconing\n    };\n\n    const beacon_threshold: count = 50 &redef;\n    const observation_window: interval = 1hr &redef;\n}\n\nevent zeek_init()\n{\n    local r1 = SumStats::Reducer(\n        $stream=\"beacon.connections\",\n        $apply=set(SumStats::SUM)\n    );\n\n    SumStats::create([\n        $name=\"detect-beaconing\",\n        $epoch=observation_window,\n        $reducers=set(r1),\n        $threshold_val(key: SumStats::Key, result: SumStats::Result) = {\n            return result[\"beacon.connections\"]$sum;\n        },\n        $threshold=beacon_threshold + 0.0,\n        $threshold_crossed(key: SumStats::Key, result: SumStats::Result) = {\n            NOTICE([\n                $note=Possible_Beaconing,\n                $msg=fmt(\"Possible beaconing: %s made %d connections in %s\",\n                         key$str, result[\"beacon.connections\"]$sum, observation_window),\n                $identifier=key$str\n            ]);\n        }\n    ]);\n}\n\nevent connection_state_remove(c: connection)\n{\n    if ( c$id$resp_h !in Site::local_nets )\n    {\n        local key = fmt(\"%s->%s:%d\", c$id$orig_h, c$id$resp_h, c$id$resp_p);\n        SumStats::observe(\"beacon.connections\", [$str=key], [$num=1]);\n    }\n}\n```\n\n### Step 4: Load Custom Scripts and Deploy\n\n```bash\n# Add custom scripts to local.zeek\nsudo tee -a \u002Fopt\u002Fzeek\u002Fshare\u002Fzeek\u002Fsite\u002Flocal.zeek \u003C\u003C 'EOF'\n\n# Custom detection scripts\n@load custom-detections\u002Fdns-tunneling.zeek\n@load custom-detections\u002Fbeacon-detection.zeek\n\n# Enable additional protocol analyzers\n@load protocols\u002Fftp\u002Fsoftware\n@load protocols\u002Fhttp\u002Fsoftware\n@load protocols\u002Fsmtp\u002Fsoftware\n@load protocols\u002Fssh\u002Fdetect-bruteforcing\n@load protocols\u002Fssl\u002Fvalidate-certs\n@load protocols\u002Fssl\u002Flog-hostcerts-only\n@load protocols\u002Fdns\u002Fdetect-external-names\n\n# Enable file extraction\n@load frameworks\u002Ffiles\u002Fextract-all-files\n\n# Enable Intel framework for threat intelligence\n@load frameworks\u002Fintel\u002Fseen\n@load frameworks\u002Fintel\u002Fdo_notice\nEOF\n\n# Reload Zeek configuration\nsudo zeekctl deploy\n\n# Verify scripts loaded without errors\nsudo zeekctl diag\n```\n\n### Step 5: Threat Hunting Queries on Zeek Logs\n\n```bash\n# Find long-duration connections (possible C2)\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fconn.log | zeek-cut ts id.orig_h id.resp_h id.resp_p duration | \\\n  awk '$5 > 3600 {print $0}' | sort -t$'\\t' -k5 -rn | head -20\n\n# Find connections with high data transfer volumes\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fconn.log | zeek-cut ts id.orig_h id.resp_h orig_bytes resp_bytes | \\\n  awk '$4 > 100000000 || $5 > 100000000 {print $0}'\n\n# Identify rare user agents (potential malware)\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fhttp.log | zeek-cut user_agent | sort | uniq -c | sort -n | head -20\n\n# Find self-signed or expired certificates\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fssl.log | zeek-cut ts id.orig_h id.resp_h server_name validation_status | \\\n  grep -v \"ok\"\n\n# Detect DNS queries to newly registered domains (DGA patterns)\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fdns.log | zeek-cut ts id.orig_h query | \\\n  awk -F'\\t' '{n=split($3,a,\".\"); if(length(a[n-1]) > 10) print $0}'\n\n# Find SSH brute force attempts\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fssh.log | zeek-cut ts id.orig_h id.resp_h auth_success | \\\n  grep \"F\" | awk '{print $2}' | sort | uniq -c | sort -rn | head -10\n\n# Identify unusual port usage\ncat \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002Fconn.log | zeek-cut id.resp_p proto service | \\\n  sort | uniq -c | sort -rn | head -50\n```\n\n### Step 6: Integrate with SIEM and Set Up Alerting\n\n```bash\n# Configure JSON log output for SIEM ingestion\nsudo tee \u002Fopt\u002Fzeek\u002Fshare\u002Fzeek\u002Fsite\u002Fjson-logs.zeek \u003C\u003C 'EOF'\n@load policy\u002Ftuning\u002Fjson-logs.zeek\nredef LogAscii::use_json = T;\nEOF\n\n# Forward logs to Elastic via Filebeat\n# \u002Fetc\u002Ffilebeat\u002Ffilebeat.yml\nsudo tee \u002Fetc\u002Ffilebeat\u002Ffilebeat.yml \u003C\u003C 'EOF'\nfilebeat.inputs:\n  - type: log\n    enabled: true\n    paths:\n      - \u002Fopt\u002Fzeek\u002Flogs\u002Fcurrent\u002F*.log\n    json.keys_under_root: true\n    json.add_error_key: true\n    fields:\n      source: zeek\n    fields_under_root: true\n\noutput.elasticsearch:\n  hosts: [\"https:\u002F\u002Felastic-siem:9200\"]\n  index: \"zeek-%{+yyyy.MM.dd}\"\n  username: \"elastic\"\n  password: \"${ES_PASSWORD}\"\nEOF\n\nsudo systemctl enable --now filebeat\n\n# Set up log rotation\nsudo tee \u002Fetc\u002Fcron.d\u002Fzeek-logrotate \u003C\u003C 'EOF'\n0 0 * * * root \u002Fopt\u002Fzeek\u002Fbin\u002Fzeekctl cron\nEOF\n\n# Monitor Zeek health\nsudo zeekctl status\nsudo zeekctl netstats\n```\n\n## Key Concepts\n\n| Term | Definition |\n|------|------------|\n| **Network Security Monitor** | Passive analysis tool that observes network traffic and generates structured metadata logs without altering or blocking traffic flow |\n| **Zeek Script** | Event-driven scripts written in Zeek's domain-specific language that process network events and generate notices, logs, and metrics |\n| **Connection Log (conn.log)** | Core Zeek log recording every observed connection with source\u002Fdestination IPs, ports, protocol, duration, and byte counts |\n| **Notice Framework** | Zeek subsystem for generating alerts when detection scripts identify suspicious activity, outputting to notice.log |\n| **SumStats Framework** | Statistical analysis framework in Zeek for tracking metrics over time windows, enabling threshold-based detection of anomalies |\n| **Intel Framework** | Zeek module for matching observed network indicators against threat intelligence feeds and generating alerts on matches |\n\n## Tools & Systems\n\n- **Zeek 6.0+**: Open-source network security monitor generating comprehensive protocol-level logs from passive traffic analysis\n- **zeek-cut**: Zeek utility for extracting specific columns from tab-separated Zeek log files for quick analysis\n- **zeekctl**: Zeek management tool for deploying, monitoring, and managing Zeek instances across single or clustered deployments\n- **RITA (Real Intelligence Threat Analytics)**: Open-source tool that analyzes Zeek logs for beaconing, DNS tunneling, and other threat indicators\n- **Filebeat**: Elastic agent for shipping Zeek JSON logs to Elasticsearch for centralized analysis and visualization\n\n## Common Scenarios\n\n### Scenario: Detecting Command-and-Control Beaconing in Enterprise Traffic\n\n**Context**: A threat intelligence report indicates that a specific threat actor uses HTTPS beaconing with 60-second intervals to compromised hosts. The SOC team needs to analyze Zeek logs to identify any hosts exhibiting this pattern across the enterprise network carrying 2 Gbps of traffic.\n\n**Approach**:\n1. Deploy Zeek on a network tap at the internet egress point with AF_PACKET for high-throughput capture\n2. Enable the custom beacon detection script with thresholds tuned for 60-second intervals over 1-hour observation windows\n3. Query conn.log for connections to external IPs with consistent duration and inter-connection timing: filter connections where the standard deviation of inter-arrival times is less than 5 seconds\n4. Cross-reference suspicious destination IPs against threat intelligence feeds loaded into Zeek's Intel framework\n5. Examine ssl.log for the associated TLS certificates -- check for self-signed certificates, unusual issuer names, or certificates with short validity periods\n6. Generate a notice for each identified beaconing source and feed into the SIEM for SOC triage\n\n**Pitfalls**:\n- Not tuning beacon detection thresholds for the environment, resulting in false positives from legitimate update services (Windows Update, AV updates)\n- Failing to exclude CDN and cloud service provider IP ranges that naturally receive many repeat connections\n- Running Zeek without sufficient CPU cores, causing packet drops on high-throughput links\n- Not enabling JSON log output, making SIEM integration unnecessarily complex with custom parsers\n\n## Output Format\n\n```\n## Zeek Network Anomaly Detection Report\n\n**Sensor**: zeek-sensor-01 (10.10.1.250)\n**Monitoring Interface**: eth1 (span port from Core-SW1)\n**Analysis Period**: 2024-03-15 00:00 to 2024-03-16 00:00 UTC\n**Total Connections Logged**: 2,847,392\n\n### Anomalies Detected\n\n| Notice Type | Source | Destination | Details |\n|-------------|--------|-------------|---------|\n| DNS_Tunneling_Detected | 10.10.3.45 | 8.8.8.8 | 847 queries to suspect-domain.xyz in 5 min |\n| Possible_Beaconing | 10.10.5.12 | 203.0.113.50:443 | 62 connections with 59.8s avg interval |\n| SSL::Invalid_Server_Cert | 10.10.8.22 | 198.51.100.33:443 | Self-signed cert, CN=localhost |\n| SSH::Password_Guessing | 45.33.32.156 | 10.10.20.11:22 | 487 failed attempts in 30 min |\n\n### Recommendations\n1. Isolate 10.10.3.45 and investigate for DNS tunneling malware\n2. Block 203.0.113.50 at firewall and forensically image 10.10.5.12\n3. Investigate self-signed TLS certificate on 198.51.100.33\n4. Block 45.33.32.156 and enforce SSH key-only authentication\n```\n",{"name":5,"tags":24,"author":30,"domain":31,"license":14,"version":32,"nist_csf":33,"subdomain":25,"description":7,"mitre_attack":38},[25,26,27,28,29],"network-security","zeek","network-monitoring","anomaly-detection","threat-hunting","mahipal","cybersecurity","1.0",[34,35,36,37],"PR.IR-01","DE.CM-01","ID.AM-03","PR.DS-02",[39,40,41,42],"T1046","T1040","T1557","T1071","main","1eb986d0b0ecc180291597e08eb5a58288843536","skills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fdetecting-network-anomalies-with-zeek","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv","2026-08-25 13:16:33",{"source":8,"skillName":5,"commands":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add vikasvardhanv\u002Fjerry_skills --skill detecting-network-anomalies-with-zeek",{"tool":55,"command":56},"bunx","bunx skills add vikasvardhanv\u002Fjerry_skills --skill detecting-network-anomalies-with-zeek",{"tool":58,"command":59},"pnpm","pnpm dlx skills add vikasvardhanv\u002Fjerry_skills --skill detecting-network-anomalies-with-zeek","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fdetecting-network-anomalies-with-zeek\u002FSKILL.md",true,[63,67,73],{"path":64,"resourceType":64,"resourceTypeDesc":65,"sizeBytes":66,"sourceHtmlUrl":15},"LICENSE","许可证",11255,{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fapi-reference.md","REFERENCE","参考文档",2550,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fdetecting-network-anomalies-with-zeek\u002Freferences\u002Fapi-reference.md",{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"scripts\u002Fagent.py","SCRIPT","脚本",11389,"https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fcurated_premium_skills\u002FAnthropic-Cybersecurity-Skills\u002Fskills\u002Fdetecting-network-anomalies-with-zeek\u002Fscripts\u002Fagent.py",[80,88,95,102,109,116],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7BESR1CJ3H5SP9XM8KYJZ9W","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","MIT","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7BES1YA6R97W7QPMFFM1PED","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7BERNHYGY035AR00VRT03KE","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7BERCK1EAKTWW7R436WAR0J","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":19},"01M7BEQZAZAQRTXFJRY7RHV3TY","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":84,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":122,"publishedAt":19},"01M7BEQKJ45K31QK5VRAQSVJCJ","grants","NIH grant research skill for clinical researchers. Grill-me intake (research idea + career stage + preliminary data + environment + submission posture + known institute targets) locks down the funding strategy before any search runs. Runs a 5-facet Consensus positioning analysis (with draft Significance\u002FInnovation language), maps the research to the right NIH institutes and study sections via RePORTER, finds NOSIs and funded overlap, and produces an editable Word document (.docx) with budget\u002Fscope-aware mechanism recommendations, submission timelines, and a mandatory program officer recommendation. Use when the user asks about research funding or makes any grant-related request (e.g., 'grants for [topic]', 'find grants for my research idea', 'what grants match my research', 'help me find NIH funding', 'grant opportunities for my research'). NIH-only scope — non-NIH funders (PCORI, DOD CDMRP, VA, foundations) are out of scope and flagged at intake.","https:\u002F\u002Fgithub.com\u002Fvikasvardhanv\u002Fjerry_skills\u002Fblob\u002Fmain\u002Fskills\u002Fresearch\u002Fgrants\u002Fskills\u002Fgrants\u002FSKILL.md",[],[]]