Individual skill
file-upload-security
Accept, store, process, and serve user uploads safely: type-appropriate content validation, decompression limits, generated storage keys, quarantine before publication, isolated media processing, and scoped direct-to-storage credentials. Use when generating a file-upload endpoint, wiring presigned or SAS uploads to S3, GCS, or Azure Blob, processing user-supplied images or documents, or serving user-generated content.
skills/file-upload-security/SKILL.md
Source commit eaba88102d91df65a9aa6397e8507c315c018f5e
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
Standard SKILL.md format has not been attested at this commit. No installation command is available; inspect the source.
Repository context
- Repository stars (not skill ratings)
- 23
- Repository last updated
- Aug 14, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- claude-skills Repository topic
- llm Repository topic
- security Repository topic
- skills Repository topic
- operations Derived category
- writing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 8,724 bytesreferences/direct-upload.mddoc · 3,112 bytesreferences/format-handling.mddoc · 4,597 bytesreferences/verifying-findings.mddoc · 3,517 bytesrules/upload_validation.jsonasset · 4,391 bytestests/corpus.jsonasset · 5,130 bytes
Read excerpt
# File Upload Security
## Rules (for AI agents)
### ALWAYS
- Put every new upload in a **non-public quarantine** location, and do not expose it,
link it, index it, or hand it to a downstream workflow until validation has
succeeded. Quarantine → validate → process → publish, in that order. This is the
invariant the rest of these rules hang from, and the one direct-to-storage uploads
most often skip.
- Validate content **server-side with checks appropriate to the format**. Where a
format has a reliable signature, verify it; for container and document formats —
DOCX, XLSX and ZIP are all ZIP at the container level — also validate structure
against the format you expect. Text-based formats such as SVG and CSV have no