Appwrite Ruby

Server-side Ruby SDK for Appwrite, covering the usual backend auth and data operations. You get user management, database CRUD with the newer TablesDB class, file storage, teams, and function execution. The docs are clear about using keyword arguments and avoiding deprecated patterns like the old string column type. If you're building a Rails or Sinatra app that talks to Appwrite, this handles the API key auth flow and gives you proper SSR session handling with separate admin and per-request clients. Solid reference for the common patterns without much ceremony.

skills.sh installs: 172
GitHub stars: 20
last updated: Jun 3, 2026

View on GitHub

Install

$ npx -y skills add appwrite/agent-skills --skill appwrite-ruby --agent claude-code

Installs into .claude/skills of the current project.

Files

Appwrite Ruby SDK

Installation

gem install appwrite

Setting Up the Client

require 'appwrite'

include Appwrite

client = Client.new
    .set_endpoint('https://<REGION>.cloud.appwrite.io/v1')
    .set_project(ENV['APPWRITE_PROJECT_ID'])
    .set_key(ENV['APPWRITE_API_KEY'])

Code Examples

User Management

users = Users.new(client)

# Create user
user = users.create(user_id: ID.unique, email: 'user@example.com', password: 'password123', name: 'User Name')

# List users
list = users.list(queries: [Query.limit(25)])

# Get user
fetched = users.get(user_id: '[USER_ID]')

# Delete user
users.delete(user_id: '[USER_ID]')

Database Operations

Note: Use TablesDB (not the deprecated Databases class) for all new code. Only use Databases if the existing codebase already relies on it or the user explicitly requests it.

Tip: Prefer keyword arguments (e.g., database_id: '...') for all SDK method calls. Only use positional arguments if the existing codebase already uses them or the user explicitly requests it.