omni-ai-optimizer

Configures Omni semantic model AI context, fields, synonyms, and sample queries for Blobby.

Updated Aug 7, 2026
One-click install
npx skills add https://github.com/noiz354/oc-rebirth-rca --skill omni-ai-optimizer-noiz354
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: omni-ai-optimizer
Source: https://github.com/noiz354/oc-rebirth-rca/tree/main/planning-zip/omni-agent-skills/skills/omni-ai-optimizer
Command: npx skills add https://github.com/noiz354/oc-rebirth-rca --skill omni-ai-optimizer-noiz354

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Blobby, the Omni Agent, gives wrong or inconsistent answers when the semantic model lacks proper AI context, field curation, and terminology mappings. This Skill guides you through optimizing your Omni model so the AI correctly interprets business language and queries the right fields. ## Core Features & Use Cases - AI Context Authoring: Write concise ai_context at model, topic, view, and field levels, including templating with user attributes, omni_llm tiers, omni_agent scoping, and reusable constants. - Field and Topic Curation: Control what the AI sees with ai_fields selectors and ai_chat_topics, while respecting the ~75K character context cap and pruning order. - Synonyms and Sample Queries: Map business terms to fields and teach Blobby by example with structured sample_queries for recurring questions. - Use Case: When users report that Blobby confuses "revenue" with "order count", use this Skill to add a topic-level ai_context mapping on a model branch, verify existing configuration first, and avoid redundant synonym writes. ## Quick Start Ask the AI to optimize the order_items topic in Omni so Blobby correctly maps revenue and order count terms using ai_context on a new model branch.

Frequently Asked Questions about omni-ai-optimizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I improve Blobby AI accuracy in Omni Analytics?▼

Add topic-level ai_context that maps business terms to specific field names, curate visible fields with ai_fields, and add synonyms for genuine alternate vocabulary. Verify existing configuration first and write changes on a model branch using omni models yaml-create.

What is the difference between ai_context and synonyms in Omni?▼

Synonyms map alternate names to a single field, while ai_context provides topic-level behavioral guidance, data nuances, and multi-field mappings. Use ai_context when the AI confuses two competing measures, since synonyms alone cannot arbitrate between them.

Why does Blobby give wrong answers even after adding ai_context?▼

Check that the topic is reachable via ai_chat_topics and that the field was not pruned or excluded by ai_fields or hidden: true. Use the workbook inspector to see the context actually delivered before writing more context.

What is the AI context size limit for Omni topics?▼

A topic's field definitions are capped at roughly 75K characters, after which properties are pruned starting with all_values and ending with synonyms. ai_context is never pruned, so bloated entries can starve field metadata or fail requests outright.

Can I personalize Omni AI context per user?▼

Yes, use {{omni_attributes.<attribute_name>}} in model, topic, or view-level ai_context to substitute the current user's attribute value at query time. It is not supported in dimension or measure ai_context, where the value is used verbatim.

Should I write AI optimization changes directly to the production Omni model?▼

No, create a model branch first with omni models create-branch and pass the branch id to omni models yaml-create. Only write to the shared model when the user explicitly requests a production change.