object-storage

Set up GCS-backed object storage with presigned URL uploads.

18|4|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/DevHive1/DevHive-Cli --skill object-storage-devhive1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: object-storage
Source: https://github.com/DevHive1/DevHive-Cli/tree/main/skills/object-storage
Command: npx skills add https://github.com/DevHive1/DevHive-Cli --skill object-storage-devhive1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @google-cloud/storage, google-auth-library, @uppy/aws-s3, @uppy/core, @uppy/dashboard, @uppy/react, and includes references (resource) and assets (resource) components.

What problem does it solve?

This Skill solves the complexity of implementing secure, scalable file uploads and asset serving in pnpm monorepo projects by providing a pre-configured GCS-backed storage architecture.

Core Features & Use Cases

  • Presigned URL Uploads: Enables secure, direct-to-cloud file uploads from the client, bypassing your server to save bandwidth and compute.
  • Flexible Serving: Provides distinct paths for public assets and private, ACL-protected object entities.
  • Use Case: Ideal for applications requiring user-generated content uploads, such as profile pictures, document management systems, or media galleries, while maintaining strict access control.

Quick Start

Run the setupObjectStorage function in your code execution sandbox to provision your storage bucket and configure the necessary environment variables.

Frequently Asked Questions about object-storage

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

FAQPage Schema
How do I implement presigned URL uploads for Google Cloud Storage in a pnpm monorepo?

Presigned URL uploads let clients send files directly to Google Cloud Storage, bypassing your server to save bandwidth. This Skill provides a pre-configured two-step presigned upload flow using Uppy and Zod-validated endpoints within a pnpm monorepo environment.

What is the best way to manage public and private file serving for a web application using GCS?

Managing public and private file serving requires distinct paths for public assets and ACL-protected objects. This Skill provides a Google Cloud Storage architecture that handles flexible serving, ensuring user-generated content like profile pictures remains accessible while private documents stay secure.

Can I integrate Uppy with Google Cloud Storage for direct-to-cloud file uploads?

Yes, you can integrate Uppy with Google Cloud Storage for direct-to-cloud uploads. This Skill includes dependencies like @uppy/react, @uppy/dashboard, and @uppy/aws-s3 to facilitate secure client-side upload integration alongside Zod-validated API endpoints.

Does this object storage solution work with pnpm monorepo environments and Zod validation?

Yes, this object storage solution is specifically designed for pnpm monorepo environments and utilizes Zod-validated API endpoints. It provisions a Google Cloud Storage bucket and configures necessary environment variables to securely manage file uploads and asset serving across your monorepo packages.

Why use direct-to-cloud presigned URLs instead of routing file uploads through my backend server?

Direct-to-cloud presigned URLs save server bandwidth and compute resources by allowing the client to upload files straight to Google Cloud Storage. This architecture prevents your backend from becoming a bottleneck during large user-generated content uploads like media galleries.

What setup is required to provision a Google Cloud Storage bucket for web app file uploads?

To provision a Google Cloud Storage bucket, you run the setupObjectStorage function in your code execution sandbox. This action configures the necessary environment variables and storage architecture required to start handling secure file management and uploads.