A collection of skills for AI coding agents. Skills are packaged instructions that extend agent capabilities for working with Tigris object storage and writing Go tests.
Get started with Tigris file storage. CLI setup (bucket, access keys, environment), @tigrisdata/storage SDK, and framework integration guides.
Use when:
- "File storage", "upload file", "store files"
- "Tigris", "set up Tigris", "tigris bucket"
- "Client upload", "presigned URL"
- "Next.js upload", "Remix upload", "Express upload"
- "Rails file upload", "Django file upload", "Laravel file upload"
What's covered:
- CLI setup: authenticate, create bucket, create and assign access keys
- SDK reference:
put,get,remove,list,head,getPresignedUrl - Client-side browser uploads via
handleClientUpload - Framework guides: Next.js, Remix, Express, Rails, Django, Laravel
- Common patterns: avatar upload, API route file serving
- Critical rules and known issues prevention
Superseded by
file-storage. This skill now redirects tofile-storage, which covers everything this skill did and more.
Upgrade:
npx skills add https://github.com/tigrisdata/skills --skill file-storageCreate, list, inspect, and delete Tigris Storage buckets with support for regions, access levels, and storage tiers.
Use when:
- "Create a bucket"
- "List my buckets"
- "Delete bucket"
- "Check bucket info"
Operations covered:
createBucket(name, options)- with access, region, snapshot enablementlistBuckets(options)- with paginationgetBucketInfo(name)- inspect bucket metadataremoveBucket(name, options)- including force delete
Options supported: public/private access, consistency levels, storage tiers (STANDARD/STANDARD_IA/GLACIER), regional deployment, and snapshot/fork source.
Upload, download, delete, list, and inspect objects in Tigris Storage. Generate presigned URLs for temporary access.
Use when:
- "Upload file"
- "Download object"
- "List files"
- "Get presigned URL"
- "Delete object"
Operations covered:
put(path, body, options)- upload with progress tracking, multipart for large filesget(path, format, options)- download as string/file/streamremove(path, options)- delete objectslist(options)- list with prefix filtering and paginationhead(path, options)- get object metadatagetPresignedUrl(path, options)- generate temporary access URLs
Point-in-time recovery and bucket forking for version control, testing, and developer sandboxes.
Use when:
- "Create snapshot"
- "Restore from snapshot"
- "Fork bucket"
- "Point-in-time recovery"
What's covered:
createBucketSnapshot(options)- capture bucket statelistBucketSnapshots(sourceBucketName)- view history- Forking buckets from snapshots - instant, isolated copies
- Reading from snapshot versions
- Deletion protection patterns
Use cases: Developer sandboxes, AI agent environments, load testing with production data, pre-migration backups.
Write Go table-driven tests following established patterns. Covers test structure, naming conventions, error handling, and integration test guards.
Use when:
- Writing tests in Go
- Creating test functions
- Adding test cases
- "Go test", "table-driven test"
Patterns covered:
- Table structure with
name, input,want,wantErr,errCheck,setupEnvfields - Environment guards for integration tests (
skipIfNoCreds) - Test helpers with
t.Helper() - Custom error validation
- Parallel testing with
t.Parallel()
Resize, crop, and optimize images stored in Tigris across all major frameworks.
Use when:
- "Image optimization", "resize images", "thumbnails"
- "Responsive images", "image CDN"
What's covered:
- Upload-time variant generation (Sharp, ImageMagick, Pillow, Intervention)
- Framework-specific: next/image, Active Storage variants, django-imagekit
- CDN delivery via Tigris public buckets
Deploy static assets (CSS, JS, fonts) to Tigris for global CDN delivery.
Use when:
- "Static assets", "deploy CSS/JS", "asset CDN"
- "Cache headers", "asset pipeline"
What's covered:
- Cache-Control headers, cache-busting strategies
- Framework integration: assetPrefix, collectstatic, Sprockets, Vite
- Upload scripts, immutable caching
Back up databases and export data to Tigris with automated pipelines.
Use when:
- "Backup database", "database dump"
- "Scheduled backup", "data export"
What's covered:
- pg_dump/mysqldump with compression
- Framework schedulers: node-cron, whenever, celery-beat, Laravel Scheduler
- Retention policies via lifecycle rules, restore workflows
Migrate from AWS S3, GCS, or Azure Blob to Tigris with zero downtime.
Use when:
- "Migrate from S3", "switch to Tigris"
- "Shadow bucket", "S3 compatible"
What's covered:
- Shadow buckets (zero-downtime automatic backfill)
- Bulk copy via CLI, SDK endpoint swaps (Node.js, Python, Ruby, PHP)
- Verification checklist, rollback strategy
Diagnose and fix excessive storage bandwidth costs.
Use when:
- "Egress costs", "high storage bill"
- "Bandwidth optimization", "reduce data transfer"
What's covered:
- 4-step framework: diagnose, analyze, fix, verify
- Anti-patterns: server proxying, missing cache headers, no CDN
- Fixes: public buckets (built-in CDN), presigned URLs, thumbnails
Configure access keys, CORS, bucket policies, and security for Tigris.
Use when:
- "CORS", "access key rotation"
- "Security audit", "bucket permissions"
What's covered:
- Access key lifecycle, Editor/ReadOnly roles
- CORS configs (dev, production, permissive)
- Presigned URL security, audit checklist, key compromise response
Automate object expiration, storage tier transitions, and cleanup.
Use when:
- "Lifecycle rules", "auto-delete"
- "Storage tiers", "TTL", "expiration"
What's covered:
- Lifecycle rule JSON format and CLI
- Patterns: temp cleanup, log archival, backup retention
- Storage tiers (STANDARD, IA, GLACIER), cost modeling
Point-in-time recovery for deleted or changed files in Tigris.
Use when:
- "Recover deleted file", "undo delete"
- "Point-in-time recovery", "restore from snapshot"
- "Enable snapshots", "revert to previous version"
What's covered:
- Snapshot-enabled buckets (must enable at creation, not after)
- Automatic change tracking — every put/delete preserved without explicit snapshots
- Recover single files, bulk restore prefixes, revert overwrites
- TypeScript, Go, and Python examples
Guide for choosing between Tigris-native SDKs and AWS S3-compatible SDKs.
Use when:
- "Which SDK", "Tigris SDK vs AWS SDK"
- "boto3 Tigris", "storage-go"
- Setting up Tigris in a new language
What's covered:
- Decision table: native SDK (TS, Go) vs AWS SDK fallback (Python, Ruby, PHP)
- CLI:
tigris/t3instead ofaws s3 - S3-compatible configuration (endpoint, region, path style)
- Tigris-only features not available through AWS SDKs
Structured commit message format for clear project history, automated changelog generation, and semantic versioning.
Use when:
- Creating git commits
- Writing commit messages
- Following version control workflows
Commit types:
feat- New feature (MINOR version)fix- Bug fix (PATCH version)docs,style,refactor,perf,test,build,ci,chore,revert- PATCH version- Breaking changes marked with
!orBREAKING CHANGE:footer
Requirements:
- Imperative mood, lowercase, no trailing period
- AI attribution in footer:
Assisted-by: Model via Tool - Use
--signoffflag when committing
Quick install (all skills):
npx skills add tigrisdata/skillsBrowse skills at https://skills.sh/tigrisdata/skills
Claude Code (manual install):
cp -r skills/{skill-name} ~/.claude/skills/claude.ai:
Add individual skill directories to project knowledge or paste SKILL.md contents into the conversation.
Skills are automatically available once installed. The agent will use them when relevant tasks are detected.
Examples:
Install Tigris storage in my Next.js project
Create a bucket called my-app-assets with public access
Upload this file to Tigris
Write a Go test for this function
Commit these changes
Each skill contains:
SKILL.md- Instructions for the agent (required)README.md- User-facing documentation (optional)scripts/- Helper scripts for automation (optional)references/- Supporting documentation (optional)
See AGENTS.md for guidance on creating new skills in this repository.
Directory structure:
skills/
{skill-name}/
SKILL.md # Required: agent instructions
README.md # Optional: user documentation
Naming conventions:
- Skill directory:
kebab-case(e.g.,tigris-deploy) - SKILL.md: Always uppercase, exact filename
Best practices:
- Keep SKILL.md under 500 lines for context efficiency
- Write specific descriptions with trigger phrases
- Use progressive disclosure for detailed reference
- Include code examples and quick reference tables
MIT