virus-scan-pipeline

Automate malware scanning of file uploads with ClamAV or cloud antivirus APIs.

Updated Mar 29, 2026

Search Tags:#s3 #file uploads #malware scanning #clamav #cloud antivirus #queue-based pipeline #quarantine workflow

Ready to run

npx skills add https://github.com/marquesfelip/agents-and-skills --skill virus-scan-pipeline

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: virus-scan-pipeline
Source: https://github.com/marquesfelip/agents-and-skills/tree/main/skills/virus-scan-pipeline
Command: npx skills add https://github.com/marquesfelip/agents-and-skills --skill virus-scan-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates malware scanning of uploaded files to prevent infected content from being served and to reduce security risk.

Core Features & Use Cases

Async, queue-driven virus scanning using ClamAV or cloud antivirus APIs
Quarantine workflow for infected files with auditable logging
Post-scan routing to downstream processing once files are verified clean
Supports object storage (e.g., S3) with controlled access until scanning completes

Quick Start

Configure and run an asynchronous malware scanning pipeline that quarantines infected files and only serves clean uploads.

Frequently Asked Questions about virus-scan-pipeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate malware scanning on file uploads to S3?▼

Automating malware scanning on S3 file uploads involves routing files through an asynchronous queue-based pipeline that uses ClamAV or cloud antivirus APIs to scan content before it is served. This ensures infected files are intercepted before reaching users.

Can I use ClamAV or cloud antivirus APIs in an asynchronous queue-based pipeline?▼

Yes, you can use ClamAV or cloud antivirus APIs within an asynchronous queue-based pipeline to process file scans. This architecture offloads scanning from the main upload path, maintaining performance while verifying file safety through managed scan queues.

How do I quarantine infected files with auditable logging?▼

Quarantining infected files with auditable logging requires isolating flagged uploads into a restricted object storage state and recording the scan event details. This workflow maintains a clear audit trail while preventing access to malicious content.

How does a quarantine workflow handle scan_status states like pending and clean?▼

A quarantine workflow tracks scan_status states like pending, scanning, clean, quarantined, and scan_failed to control file routing. Downloads are only permitted once a file reaches the clean state, while infected files are diverted to quarantine.

What is the best way to prevent infected content from being served in a SaaS architecture?▼

Preventing infected content from being served in a SaaS architecture requires implementing controlled access to object storage until an asynchronous malware scan completes. Files remain pending and inaccessible until verified clean by the scanning pipeline.

How do I route files to downstream processing only after a virus scan is clean?▼

Routing files to downstream processing after a clean virus scan requires monitoring scan_status states and triggering post-scan routing only when the clean state is reached. This guarantees that infected files remain quarantined and unprocessed.