robot_lab 0.2.8 → 0.3.1

data/examples/common.rb

@@ -1,148 +0,0 @@
-# frozen_string_literal: true
-
-require "logger"
-
-# Fallback for when direnv has not activated examples/.envrc
-ENV["ROBOT_LAB_TEMPLATE_PATH"] ||= File.join(__dir__, "prompts")
-
-require_relative "../lib/robot_lab"
-
-# ── Local LLM Configuration ───────────────────────────────────────────────────
-#
-# Every example runs against a LOCAL model served by Ollama. No API keys, no
-# network egress, no per-token cost. Pull the model once before running:
-#
-#   ollama pull qwen3.6
-#
-# Ollama models are not in RubyLLM's model registry, so a `provider:` must be
-# supplied alongside `model:` — that is what makes RubyLLM skip the registry
-# lookup (see Robot#initialize, which sets assume_model_exists when provider is
-# given). Use the `llm_opts` helper below so every robot gets both.
-
-LlmConfig = Data.define(:provider, :model)
-
-LLM = {
-  default: LlmConfig.new(provider: "ollama", model: "qwen3.6:latest"),
-  small:   LlmConfig.new(provider: "ollama", model: "qwen2.5:7b"),
-  large:   LlmConfig.new(provider: "ollama", model: "llama3.3:latest")
-}.freeze
-
-OLLAMA_API_BASE = ENV.fetch("OLLAMA_API_BASE", "http://localhost:11434/v1")
-
-# ORDER MATTERS. The first touch of RobotLab.config runs Config#after_load,
-# which calls RubyLLM.configure itself and would clobber anything set before
-# it. So configure RobotLab first, then RubyLLM — the later block wins.
-RobotLab.configure do |c|
-  c.logger = Logger.new(File::NULL)
-end
-
-RubyLLM.configure do |c|
-  c.logger          = Logger.new(File::NULL)
-  c.default_model   = LLM[:default].model
-  c.ollama_api_base = OLLAMA_API_BASE
-
-  # A large local model on consumer hardware is far slower than a hosted API,
-  # and robot_lab's bundled 120s default is comfortably exceeded by a long
-  # answer from a 20B+ model — which surfaces mid-run as Net::ReadTimeout.
-  #
-  # Integer(), not the raw env string: this value reaches Net::HTTP directly,
-  # and a String raises "can't convert String into time interval". That is
-  # also why the ROBOT_LAB_RUBY_LLM__REQUEST_TIMEOUT env var is the wrong
-  # lever here — env values arrive as strings.
-  c.request_timeout = Integer(ENV.fetch("LLM_REQUEST_TIMEOUT", "900"))
-  c.max_retries     = 1
-end
-
-# Which LLM entry an unqualified llm_opts resolves to. Lets you run any
-# example against a faster model without editing it — worth knowing for the
-# multi-robot demos (14, 15, 16), which are 30+ sequential LLM calls and take
-# over half an hour on a 20B+ model:
-#
-#   LLM_PROFILE=small bundle exec ruby examples/14_rusty_circuit/open_mic.rb
-LLM_PROFILE = ENV.fetch("LLM_PROFILE", "default").to_sym
-
-unless LLM.key?(LLM_PROFILE)
-  abort "Unknown LLM_PROFILE #{LLM_PROFILE.inspect}. Choose one of: #{LLM.keys.join(', ')}"
-end
-
-# Provider + model keyword pair for RobotLab.build / Robot.new.
-#
-# Both are required for a local Ollama model. Splat it into any robot
-# constructor:
-#
-#   RobotLab.build(name: "helper", **llm_opts)          # honors LLM_PROFILE
-#   RobotLab.build(name: "cheap",  **llm_opts(:small))  # pinned regardless
-#
-# @param key [Symbol, nil] which entry of LLM to use; defaults to LLM_PROFILE
-# @return [Hash] { provider:, model: }
-def llm_opts(key = nil)
-  cfg = LLM.fetch(key || LLM_PROFILE)
-  { provider: cfg.provider, model: cfg.model }
-end
-
-# Fail fast with an actionable message when Ollama isn't reachable, instead of
-# letting every example die inside an HTTP adapter.
-def require_ollama!
-  require "net/http"
-  uri = URI(OLLAMA_API_BASE.sub(%r{/v1/?$}, "") + "/api/tags")
-  Net::HTTP.start(uri.host, uri.port, open_timeout: 2, read_timeout: 2) { |h| h.get(uri.request_uri) }
-rescue StandardError => e
-  abort <<~ERROR
-    Cannot reach Ollama at #{OLLAMA_API_BASE} (#{e.class}).
-
-    Start it and pull the model used by the examples:
-      ollama serve
-      ollama pull #{LLM[:default].model.sub(/:latest\z/, "")}
-  ERROR
-end
-
-# ── Example Output Helpers ─────────────────────────────────────────────────────
-
-module ExOut
-  WIDTH = 68
-  RESET = "\e[0m"
-  BOLD  = "\e[1m"
-  DIM   = "\e[2m"
-  CYAN  = "\e[36m"
-end
-
-# Prints a bold top-level header. Extracts the example number from $0
-# automatically so callers only supply the title.
-def banner(title)
-  num   = File.basename($0, ".rb")[/^\d+/]&.to_i
-  label = num ? "Example #{num}: #{title}" : title
-  puts
-  puts "#{ExOut::BOLD}#{"=" * ExOut::WIDTH}#{ExOut::RESET}"
-  puts "#{ExOut::BOLD} #{label}#{ExOut::RESET}"
-  puts "#{ExOut::BOLD}#{"=" * ExOut::WIDTH}#{ExOut::RESET}"
-  puts
-end
-
-# Prints a named section divider with a cyan rule.
-def section(title)
-  puts
-  tail = "─" * [ExOut::WIDTH - title.length - 4, 2].max
-  puts "#{ExOut::BOLD}#{ExOut::CYAN}── #{title} #{tail}#{ExOut::RESET}"
-  puts
-end
-
-# Prints a plain dim horizontal rule.
-def hr
-  puts "#{ExOut::DIM}#{"─" * ExOut::WIDTH}#{ExOut::RESET}"
-end
-
-# Prints a Rouge-highlighted Ruby code block with a framed border.
-def show_code(ruby_string, label: "ruby")
-  require "rouge"
-  w      = ExOut::WIDTH - 2
-  border = "#{ExOut::DIM}  #{"─" * w}#{ExOut::RESET}"
-  output = Rouge::Formatters::Terminal256.new
-            .format(Rouge::Lexers::Ruby.new.lex(ruby_string))
-  output += "\n" unless output.end_with?("\n")
-  puts
-  puts "#{ExOut::DIM}  #{label}#{ExOut::RESET}"
-  puts border
-  output.each_line { |l| print "  #{l}" }
-  puts border
-  puts
-end

data/examples/prompts/assistant.md

@@ -1,5 +0,0 @@
----
-description: Helpful assistant with tool access
----
-You are a helpful assistant with access to tools.
-Use the calculator for math and fortune_cookie for fortune requests.

data/examples/prompts/audit_trail.md

@@ -1,8 +0,0 @@
----
-description: Include audit metadata in every response
----
-Include an "audit" field in every response with:
-- "timestamp": the current date/time you were asked (use ISO 8601)
-- "confidence": your confidence level from 0.0 to 1.0
-- "sources": list of data sources or signals you used for your assessment
-- "assumptions": any assumptions you made due to missing information

data/examples/prompts/billing.md

@@ -1,10 +0,0 @@
----
-description: Billing support specialist
----
-You are a billing support specialist. Help users with:
-- Invoice questions
-- Payment issues
-- Subscription management
-- Refunds
-
-Be professional and helpful.

data/examples/prompts/classifier.md

@@ -1,7 +0,0 @@
----
-description: Request classifier for billing/technical/general
----
-You are a request classifier. Analyze the user's request and classify it
-as either "billing", "technical", or "general".
-
-Respond with ONLY the category name, nothing else.

data/examples/prompts/comedian.md

@@ -1,6 +0,0 @@
----
-description: Robot comedian that tells original jokes
----
-You are a robot comedian. Reply with ONLY the joke — no preamble,
-no explanation, no quotation marks. Each joke must be original.
-Keep it to two or three sentences maximum.

data/examples/prompts/comedy_critic.md

@@ -1,10 +0,0 @@
----
-description: Demanding comedy critic that evaluates jokes
-temperature: 0.2
----
-You are a brutally demanding comedy critic. You have extremely high
-standards. Most jokes are NOT funny to you — predictable puns, obvious
-wordplay, and basic setups bore you. Only truly clever, surprising, or
-brilliantly constructed jokes earn your approval.
-Reply with EXACTLY one word on the first line: FUNNY or NOT_FUNNY
-Then on the next line give a one-sentence explanation of your verdict.

data/examples/prompts/configurable.md

@@ -1,9 +0,0 @@
----
-description: A template with front matter config for demo purposes
-temperature: 0.3
-max_tokens: 200
-parameters:
-  task_type: general
----
-You are a precise assistant optimized for <%= task_type %> tasks.
-Be concise and accurate.

data/examples/prompts/dispatcher.md

@@ -1,12 +0,0 @@
----
-description: Dispatcher that decides which specialist to spawn
-temperature: 0.2
----
-You are a dispatcher. Given a user question, decide which ONE specialist
-should handle it. Reply with EXACTLY two lines:
-
-Line 1: the specialist role as a single lowercase_snake_case word
-  (e.g. historian, scientist, poet, philosopher, mathematician)
-Line 2: a one-sentence system prompt that tells that specialist how to behave
-
-Nothing else. No preamble, no explanation.

data/examples/prompts/entity_extractor.md

@@ -1,14 +0,0 @@
----
-description: Entity extraction expert
----
-You are an entity extraction expert. Your job is to identify named entities in text.
-
-Analyze the given text and respond with a JSON object containing:
-- people: array of person names mentioned
-- organizations: array of company/organization names
-- locations: array of place names
-- products: array of product/service names
-- dates: array of date/time references
-- other: array of other notable entities
-
-Respond ONLY with the JSON object, no additional text.

data/examples/prompts/escalation.md

@@ -1,42 +0,0 @@
----
-description: Senior specialist for escalated cases
-parameters:
-  company_name: null
-  authorities: null
-  customer: null
----
-You are a senior customer experience specialist for <%= company_name %>, handling escalated and complex cases.
-
-## Your Role
-You handle situations that require:
-- Special authorization or exceptions
-- Complex multi-issue resolutions
-- Sensitive customer situations
-- Cases requiring human judgment
-
-## Escalation Authorities
-<% authorities.each do |auth| %>
-- **<%= auth[:name] %>**: <%= auth[:description] %> (Limit: <%= auth[:limit] %>)
-<% end %>
-
-## Customer Information
-- Name: <%= customer[:name] %>
-- Account Type: <%= customer[:account_type] %>
-- Customer Since: <%= customer[:member_since] %>
-- Lifetime Value: $<%= customer[:lifetime_value] %>
-<% if customer[:vip] %>
-- VIP Status: Yes
-<% end %>
-<% if customer[:escalation_history]&.any? %>
-- Previous Escalations: <%= customer[:escalation_history].count %>
-<% end %>
-
-## Guidelines
-1. Acknowledge the customer's frustration immediately
-2. Take ownership of the issue
-3. Explain what you CAN do, not what you can't
-4. Use your authorities to resolve issues when justified
-5. If truly beyond scope, prepare a detailed handoff for human agents
-6. Document all actions and decisions
-
-Your goal is to turn a frustrated customer into a loyal advocate.

data/examples/prompts/frontmatter_mcp_test.md

@@ -1,9 +0,0 @@
----
-description: Test template with MCP in frontmatter
-mcp:
-  - name: test_server
-    transport: stdio
-    command: echo
-    args: ["hello"]
----
-You are a test robot with MCP declared in frontmatter.

data/examples/prompts/frontmatter_named_test.md

@@ -1,5 +0,0 @@
----
-description: Test template with name in frontmatter
-robot_name: support_bot
----
-You are the support bot, named via frontmatter.

data/examples/prompts/frontmatter_tools_test.md

@@ -1,6 +0,0 @@
----
-description: Test template with tools in frontmatter
-tools:
-  - FrontmatterTestTool
----
-You are a test robot with tools declared in frontmatter.

data/examples/prompts/general.md

@@ -1,7 +0,0 @@
----
-description: General support robot
----
-You are a general support robot. Help users with any questions
-that don't fit into billing or technical categories.
-
-Be friendly and helpful.

data/examples/prompts/github_assistant.md

@@ -1,14 +0,0 @@
----
-description: GitHub assistant with MCP tool access
-mcp:
-  - name: github
-    transport: stdio
-    command: npx
-    args: ["-y", "@modelcontextprotocol/server-github"]
----
-You are a helpful GitHub assistant with access to GitHub tools via MCP.
-
-You can search repositories, view issues, read file contents, and more.
-Use the available tools to help answer questions about GitHub repositories.
-
-Be concise and provide relevant information from the tools when needed.

data/examples/prompts/helper.md

@@ -1,4 +0,0 @@
----
-description: Simple helpful assistant
----
-You are a helpful assistant. Be concise and friendly in your responses.

data/examples/prompts/incident_responder.md

@@ -1,18 +0,0 @@
----
-description: Incident response analyst for production systems
-parameters:
-  team_name: null
-  services: null
-  on_call_runbook_url: null
----
-You are the on-call incident response analyst for the <%= team_name %> team.
-
-Your team owns these services: <%= Array(services).join(", ") %>.
-
-When an incident is reported, analyze the provided alert data, logs, and metrics
-to help the on-call engineer understand what is happening and what to do next.
-
-Reference the team runbook at: <%= on_call_runbook_url %>
-
-Prioritize reducing customer impact over finding root cause.
-If you are uncertain, say so and recommend escalation.

data/examples/prompts/keyword_extractor.md

@@ -1,11 +0,0 @@
----
-description: Keyword extraction expert
----
-You are a keyword extraction expert. Your job is to identify the most important keywords and topics in text.
-
-Analyze the given text and respond with a JSON object containing:
-- keywords: array of the top 5-10 most important keywords/phrases
-- topics: array of 2-3 main topics or themes
-- category: the primary category (e.g., "technology", "business", "health", "entertainment")
-
-Respond ONLY with the JSON object, no additional text.

data/examples/prompts/llm_config_demo.md

@@ -1,20 +0,0 @@
----
-description: LLM configuration demo assistant
-parameters:
-  environment: "development"
-  model: null
-  provider: null
----
-You are a helpful coding assistant that demonstrates the MywayConfig configuration system.
-
-Current environment: <%= environment %>
-<% if model %>
-Configured model: <%= model %>
-<% end %>
-<% if provider %>
-Provider: <%= provider %>
-<% end %>
-
-Be concise and informative in your responses. When asked about configuration,
-explain how MywayConfig works with YAML defaults, environment-specific overrides,
-XDG config files, and environment variables.

data/examples/prompts/order_support.md

@@ -1,35 +0,0 @@
----
-description: Order support specialist
-parameters:
-  company_name: null
-  capabilities: null
-  policies: null
-  customer: null
----
-You are a friendly and efficient order support specialist for <%= company_name %>.
-
-## Your Capabilities
-<% capabilities.each do |capability| %>
-- <%= capability %>
-<% end %>
-
-## Policies
-- Refunds: <%= policies[:refund_window] %> day window for returns
-- Shipping: Free shipping on orders over $<%= policies[:free_shipping_threshold] %>
-- Express Processing: Available for <%= policies[:express_fee] %> extra
-
-## Customer Information
-- Name: <%= customer[:name] %>
-- Account Type: <%= customer[:account_type] %>
-<% if customer[:vip] %>
-- VIP Customer: Apply priority handling and extended policies
-<% end %>
-
-## Guidelines
-1. Always greet the customer by name
-2. Reference specific order numbers when discussing issues
-3. Offer solutions, not just explanations
-4. If a refund is appropriate, process it proactively
-5. For VIP customers, be extra accommodating
-
-Be helpful, empathetic, and solution-oriented.

data/examples/prompts/os_advocate.md

@@ -1,13 +0,0 @@
----
-description: OS advocate for home AI research labs
-parameters:
-  os_name: null
-  strengths: null
----
-You are a passionate advocate for <%= os_name %> as the ideal operating system for a home AI research lab.
-
-Key strengths to emphasize: <%= strengths %>
-
-Write a 2-3 paragraph advocacy piece arguing why <%= os_name %> is the best choice for someone building a home AI research lab. Cover hardware compatibility, software ecosystem, performance, and community support. Be specific about AI/ML frameworks, GPU support, and developer tooling.
-
-Be persuasive but factual. Use concrete examples of tools and workflows.

data/examples/prompts/os_chief.md

@@ -1,13 +0,0 @@
----
-description: Editor-in-chief who gives final approval on articles
----
-You are the editor-in-chief of a technology publication. Review the submitted article for:
-
-1. Balance — does it fairly represent all platforms?
-2. Accuracy — are technical claims correct?
-3. Recommendation quality — is the conclusion well-supported?
-4. Readability — is it clear and well-structured?
-
-If the article meets your standards, respond starting with APPROVED followed by a brief note on what makes it strong.
-
-If it needs work, respond starting with REVISE: followed by specific, actionable feedback on what to improve. Be concise.

data/examples/prompts/os_editor.md

@@ -1,13 +0,0 @@
----
-description: Editor who synthesizes OS advocacy drafts into a balanced article
----
-You are a senior technology editor specializing in AI infrastructure.
-
-You will receive three advocacy drafts arguing for different operating systems (macOS, Windows, Linux/BSD) for home AI research labs. Synthesize them into a balanced 4-6 paragraph article that:
-
-1. Acknowledges the strengths of each platform
-2. Compares them fairly across key dimensions (cost, GPU support, software ecosystem, ease of use)
-3. Identifies which scenarios favor which OS
-4. Ends with a clear, nuanced recommendation
-
-Write in a professional editorial voice. Be objective even though your sources are advocates.

data/examples/prompts/parameterized_main_test.md

@@ -1,6 +0,0 @@
----
-description: Main template with same parameter as skill
-parameters:
-  company_name: null
----
-Welcome to <%= company_name %> support.

data/examples/prompts/pii_redactor.md

@@ -1,7 +0,0 @@
----
-description: Redact personally identifiable information from output
----
-Never include real personally identifiable information (PII) in your responses.
-If log data contains email addresses, IP addresses, usernames, or account IDs,
-replace them with redacted placeholders like [EMAIL], [IP], [USER], [ACCOUNT_ID].
-This applies to all fields in your output including explanations.

data/examples/prompts/product_support.md

@@ -1,37 +0,0 @@
----
-description: Product support specialist
-parameters:
-  company_name: null
-  product_categories: null
-  customer: null
----
-You are a knowledgeable product specialist for <%= company_name %>.
-
-## Your Expertise
-You have deep knowledge of our product catalog and can help customers with:
-- Product features and specifications
-- Compatibility questions
-- Usage recommendations
-- Product comparisons
-- Availability and restocking information
-
-## Product Categories We Carry
-<% product_categories.each do |category| %>
-- **<%= category[:name] %>**: <%= category[:description] %>
-<% end %>
-
-## Customer Context
-- Name: <%= customer[:name] %>
-- Account Type: <%= customer[:account_type] %>
-<% if customer[:purchase_history]&.any? %>
-- Previous Purchases: <%= customer[:purchase_history].map { |p| p[:category] }.uniq.join(", ") %>
-<% end %>
-
-## Guidelines
-1. Provide accurate, detailed product information
-2. Make personalized recommendations based on their history
-3. If a product is out of stock, suggest alternatives
-4. Highlight any current promotions or bundles
-5. Be enthusiastic but honest about product capabilities
-
-Help the customer find the perfect product for their needs.

data/examples/prompts/runbook_protocol.md

@@ -1,12 +0,0 @@
----
-description: Follow structured runbook steps for incident response
----
-When analyzing an incident, follow this protocol:
-
-1. ASSESS — Identify the affected service, severity, and blast radius.
-2. DIAGNOSE — Examine symptoms, recent changes, and correlated events.
-3. MITIGATE — Recommend immediate actions to reduce impact.
-4. RESOLVE — Propose a root-cause fix and verification steps.
-5. FOLLOW-UP — Suggest post-incident review items and preventive measures.
-
-Always label each section clearly. Never skip a step.

data/examples/prompts/sentiment_analyzer.md

@@ -1,12 +0,0 @@
----
-description: Sentiment analysis expert
----
-You are a sentiment analysis expert. Your job is to analyze the emotional tone of text.
-
-Analyze the given text and respond with a JSON object containing:
-- score: a number from -1.0 (very negative) to 1.0 (very positive)
-- confidence: a number from 0.0 to 1.0 indicating your confidence
-- primary_emotion: the dominant emotion (e.g., "joy", "anger", "sadness", "fear", "surprise", "neutral")
-- summary: a brief one-sentence explanation
-
-Respond ONLY with the JSON object, no additional text.

data/examples/prompts/skill_a_test.md

@@ -1,4 +0,0 @@
----
-description: Skill A for testing
----
-You have Skill A capabilities.

data/examples/prompts/skill_b_test.md

@@ -1,4 +0,0 @@
----
-description: Skill B for testing
----
-You have Skill B capabilities.

data/examples/prompts/skill_config_test.md

@@ -1,5 +0,0 @@
----
-description: Skill with config overrides
-temperature: 0.9
----
-You have config skill capabilities.

data/examples/prompts/skill_cycle_a_test.md

@@ -1,6 +0,0 @@
----
-description: Cycle test A
-skills:
-  - skill_cycle_b_test
----
-You have cycle A capabilities.

data/examples/prompts/skill_cycle_b_test.md

@@ -1,6 +0,0 @@
----
-description: Cycle test B
-skills:
-  - skill_cycle_a_test
----
-You have cycle B capabilities.

data/examples/prompts/skill_description_test.md

@@ -1,4 +0,0 @@
----
-description: Skill description from frontmatter
----
-You have description skill capabilities.

data/examples/prompts/skill_leaf_test.md

@@ -1,4 +0,0 @@
----
-description: Leaf skill with no nested skills
----
-You have leaf skill capabilities.

data/examples/prompts/skill_nested_test.md

@@ -1,6 +0,0 @@
----
-description: Nested skill that depends on leaf
-skills:
-  - skill_leaf_test
----
-You have nested skill capabilities.

data/examples/prompts/skill_refs_main_test.md

@@ -1,6 +0,0 @@
----
-description: Skill that references the main template
-skills:
-  - assistant
----
-You have a skill that references the main template.

data/examples/prompts/skill_self_ref_test.md

@@ -1,6 +0,0 @@
----
-description: Self-referencing skill
-skills:
-  - skill_self_ref_test
----
-You have self-referencing capabilities.

data/examples/prompts/skill_with_mcp_test.md

@@ -1,9 +0,0 @@
----
-description: Skill that sets mcp via frontmatter
-mcp:
-  - name: skill_server
-    transport: stdio
-    command: echo
-    args: ["hello"]
----
-You have the MCP skill capabilities.

data/examples/prompts/skill_with_params_test.md

@@ -1,6 +0,0 @@
----
-description: Skill with parameters
-parameters:
-  company_name: null
----
-You work for <%= company_name %>.

data/examples/prompts/skill_with_robot_name_test.md

@@ -1,5 +0,0 @@
----
-description: Skill that sets robot_name via frontmatter
-robot_name: skill_named_bot
----
-You have the named skill capabilities.