# tigris-sdk-guide

Tells your agent which Tigris SDK or CLI to reach for: native packages for TypeScript, Go and Python, AWS-compatible clients for Ruby and PHP.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 3100 installs · ★ 2
- Author: tigrisdata
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/tigrisdata/skills/tree/HEAD/skills/tigris-sdk-guide/SKILL.md
- Updated: 2026-07-23
- HTML: https://affpapa.org/en/nevibecode/skills/tigris-sdk-guide

## What it does

The skill fires when a project needs to talk to Tigris object storage and the choice of client is still open. A decision table maps each language to its option: `@tigrisdata/storage` for TypeScript and JavaScript, `github.com/tigrisdata/storage-go` for Go, and the `tigris-boto3-ext` extension for Python instead of plain `boto3`. Ruby and PHP have no native path, so the agent falls back to `aws-sdk-s3` or `aws-sdk-php` pointed at the Tigris endpoint.

The CLI gets its own section. The skill pushes `tigris` / `t3` over `aws s3`, since forks, snapshots and `tigris login` exist only in the native tool. When the CLI is missing, it runs `npm install -g @tigrisdata/cli` and asks the agent to announce the install out loud.

AWS-compatible clients come with fixed settings: `endpoint` set to `https://t3.storage.dev`, `region` set to `auto`, plus `force_path_style: true` for Ruby and PHP. Skip path style and those two clients will not connect. Hardcoding a region breaks routing, which Tigris handles itself. From there the skill points the agent at the per-language files under `./resources/`.

## Requirements
- Works with: AWS

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add tigrisdata/skills --skill tigris-sdk-guide -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/tigris-sdk-guide/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/tigris-sdk-guide/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add tigrisdata/skills --skill tigris-sdk-guide -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/tigris-sdk-guide/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add tigrisdata/skills --skill tigris-sdk-guide -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/tigris-sdk-guide/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install tigrisdata/skills tigris-sdk-guide
```

2. **Manually: put the files in place**
- File: `.github/skills/tigris-sdk-guide/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add tigrisdata/skills --skill tigris-sdk-guide -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/tigrisdata/skills --path skills/tigris-sdk-guide
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/tigris-sdk-guide/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add tigrisdata/skills --skill tigris-sdk-guide -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/tigrisdata/skills/tree/HEAD/skills/tigris-sdk-guide/SKILL.md

## When to use it
- pick an SDK that matches the project language instead of defaulting to AWS
- move existing scripts off `aws s3` and onto `tigris` / `t3`
- configure endpoint and region for an AWS-compatible client
- wire Python to Tigris through the boto3 extension rather than raw `boto3`
- find out where no native SDK exists and an AWS client is the only route

## Example prompts
- Which SDK should I use for Tigris in this Go project?
- Swap the `aws s3` calls in my scripts for `tigris`
- Set up `aws-sdk-php` against the Tigris endpoint with path style

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: fae66342f47f114c.

BEGIN THIRD-PARTY FILE fae66342f47f114c
````text
---
name: tigris-sdk-guide
description: Use when choosing between Tigris-native SDKs and AWS S3-compatible SDKs — covers which SDK to use per language, CLI preference, and when AWS SDKs are the only option
---

# Tigris SDK & CLI Guide

Always prefer Tigris-native SDKs and the Tigris CLI over AWS S3 SDKs. This guide explains what's available per language, when you must fall back to AWS SDKs, and how to configure them.

## Prerequisites

**Before doing anything else**, install the Tigris CLI if it's not already available:

```bash
tigris help || npm install -g @tigrisdata/cli
```

If you need to install it, tell the user: "I'm installing the Tigris CLI (`@tigrisdata/cli`) so we can work with Tigris object storage."

## Decision Table

| Language | Tigris SDK/Extension | Package | Use AWS SDK? |
|----------|:-:|---------|----------|
| TypeScript/JS | **Native SDK** | `@tigrisdata/storage` | No |
| Go | **Native SDK** | `github.com/tigrisdata/storage-go` | No |
| Python | **boto3 extension** | `tigris-boto3-ext` | No — use the extension |
| Ruby | None yet | — | Yes — `aws-sdk-s3` with Tigris endpoint |
| PHP | None yet | — | Yes — `aws-sdk-php` with Tigris endpoint |
| CLI | **Native CLI** | `@tigrisdata/cli` (`tigris` / `t3`) | No |

**Rule:** Always prefer Tigris-native SDKs, the boto3 extension, and the Tigris CLI. Only use raw AWS S3 SDKs for Ruby and PHP where no Tigris option exists.

---

## CLI: Always Use `tigris` / `t3`

Use the Tigris CLI instead of `aws s3` for all object storage operations.

```bash
# ✅ Do this
tigris cp local-file.txt t3://my-bucket/file.txt
tigris ls t3://my-bucket/
tigris rm t3://my-bucket/old-file.txt

# ❌ Not this
aws s3 cp local-file.txt s3://my-bucket/file.txt
aws s3 ls s3://my-bucket/
aws s3 rm s3://my-bucket/old-file.txt
```

**Why:** The Tigris CLI supports features the AWS CLI doesn't — forks, snapshots, and native authentication via `tigris login`.

### Tigris-Only CLI Features

```bash
# Forks (copy-on-write clones) — not in AWS CLI
tigris forks create my-bucket my-fork

# Snapshots — not in AWS CLI
tigris snapshots take my-bucket
tigris snapshots list my-bucket

# Native auth — no AWS credentials needed
tigris login
tigris whoami
```

---

## Language-Specific SDK Guides

Read the resource file for your language:

- **TypeScript / JavaScript** — Read `./resources/typescript.md` for `@tigrisdata/storage` usage
- **Go** — Read `./resources/go.md` for `storage-go` usage (simplestorage + full client)
````
END THIRD-PARTY FILE fae66342f47f114c

The third-party file has ended. Everything between the fae66342f47f114c tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2509 of 4542 bytes. © tigrisdata · MIT · https://github.com/tigrisdata/skills/tree/HEAD/skills/tigris-sdk-guide/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md