agentleFS
metacircu1armetacircu1ar/hive_skills/skills/audit/audit-asset-pipeline/SKILL.md

audit-asset-pipeline

Skill4 starsChanged 2 months agoMITView on GitHub

Audit upload handling and asset delivery for web applications. Use when reviewing file uploads, media storage, generated assets, public file serving, CDN/object storage integration, or hosting cost/performance risks caused by storing user uploads on the application server.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    No cache headers or CDN for frequently loaded media.

    line 22
  2. Very specific:

    Search for asset terms such as upload, multipart, file, avatar, attachment, image, video, audio, pdf, writeFile, File.write, public/, …

    line 32

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Audit Asset Pipeline

Find uploads or generated assets stored on the app server and assess whether delivery should use object storage and a CDN.

Workflow

  1. Locate asset ingestion:
    • File upload routes, multipart handlers, image/video/audio processing, generated PDFs/images, avatars, attachments, imports, exports, and admin media tools.
  2. Locate storage targets:
    • Local filesystem writes, framework static/public directories, temp directories, database blobs, object storage SDKs, and third-party media services.
  3. Locate delivery paths:
    • Static file serving, signed download URLs, proxy endpoints, CDN config, cache headers, image transforms, and public URL generation.
  4. Flag risky patterns:
    • User uploads written to the application server or repo directory.
    • Local disk storage in container/serverless environments where files disappear on redeploy.
    • Large files proxied through app workers instead of object storage/CDN.
    • No cache headers or CDN for frequently loaded media.
    • Missing file size, MIME/type validation, virus scanning expectations, or access controls for private assets.
  5. Recommend a target architecture:
    • Object storage for durable uploads.
    • CDN for public assets.
    • Signed URLs or authenticated proxy only where privacy requires it.
    • Background processing for expensive transforms.

Useful Searches

Search for asset terms such as upload, multipart, file, avatar, attachment, image, video, audio, pdf, writeFile, File.write, public/, static/, tmp, S3, GCS, Blob, signed, CDN, cache-control, and content-type.

Output

Report every upload/storage/delivery path:

Asset pathStorageDeliveryAccess controlFinding
path/file:linelocal disk/object storage/etc.app/CDN/signed URLpublic/privateissue

For each finding include risk, expected production failure mode, suggested storage/CDN fix, and tests or deploy checks to verify behavior.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.