tigrisdata/tigris-agents-plugins

tigris-access-keys

Use when creating, listing, assigning, or deleting access keys for Tigris Storage

First seen Apr 12, 2026

Installation

$ npx skills add tigrisdata/tigris-agents-plugins --skill tigris-access-keys

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from tigrisdata/tigris-agents-plugins.

npx skills add tigrisdata/tigris-agents-plugins

Browse all from tigrisdata/tigris-agents-plugins

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
License LICENSE
Default branch main
Open issues 0
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 4,898 B
  • docs SUMMARY.md 107 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 69 installs

SKILL.md

Tigris Access Keys

Access keys are programmatic credentials for the Tigris API. Key IDs use the tid prefix, secrets use the tsec prefix.

Commands

tigris access-keys list (alias: l)

List all access keys in the current organization.

tigris access-keys list
tigris access-keys list --json
Flag Alias Description Default
--format -f Output format (json, table, xml) table
--json Output as JSON

tigris access-keys create <name> (alias: c)

Create a new access key with the given name. The secret is shown only once — save it immediately.

tigris access-keys create my-ci-key
tigris access-keys create my-ci-key --json
Flag Alias Description Default
--format -f Output format (json, table) table
--json Output as JSON

tigris access-keys get <id> (alias: g)

Show details for an access key including its name, creation date, and assigned bucket roles.

tigris access-keys get tid_AaBbCcDdEeFf
tigris access-keys get tid_AaBbCcDdEeFf --json
Flag Alias Description Default
--format -f Output format (json, table) table
--json Output as JSON

tigris access-keys delete <id> (alias: d)

Permanently delete an access key. This revokes all access immediately.

tigris access-keys delete tid_AaBbCcDdEeFf --force
Flag Description
--force Skip confirmation prompt
--format / -f Output format (json, table; default: table)
--json Output as JSON

tigris access-keys assign <id> (alias: a)

Assign per-bucket roles to an access key. Pair each --bucket with a --role (Editor or ReadOnly), or use --admin for org-wide access.

# Single bucket
tigris access-keys assign tid_AaBb --bucket my-bucket --role Editor

# Multiple buckets with different roles
tigris access-keys assign tid_AaBb --bucket a,b --role Editor,ReadOnly

# Org-wide admin access
tigris access-keys assign tid_AaBb --admin

# Revoke all roles
tigris access-keys assign tid_AaBb --revoke-roles
Flag Alias Description
--bucket -b Bucket name(s), comma-separated. Each bucket pairs positionally with a --role value
--role -r Role(s) to assign (Editor, ReadOnly), comma-separated. Each role pairs with the corresponding --bucket
--admin Grant admin access to all buckets in the organization
--revoke-roles Revoke all bucket roles from the access key
--format -f Output format (json, table; default: table)
--json Output as JSON

Workflow

# 1. Create a key
tigris access-keys create my-app-key --json
# Save the tid_ and tsec_ values from the output!

# 2. Scope it to specific buckets
tigris access-keys assign tid_AaBb --bucket my-bucket --role Editor

# 3. Configure your environment (Tigris env vars)
export TIGRIS_STORAGE_ACCESS_KEY_ID=tid_AaBb
export TIGRIS_STORAGE_SECRET_ACCESS_KEY=tsec_XxYy
export TIGRIS_STORAGE_ENDPOINT=https://t3.storage.dev
export TIGRIS_STORAGE_BUCKET=my-bucket

Security Best Practices

  • Scope to specific buckets — avoid --admin unless truly needed
  • Use minimal roles — prefer ReadOnly when writes aren't required
  • Separate keys per app — create dedicated keys for each application or environment
  • Rotate keys regularly — delete old keys and create new ones
  • Never commit secrets — use environment variables or secret managers, not source code