sigma-data-models

sigma-data-models is a skill for Claude Code from twells89/sigma-migration-skills. It costs 171 tokens per session (1,835 once invoked), scanned A, original, MIT.

Instructions for defining and managing Sigma data models, which organize warehouse tables, columns, calculations, relationships, filters, and access rules for analytics.

In plain words
What is it for?
Use them to build models from warehouse tables, add metrics and relationships, edit columns or sources, and retrieve or update model specifications.
Why use it?
They let you create or change a shared data definition through Sigma's REST API instead of assembling it manually in the interface.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the sigma-authoring plugin — 5 skills shipped together

Good fit Use them to build models from warehouse tables, add metrics and relationships, edit columns or sources, and retrieve or update model specifications.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/twells89/sigma-migration-skills/sigma-data-models
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add twells89/sigma-migration-skills --skill sigma-data-models
Clone the repo
git clone --depth 1 https://github.com/twells89/sigma-migration-skills

Made for: Claude Code.

Or install sigma-authoring, the plugin that ships this one along with the rest of its 5 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.

agentmods badge for sigma-data-models

README.md
[![agentmods](https://agentmods.dev/badge/skills/twells89/sigma-migration-skills/sigma-data-models/github.svg)](https://agentmods.dev/skills/twells89/sigma-migration-skills/sigma-data-models)
Your own site
<a href="https://agentmods.dev/skills/twells89/sigma-migration-skills/sigma-data-models"><img src="https://agentmods.dev/badge/skills/twells89/sigma-migration-skills/sigma-data-models/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.

agentmods 80×15 button for sigma-data-models

Your own site · 80×15
<a href="https://agentmods.dev/skills/twells89/sigma-migration-skills/sigma-data-models"><img src="https://agentmods.dev/badge/skills/twells89/sigma-migration-skills/sigma-data-models.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 171 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,835 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00171 $0.01835
Opus 5 $0.00086 $0.00918
Sonnet 5 $0.00034 $0.00367
Haiku 4.5 $0.00017 $0.00184

Measured 10d ago against content hash 42cb0719c656, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

sigma-data-models scanned grade A with 1 finding 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 10d ago.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

**Requirements:** `curl`, `jq`, `base64`. Your Sigma API credentials must have permission to create or edit data models, plus "Can edit" access on the destination folder (for create) or the existing data model (for updat
plugins/sigma-authoring/skills/sigma-data-models/SKILL.md · 87 lines

How it starts

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

Sigma Data Models (Author / Get / Update)

Build a Sigma data model spec — the JSON definition of pages, sources, columns, metrics, relationships, filters, controls, folder groupings, and column-level security — and round-trip it through the Sigma REST API.

This skill is for authoring from existing warehouse tables: a user knows their warehouse, wants to expose specific tables as a Sigma data model with the right joins, metrics, and governance, and needs help composing the spec. Conversions from other BI-tool formats (dbt schema.yml, LookML views, Tableau TDS, Power BI PBIT, Alteryx YXMD, etc.) are not in this skill — direct users to the Sigma data-model converter MCP / browser tool, which already handles those mappings.

Auth: Authenticate via the sigma-api skill first to set $SIGMA_BASE_URL and $SIGMA_API_TOKEN. This skill assumes both are already exported.

Requirements: curl, jq, base64. Your Sigma API credentials must have permission to create or edit data models, plus "Can edit" access on the destination folder (for create) or the existing data model (for update). If a request returns 403, ask your Sigma admin to confirm the credential's permissions.

Reference Index

Feature-specific JSON patterns live in reference/. Load each file when you identify the corresponding feature in the user's request — don't read every file up-front.

File When to load
reference/columns.md Calculated columns, formula columns, derived columns; renaming a column, changing a formula, warehouse-column ID conventions, column reference rules.
reference/metrics.md Metrics, aggregate measures, metric timelines, time-series / trend metrics; adding a metric to an existing table or changing aggregation.
reference/relationships.md Relationships, foreign-key linking, related tables, cross-table lookups; adding a relationship between an existing element and a new one (mixed-ID rule — see workflows/crud.md).
reference/sources.md Custom SQL sources, join sources, union sources, transpose sources; swapping a model's source kind on an existing model.
reference/filters.md Row filters, where clauses, date range filters, top-N; adding/removing a filter on an existing model.
reference/folders-groupings.md Folders, column groupings, column ordering, sort, organize columns; reordering existing columns.
reference/column-level-security.md Column-level security (CLS), data masking, restrict columns by team / user attribute; applying CLS to an existing column.
reference/controls.md List/dropdown, text input, text area, number input, number range, date, date range, slider, range slider, segmented, switch, checkbox, top-N controls; adding a control to an existing page.
reference/formatting.md Column or metric formatting — currency, percentage, date format, decimals, datetime; reformatting a column or metric on an existing model.
reference/calc-columns.md Calculated / derived / formula columns on a DM element. Covers shape, formula references, and the window-function silent-error gotcha (CountOver/SumOver etc. fail in DM element calc cols → workarounds).

Read the full file on GitHub · 87 lines

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.

  1. 10d ago First seen · 87 lines · 171 tokens per session scan A 42cb0719c656

Subscribe to this mod's changes

sigma-data-models is a skill published in the GitHub repository twells89/sigma-migration-skills (15 stars, last pushed today), licensed MIT. It adds 171 tokens to every session and 1,835 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

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

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

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens