microstrategy-to-sigma

microstrategy-to-sigma is a skill for Claude Code from twells89/sigma-migration-skills. It costs 107 tokens per session (8,585 once invoked), scanned B, original, MIT.

A skill for migrating MicroStrategy dossiers, reports, and classic semantic models into Sigma. It extracts the source content through the MicroStrategy API, converts it, and builds Sigma data models and workbooks.

In plain words
What is it for?
Use it when moving MicroStrategy content to Sigma: authenticate to MicroStrategy, extract the model and reports, generate the Sigma specifications, validate them, and verify that real report results match.
Why use it?
It provides a controlled conversion path with validation and result comparison, helping prevent empty or unverified workbooks from being delivered.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: reads .claude/ paths.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python3 scripts/mstr.py # login probe + project list.

Part of the microstrategy-to-sigma plugin — 2 skills shipped together

Good fit Use it when moving MicroStrategy content to Sigma: authenticate to MicroStrategy, extract the model and reports, generate the Sigma specifications, validate them, and verify that real report results match.

Compare 6 skills from other repositories ↓
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/microstrategy-to-sigma

Made for: Claude Code.

Or install microstrategy-to-sigma, the plugin that ships this one along with the rest of its 2 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 microstrategy-to-sigma

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

agentmods 80×15 button for microstrategy-to-sigma

Your own site · 80×15
<a href="https://agentmods.dev/skills/twells89/sigma-migration-skills/microstrategy-to-sigma"><img src="https://agentmods.dev/badge/skills/twells89/sigma-migration-skills/microstrategy-to-sigma.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 107 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 8,585 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. 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.00107 $0.08585
Opus 5 $0.00053 $0.04293
Sonnet 5 $0.00021 $0.01717
Haiku 4.5 $0.00011 $0.00859

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

Security

Grade B, and why

microstrategy-to-sigma scanned grade B with 2 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 12d ago.

The scan reads SKILL.md. This mod also ships 28 executable files (fixtures/build_schema.py, scripts/assert-phase6-ran.rb, scripts/bootstrap.ps1, …), 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.

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

both `~/.claude/settings.json` and `~/.sigma-migration/env`, so `get-token.sh`

Makes network callslowCapability

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

> - **NEVER hand-author a DM/workbook JSON and `curl`-POST it, and never ship empty
plugins/microstrategy-to-sigma/skills/microstrategy-to-sigma/SKILL.md · 526 lines

How it starts

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

MicroStrategy → Sigma migration

Windows / first run — run the environment doctor before anything else: bash scripts/doctor.sh (macOS/Linux/Git Bash) or powershell -ExecutionPolicy Bypass -File scripts\doctor.ps1 (Windows). It checks Ruby/Python/Node/bash and flags the Python "Store stub" + CRLF with exact fixes. Details: refs/environment.md.

⛔ THE ONE PATH (do not ship an unverified/empty workbook)

Convert with convert.py, POST its specs, then verify with verify_parity.py. Rules:

  • NEVER hand-author a DM/workbook JSON and curl-POST it, and never ship empty "placeholder" pages. Post only what convert.py produces. If MicroStrategy is unreachable (no session), STOP and tell the user to authenticate — don't build a shell.
  • verify_parity.py must be GREEN with REAL reports before you're done. It now refuses a vacuous pass — an expected_parity.json with 0 reports is "NOT parity-clean" (exit 1), never a silent green. An empty/placeholder workbook is never done.

Preflight the workbook spec before POST (mandatory)

Before POSTing any workbook spec, run both validators:

  1. ruby scripts/lib/preflight_lint.rb <spec.json> catches grouping and control grammar failures.
  2. From the companion sigma-workbooks skill, run ./scripts/validate-spec.sh <absolute-spec-path> to reject bare source-column self-references and list/segmented controls without a value-list source.

The API accepts a filters-only list control, but the picker is empty: filters names what changes; source supplies the values a user can select. API acceptance is not a shipping criterion. Date-range controls are different and correctly use filters without a separate value-list source. Fix every violation first — never POST past it, and never conclude a feature is "unsupported" from an Invalid kind error (it means the inner fields are wrong). Verified shapes: sigma-workbooks controls.md / tables.md.

Converter architecture (read if you know the other migration skills)

Read the full file on GitHub · 526 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.

  1. 12d ago First seen · 526 lines · 107 tokens per session scan B 65ff7307fec6

Subscribe to this mod's changes

microstrategy-to-sigma is a skill published in the GitHub repository twells89/sigma-migration-skills (16 stars, last pushed yesterday), licensed MIT. It adds 107 tokens to every session and 8,585 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, 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