blobsy

Track and store large binary files in Git with external storage backends.

3|Updated Feb 19, 2026
One-click install
npx skills add https://github.com/jlevy/blobsy --skill blobsy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: blobsy
Source: https://github.com/jlevy/blobsy/tree/main/packages/blobsy
Command: npx skills add https://github.com/jlevy/blobsy --skill blobsy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

It enables users to efficiently track and store large binary files directly within Git repositories, eliminating the need for external storage solutions.

Core Features & Use Cases

  • Large File Externalization: Automatically externalizes files exceeding configurable size thresholds and manages their references.
  • Remote Storage Flexibility: Supports storing blobs in S3, local directories, or via custom command backends.
  • Use Case: Developers working with big datasets or models can push updates without bloating Git history, and easily share large assets across team members.

Quick Start

Use the blobsy skill to manage large files and incorporate them into your Git workflow for scalable version control.

Frequently Asked Questions about blobsy

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

FAQPage Schema
How do I manage large files in Git without bloating repository history?

To manage large files in Git, this skill externalizes binaries exceeding configurable size thresholds to remote storage backends. It tracks file references in version history while storing actual blobs elsewhere, preventing repository bloat and ensuring fast synchronization.

What is the best way to store large binary assets for version control outside of local Git?

The best way to store large binary assets for version control is using flexible remote storage backends. You can configure S3, local directories, or custom command backends to hold your blobs while maintaining standard Git collaboration workflows.

Can I use S3 to store large datasets tracked in my Git repository?

Yes, you can use S3 to store large datasets tracked in Git. The system supports multiple storage backends including S3, allowing developers to push updates to big datasets or models without bloating local Git history and easily sharing assets across team members.

Does externalizing large files affect data integrity and synchronization in version control?

Externalizing large files maintains data integrity and synchronization in version control by enforcing security and validation policies. It supports fast detection of changes for optimized synchronization, preventing misuse and data leaks during collaboration.

How do I automatically externalize files exceeding a specific size threshold in Git?

You can automatically externalize files exceeding a specific size threshold in Git by configuring size limits. Files crossing the threshold are routed to designated storage backends, while their references are seamlessly managed within the version history.