What is domo-to-sigma?

A migration tool for recreating Domo dashboards in Sigma, a cloud analytics platform. It converts dashboard pages, cards, datasets, and Beast Modes—Domo's SQL-like calculated fields.

Use it to discover Domo content, convert Beast Mode calculations, build Sigma data models and workbooks, carry over user data filters, and check value and visual parity.

It reduces the manual work of translating Domo calculations, data structures, filters, and dashboard layouts into Sigma while checking the results against the same warehouse.

domo-to-sigma — Skill for Claude Code by twells89

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/twells89/sigma-migration-skills

agentmods

npx agentmods add skills/twells89/sigma-migration-skills/domo-to-sigma

Made for: Claude Code.

Or install domo-to-sigma, the plugin that ships this one along with the rest of its 3 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/twells89/sigma-migration-skills/domo-to-sigma/github.svg)](https://agentmods.dev/skills/twells89/sigma-migration-skills/domo-to-sigma)

Your own site

<a href="https://agentmods.dev/skills/twells89/sigma-migration-skills/domo-to-sigma"><img src="https://agentmods.dev/badge/skills/twells89/sigma-migration-skills/domo-to-sigma/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/twells89/sigma-migration-skills/domo-to-sigma"><img src="https://agentmods.dev/badge/skills/twells89/sigma-migration-skills/domo-to-sigma.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 122 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 8,799 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 4 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

high Privilege Escalation · line 39
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
high Privilege Escalation · line 209
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
high Privilege Escalation · line 214
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
high Privilege Escalation · line 209
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00122	$0.08799
Opus 5	$0.00061	$0.04399
Sonnet 5	$0.00024	$0.01760
Haiku 4.5	$0.00012	$0.00880

Measured 8d ago against content hash 4e16968da992, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

domo-to-sigma scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

The scan reads SKILL.md. This mod also ships 38 executable files (converter/sql.mjs, plugins/domo-visuals/react.production.min.js, plugins/domo-visuals/sigma-plugin-sdk.umd.js, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/domo-to-sigma/skills/domo-to-sigma/SKILL.md · 587 lines

How it starts

The opening of the file, as written. The whole thing — 587 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Domo → Sigma Conversion

Status: GOLD — live end-to-end validated (2026-08-10). The gold acceptance run migrated a purpose-built 16-card Domo executive dashboard to a live Sigma workbook and passed 28/28 strict value-parity checks (100%) with zero exclusions, a fresh context-free 6/6 visual PASS, clean live column/layout/ control lint, and assert-phase6-ran.rb exit 0 / GREEN with an empty degradation ledger (no scope cuts, waivers, or residuals). The earlier Tier-A validation remains part of the evidence base: 48 cards / 24 chart types / 81 Beast Modes, plus the purpose-built cards, against a real Domo instance. It answered all three former open questions and disproved several doc-inferred shapes in refs/connection.md — card enumeration, the summary-number path, and page-layout geometry were all wrong. Read refs/live-validation-2026-07-30.md before trusting any private-API shape; where it and refs/connection.md disagree, live-validation wins. The public OAuth path is documented and stable. Gold proves the converter's live baseline; each customer migration must still run its own Phase-6 value, visual, layout, and security gates rather than inheriting the fixture's result. Compliance: before a production run, confirm with the customer's Domo account team that programmatic extraction for migration is acceptable — see refs/connection.md "Compliance note".

Read ALL of the following before replying or taking any action:

refs/connection.md — Domo auth (OAuth public API + developer access token for private API)
refs/beast-mode-to-sigma.md — Beast Mode (MySQL SQL) → Sigma formula mapping
refs/card-to-element.md — Domo card → Sigma element map. Read before Phase 5. Rule 0 (Summary Number → KPI, never a table) is the #1 fidelity fix; also covers filtering + no-liberties discipline.

Phase-scoped (read at its phase, not upfront): at Phase 5e, read refs/layout-visual-qa.md — the visual QA gate — before grading the layout.

General workbook-spec and data-model-spec authoring idioms (grid layout mechanics, chart/control shapes, DM column/relationship shapes) are deferred to the sigma-workbooks and sigma-data-models skills — this skill covers only what's Domo-specific: extraction, Beast Mode translation, and the card→element map.

Read the full file on GitHub · 587 lines

Files

What ships with it

60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

8d ago Changed · +20 lines 4e16968da992
12d ago First seen · 567 lines · 122 tokens per session scan A 7de1dc511b39

Subscribe to this mod's changes

domo-to-sigma is a skill published in the GitHub repository twells89/sigma-migration-skills (16 stars, last pushed yesterday), licensed MIT. It adds 122 tokens to every session and 8,799 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Analytics and metrics

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens