iris-development
Iris is Redis's umbrella for AI-focused products. Use this skill when integrating with the Iris Redis Agent Memory (RAM) data plane on Redis Cloud — recording session events for an AI agent, creating or searching long-term memories, configuring a memory store, or tuning background memory promotion. Code examples use the official `redis-agent-memory` (Python) and `@redis-iris/agent-memory` (TypeScript) SDKs.
Works with
--- name: iris-development description: Iris is Redis's umbrella for AI-focused products. Use this skill when integrating with the Iris Redis Agent Memory (RAM) data plane on Redis Cloud — recording session events for an AI agent, creating or searching long-term memories, configuring a memory store, or tuning background memory promotion. Code examples use the official `redis-agent-memory` (Python) and `@redis-iris/agent-memory` (TypeScript) SDKs. license: MIT --- # Iris: Redis Agent Memory **Iris** is the umbrella brand for Redis's AI-focused products. This skill currently covers one product in that family: **Redis Agent Memory (RAM)** — the persistent memory layer for AI agents, delivered as a managed service on Redis Cloud. Additional Iris products will be added as separate sections when they ship. Redis Agent Memory exposes a REST/JSON data-plane API with two memory tiers: - **Session memory** — append-only conversation history per session (working memory). - **Long-term memory** — semantically searchable records extracted from sessions (or created directly). A background **promotion** worker — managed by Redis Cloud — extracts durable facts from session events and writes them into long-term memory. ## Official SDKs All code samples use the official SDKs: | Language | Package | Class | Install | | ---------- | -------------------------- | ------------- | ---------------------------------- | | Python | `redis-agent-memory` | `AgentMemory` | `pip install redis-agent-memory` | | TypeScript | `@redis-iris/agent-memory` | `AgentMemory` | `npm add @redis-iris/agent-memory` | Both SDKs read the bearer token from `AGENT_MEMORY_API_KEY` and the default store ID from `AGENT_MEMORY_STORE_ID`. The production data-plane URL is `https://gcp-us-east4.memory.redis.io`; the exact URL for your service is also shown in the Cloud console after provisioning. ## When to Apply Reference these guidelines when: - Creating a memory service on Redis Cloud ([https://cloud.redis.io/#/agent-memory](https://cloud.redis.io/#/agent-memory)) - Wiring an agent to call `AgentMemory.add_session_event(...)` / `addSessionEvent(...)` - Searching long-term memory with `search_long_term_memory(...)` / `searchLongTermMemory(...)` - Choosing between session events and direct long-term memory writes ## Rule Categories by Priority | Priority | Category | Impact | Prefix | | -------- | ----------------------- | ------ | ------------ | | 1 | Setup & Cloud Service | HIGH | `setup-` | | 2 | Session Memory / Events | HIGH | `session-` | | 3 | Long-Term Memory | HIGH | `ltm-` | | 4 | Memory Promotion | MEDIUM | `promotion-` | ## Quick Reference ### 1. Setup & Cloud Service (HIGH) - [`setup-cloud-service`](references/setup-cloud-service.md) - Create a Memory service on Redis Cloud - [`setup-auth-token`](references/setup-auth-token.md) - Authenticate the SDK with a store API key ### 2. Session Memory / Events (HIGH) - [`session-when-to-use`](references/session-when-to-use.md) - Choose session events vs direct long-term memory - [`session-add-event`](references/session-add-event.md) - Append a session event correctly - [`session-retrieval`](references/session-retrieval.md) - Retrieve session memory and individual events ### 3. Long-Term Memory (HIGH) - [`ltm-bulk-create`](references/ltm-bulk-create.md) - Create long-term memories in bulk with idempotent IDs - [`ltm-search`](references/ltm-search.md) - Search long-term memory semantically with filters - [`ltm-organize`](references/ltm-organize.md) - Organize records with namespace, ownerId, topics, and memoryType ### 4. Memory Promotion (MEDIUM) - [`promotion-overview`](references/promotion-overview.md) - How background promotion works ## How to Use Read individual rule files under `references/` for detailed explanations and code examples: ``` references/setup-cloud-service.md references/session-add-event.md references/promotion-overview.md ``` Each rule file contains: - Brief explanation of why it matters - Correct example(s) with Python and TypeScript SDK code - Either an "Incorrect" example or "When to use / When NOT needed" guidance - Additional context and references
More Database skills
supabase-postgres-best-practices
supabase/agent-skills
Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.
prisma-database-setup
prisma/skills
Guides for configuring Prisma with different database providers (PostgreSQL, MySQL, SQLite, MongoDB, etc.). Use when setting up a new project, changing databases, or troubleshooting connection issues. Triggers on "configure postgres", "connect to mysql", "setup mongodb", "sqlite setup".
prisma-postgres
prisma/skills
Prisma Postgres setup and operations guidance across Console, create-db CLI, Management API, and Management API SDK. Use when creating Prisma Postgres databases, working in Prisma Console, provisioning with create-db/create-pg/create-postgres, or integrating programmatic provisioning with service tokens or OAuth.
