Skip to main content
Ruby client library for the Skald API.

Installation

Add this line to your application’s Gemfile:
And then execute:
Or install it yourself as:

Requirements

  • Ruby 3.0.0 or higher

Usage

Initialize the client

Memo Management

Create a Memo

Create a new memo that will be automatically processed (summarized, tagged, chunked, and indexed for search):
Required Fields:
  • title (string, max 255 chars) - The title of the memo
  • content (string) - The full content of the memo
Optional Fields:
  • metadata (hash) - Custom JSON metadata
  • reference_id (string, max 255 chars) - An ID from your side that you can use to match Skald memo UUIDs with e.g. documents on your end
  • tags (array of strings) - Tags for categorization
  • source (string, max 255 chars) - An indication from your side of the source of this content, useful when building integrations
  • expiration_date (string) - ISO 8601 timestamp for automatic memo expiration

Get a Memo

Retrieve a memo by its UUID or your reference ID:
The get_memo() method returns complete memo details including content, AI-generated summary, tags, and content chunks.

List Memos

List all memos with pagination:
Parameters:
  • page (integer, optional) - Page number (default: 1)
  • page_size (integer, optional) - Results per page (default: 20, max: 100)

Update a Memo

Update an existing memo by UUID or reference ID:
Note: When you update the content field, the memo will be automatically reprocessed (summary, tags, and chunks regenerated). Updatable Fields:
  • title (string)
  • content (string)
  • metadata (hash)
  • client_reference_id (string)
  • source (string)
  • expiration_date (string)

Delete a Memo

Permanently delete a memo and all associated data:
Warning: This operation permanently deletes the memo and all related data (content, summary, tags, chunks) and cannot be undone.

Search Memos

Search through your memos using various search methods with optional filters:

Search Methods

  • chunk_vector_search - Semantic search on memo chunks for detailed content search
  • title_contains - Case-insensitive substring match on memo titles
  • title_startswith - Case-insensitive prefix match on memo titles

Search Parameters

  • query (string, required) - The search query
  • search_method (SearchMethod, required) - One of the search methods above
  • limit (integer, optional) - Maximum results to return (1-50, default 10)
  • filters (array, optional) - Array of filter hashes to narrow results (see Filters section below)

Search Response

  • uuid - Unique identifier for the memo
  • title - Memo title
  • summary - Auto-generated summary for the memo
  • content_snippet - A snippet containing the beginning of the memo
  • distance - A decimal from 0 to 2 determining how close the result was deemed to be to the query when using semantic search (chunk_vector_search). The closer to 0 the more related the content is to the query. nil if using title_contains or title_startswith.

Chat with Your Knowledge Base

Ask questions about your memos using an AI agent. The agent retrieves relevant context and generates answers with inline citations.

Non-Streaming Chat

Streaming Chat

For real-time responses, use streaming chat:

Chat Parameters

  • query (string, required) - The question to ask
  • filters (array, optional) - Array of filter hashes to focus chat context on specific sources (see Filters section below)

Chat Response

Non-streaming responses include:
  • ok (boolean) - Success status
  • response (string) - The AI’s answer
  • intermediate_steps (array) - Steps taken by the agent (for debugging)
Streaming responses yield events:
  • { type: 'token', content: string } - Each text token as it’s generated
  • { type: 'done' } - Indicates the stream has finished

Generate Documents

Generate documents based on prompts and retrieved context from your knowledge base. Similar to chat but optimized for document generation with optional style/format rules.

Non-Streaming Document Generation

Streaming Document Generation

For real-time document generation, use streaming:

Generate Document Parameters

  • prompt (string, required) - The prompt describing what document to generate
  • rules (string, optional) - Optional style/format rules (e.g., “Use formal language. Include sections: X, Y, Z”)
  • filters (array, optional) - Array of filter hashes to control which memos are used for generation (see Filters section below)

Generate Document Response

Non-streaming responses include:
  • ok (boolean) - Success status
  • response (string) - The generated document
  • intermediate_steps (array) - Steps taken by the agent (for debugging)
Streaming responses yield events:
  • { type: 'token', content: string } - Each text token as it’s generated
  • { type: 'done' } - Indicates the stream has finished

Filters

Filters allow you to narrow down results based on memo metadata. You can filter by native fields or custom metadata fields. Filters are supported in search(), chat(), generate_doc(), and their streaming variants. See Filters for complete documentation.

Filter Structure

Native Fields

Native fields are built-in memo properties:
  • title - Memo title
  • source - Source system (e.g., “notion”, “confluence”)
  • client_reference_id - Your external reference ID
  • tags - Memo tags (array)

Custom Metadata Fields

You can filter on any field from the metadata hash you provided when creating the memo.

Filter Operators

  • eq - Equals (exact match)
  • neq - Not equals
  • contains - Contains substring (case-insensitive)
  • startswith - Starts with prefix (case-insensitive)
  • endswith - Ends with suffix (case-insensitive)
  • in - Value is in array (requires array value)
  • not_in - Value is not in array (requires array value)

Filter Examples

Combining Multiple Filters

When you provide multiple filters, they are combined with AND logic (all filters must match):

Filters with Chat

Focus chat context on specific sources:

Filters with Document Generation

Control which memos are used for document generation:

Error Handling