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.
git clone --depth 1 https://github.com/twells89/sigma-migration-skillsnpx agentmods add skills/twells89/sigma-migration-skills/sisense-to-sigmaWrote 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.
[](https://agentmods.dev/skills/twells89/sigma-migration-skills/sisense-to-sigma)<a href="https://agentmods.dev/skills/twells89/sigma-migration-skills/sisense-to-sigma"><img src="https://agentmods.dev/badge/skills/twells89/sigma-migration-skills/sisense-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.
<a href="https://agentmods.dev/skills/twells89/sigma-migration-skills/sisense-to-sigma"><img src="https://agentmods.dev/badge/skills/twells89/sigma-migration-skills/sisense-to-sigma.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
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 →
- medium Rogue Agent · line 5 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00172 | $0.04244 |
| Opus 5 | $0.00086 | $0.02122 |
| Sonnet 5 | $0.00034 | $0.00849 |
| Haiku 4.5 | $0.00017 | $0.00424 |
Grade A, and why
sisense-to-sigma 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 12d 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.
> - **NEVER hand-author a DM/workbook JSON and `curl`-POST it, and never lay out How it starts
The opening of the file, as written. The whole thing — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sisense → Sigma migration
Windows / first run — run the environment doctor before anything else:
bash scripts/doctor.sh(macOS/Linux/Git Bash) orpowershell -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.
Convert a Sisense data model + dashboards into a Sigma data model + workbook. Pull the model schema export and the widget definitions over REST, translate JAQL / widget types / filters, emit the specs, then verify parity against numbers from Sisense's own JAQL engine. Translate what maps cleanly; flag what doesn't (custom JAQL functions, BloX/plugin widgets, scripted widgets) — never emit confidently-wrong logic.
Status — LIVE-VALIDATED (2026-06-17). A full end-to-end migration of the Sisense Sample ECommerce model + dashboard was run and verified at exact data parity: Sisense ElastiCube → Sisense Live-on-Snowflake → Snowflake (
DEMO_DB.SISENSE_ECOMMERCE) → Sigma data model (<dm-id>s) → Sigma workbook (d9312472). Total Revenue $39,759,625.515, Total Quantity 91,206, and the joined Revenue-by-Category breakdown all match Sisense JAQL exactly. The converter (jaql_expr.py+convert.py) was exercised against an 18-widget coverage corpus (every chart type + JAQL formula/level/ top-N/break-by). Known refinements: pie-chartcolorspec + bartopNdisplay-limit (values correct; display cap not yet enforced). Still flag — never fake — treemap/sunburst (no native Sigma equivalent) and unsupported JAQL functions. Seerefs/design-notes.md.
⛔ THE ONE PATH (do not improvise a workbook)
Run the phases below in order — Discover → Convert model → Convert dashboards → Verify (Phase 4). Rules:
- NEVER hand-author a DM/workbook JSON and
curl-POST it, and never lay out empty "placeholder" pages. Post only the specsconvert.pyproduces. If you can't reach Sisense (no host/token), STOP and tell the user to authenticate — do not build a shell.- Both verify gates must be GREEN with REAL elements before you're done.
verify_parity.pyandverify_layout.pynow refuse a vacuous pass — a workbook with zero widgets/checks is RED, not "0/0 GREEN". A migration with nothing to verify is not done.READ FIRST —
refs/operating-contract.md: the fidelity guardrails (render + value-check EVERY page against the source; never ship empty or silently drop a tile; don't spin — surface blockers). Modeling strategy —refs/modeling-strategy.md: faithful reproduction of the source model is the DEFAULT (parity is the gate); an upstream OBT or Sigma-native materialization is an OPT-IN optimization for hot, join-heavy dashboards, re-verified against the same parity oracle. The converter never auto-flattens. Readrefs/before relying on shapes:sisense-rest-api.md(validated endpoint map + auth + the access-key-vs-token gotcha),jaql-mapping.md(JAQL → Sigma formula + what's flagged),widget-type-mapping.md(widget → Sigma element coverage),design-notes.md(architecture, the Snowflake-parity requirement, hard problems, the Layout translator),layout-visual-qa.md(the render-and-inspect gate). For canonical Sigma spec shapes, defer to thesigma-data-models/sigma-workbooksskills.
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.
- fixtures/dashboards.json 56 KB
- fixtures/model_ecommerce.json 26 KB
- refs/app-recommendation-signals.md 3.1 KB
- refs/catalogs/aggregation.json 4.2 KB
- refs/catalogs/control.json 4.9 KB
- refs/catalogs/jaql-function.json 12 KB
- refs/catalogs/number-format.json 1.8 KB
- refs/catalogs/viz-kind.json 7.0 KB
- refs/catalogs/workbook-feature.json 5.6 KB
- refs/design-notes.md 12 KB
- refs/environment.md 5.7 KB
- refs/jaql-mapping.md 2.0 KB
- refs/layout-visual-qa.md 19 KB
- refs/migration-report-format.md 5.9 KB
- refs/modeling-strategy.md 6.7 KB
- refs/open-items.md 3.8 KB
- refs/operating-contract.md 2.8 KB
- refs/phase-e-enhance.md 12 KB
- refs/sisense-coverage.md 24 KB
- refs/sisense-rest-api.md 3.7 KB
- refs/source-anchors.md 12 KB
- refs/visual-similarity.md 5.0 KB
- refs/widget-type-mapping.md 2.0 KB
- refs/workbook-code-release-gaps.md 2.0 KB
- schemas/app-plan.schema.json 3.0 KB
- scripts/apply_sigma_rls.py 19 KB runs code
- scripts/assert-phase6-ran.rb 254 KB runs code
- scripts/bootstrap.ps1 41 KB runs code
- scripts/bootstrap.sh 44 KB runs code
- scripts/build-migration-report.rb 32 KB runs code
- scripts/build-sisense-accounting.py 23 KB runs code
- scripts/build-sisense-control-scope.py 7.7 KB runs code
- scripts/build-sisense-parity.py 11 KB runs code
- scripts/cleanup-orphan-workbooks.rb 11 KB runs code
- scripts/convert.py 48 KB runs code
- scripts/detect_rls.py 6.7 KB runs code
- scripts/discover.py 5.1 KB runs code
- scripts/doctor.ps1 24 KB runs code
- scripts/doctor.sh 34 KB runs code
- scripts/enhance-app-plan.rb 8.1 KB runs code
- scripts/enhance-apply.rb 48 KB runs code
- scripts/enhance-scan.rb 38 KB runs code
- scripts/enhance-select.rb 5.3 KB runs code
- scripts/escalate-gap.py 9.8 KB runs code
- scripts/fetch_inodes.py 1.8 KB runs code
- scripts/finalize-sisense-report.py 8.7 KB runs code
- scripts/find-or-pick-dm.rb 29 KB runs code
- scripts/gen-coverage-matrix.py 5.7 KB runs code
- scripts/get_token.py 8.2 KB runs code
- scripts/get-token.sh 4.4 KB runs code
- scripts/jaql_expr.py 6.6 KB runs code
- scripts/lib/anchor_values.rb 5.6 KB runs code
- scripts/lib/blind_grade.rb 8.8 KB runs code
- scripts/lib/cli_encoding.rb 1.8 KB runs code
- scripts/lib/code_rep.mjs 7.9 KB runs code
- scripts/lib/code_rep.py 9.3 KB runs code
- scripts/lib/code_rep.rb 11 KB runs code
- scripts/lib/control_lint.rb 22 KB runs code
- scripts/lib/coverage_catalog.py 6.1 KB runs code
- scripts/lib/degradation_ledger.rb 20 KB runs code
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.
- 12d ago First seen · 267 lines · 172 tokens per session scan A d0f7b297a249
sisense-to-sigma is a skill published in the GitHub repository twells89/sigma-migration-skills (16 stars, last pushed yesterday), licensed MIT. It adds 172 tokens to every session and 4,244 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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.
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…
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…