Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

loom-semantic-model-report

Étoiles2

Forks1

Mis à jour11 juin 2026 à 06:41

Azure-native semantic model + report in CSA Loom — build a Loom-native tabular layer over Synapse/warehouse (Azure Analysis Services optional) and render reports natively, never requiring a Power BI / Fabric workspace. Call aas-client.ts + paginated-report-client.ts via /api/powerbi and /api/items. Triggers on semantic model, tabular model, TMSL, DAX, measure, RLS, Power BI, paginated report, RDL, dataset.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

fgarofalo56

fgarofalo56/csa-inabox

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Développeurs de logicielsProfessions informatiques et mathématiques·SOC 15-1252

SKILL.md

readonly

name	loom-semantic-model-report
description	Azure-native semantic model + report in CSA Loom — build a Loom-native tabular layer over Synapse/warehouse (Azure Analysis Services optional) and render reports natively, never requiring a Power BI / Fabric workspace. Call aas-client.ts + paginated-report-client.ts via /api/powerbi and /api/items. Triggers on semantic model, tabular model, TMSL, DAX, measure, RLS, Power BI, paginated report, RDL, dataset.
allowed-tools	Read, Grep, Glob, Bash

loom-semantic-model-report — Loom-native tabular + report (no Power BI/Fabric workspace)

A Loom semantic-model is a Loom-native tabular layer (metadata in Cosmos, evaluated over Synapse SQL / warehouse), with Azure Analysis Services (AAS) as an optional managed tabular engine. A report is rendered by the Loom-native report renderer. Neither requires a Power BI / Fabric workspace on the default path — Power BI counts as Fabric-family.

Clients

apps/fiab-console/lib/azure/aas-client.ts (XMLA TMSL exec + ARM + the Gov gate), synapse-sql-client.ts (the default eval engine), and paginated-report-client.ts (RDL render). aas-roles.ts carries RLS/OLS role authoring. Sovereign scopes come from cloud-endpoints.ts (aasScope(), aasXmlaUrl(), pbiXmlaScope(), and — opt-in only — getPbiScope() / getPbiEmbedHostname()).

Backends (explicit precedence)

Loom-native (DEFAULT) — tabular metadata in Cosmos, measures evaluated via executeQuery(dedicatedTarget(), …). No Power BI, no Fabric, works in every cloud.
AAS (opt-in) — set the AAS server; TMSL is executed over XMLA via aasXmlaUrl(). AAS is Commercial/GCC only — aas-client.ts guards on isGovCloud() and surfaces an honest "not available in this boundary" gate.
Power BI / Fabric (opt-in) — only when a workspace is explicitly bound; guard with assertFabricFamilyAvailable('powerbi'). Never the default.

Auth

UAMI-first chain. Loom-native uses the SQL scope; AAS uses aasScope() (note the literal * subdomain required by the AAS REST auth spec); opt-in Power BI uses getPbiScope() (4-way sovereign split).

BFF routes

/api/powerbi/** and /api/items/semantic-model|report/[id]/**. The model route dispatches on the selected backend (loom-native → AAS → Power BI) and returns { ok, data }. The report render route returns a real rendered artifact, not a placeholder.

Do / don't

DO default to the loom-native tabular layer; treat AAS and Power BI as opt-in.
DO author measures/RLS through guided editors (not a raw TMSL textbox as the only surface).
DON'T require a Power BI / Fabric workspace for the default path.
DON'T call api.powerbi.com without assertFabricFamilyAvailable('powerbi').

Cross-links

UI parity: docs/fiab/parity/semantic-model.md, report.md, paginated-report.md. Backend map rows: semantic-model / report in .claude/rules/no-fabric-dependency.md.

Plus depuis ce dépôt

même dépôt

loom-activator

fgarofalo56/csa-inabox

Azure-native activator (Reflex) in CSA Loom — back it with an Azure Monitor scheduled-query alert (or Logic App), never Fabric Activator. Call monitor-client.ts via /api/monitor. Triggers on activator, Reflex, alert, trigger, scheduled query rule, action group, notification, data activator.

2026-06-112

loom-cloud-endpoints

fgarofalo56/csa-inabox

MUST-READ root skill for CSA Loom. Resolve every Azure endpoint host and AAD scope from cloud-endpoints.ts instead of hard-coding management.azure.com / kusto.windows.net / dfs.core.windows.net. Triggers on sovereign cloud, GCC, GCC-High, DoD, IL5, endpoint, hostname, ARM, scope, token audience, government cloud.

2026-06-112

loom-data-pipeline

fgarofalo56/csa-inabox

Azure-native data pipeline in CSA Loom — back it with a Synapse pipeline (or ADF), never a Fabric Data pipeline. Call synapse-dev-client.ts + adf-client.ts via /api/adf and /api/synapse. Triggers on data pipeline, copy activity, dataflow, orchestration, trigger, integration runtime, ADF, Synapse pipeline.

2026-06-112

loom-eventhouse-kql

fgarofalo56/csa-inabox

Azure-native Eventhouse/KQL in CSA Loom — call Azure Data Explorer (ADX) via kusto-client.ts + kusto-arm-client.ts, never Fabric RTI. Use /api/adx routes. Triggers on KQL, Eventhouse, ADX, Kusto, real-time intelligence, KQL database, KQL dashboard, ingestion mapping, materialized view, RLS.

2026-06-112

loom-eventstream

fgarofalo56/csa-inabox

Azure-native eventstream in CSA Loom — back it with Azure Event Hubs (+ Stream Analytics for processing), never Fabric Eventstream. Call eventhubs-client.ts + stream-analytics-client.ts via /api/eventhubs. Triggers on eventstream, Event Hubs, streaming, real-time ingestion, consumer group, Stream Analytics, capture, schema registry.

2026-06-112

loom-items-bff

fgarofalo56/csa-inabox

The generic CSA Loom item BFF contract. Every item type exposes /api/items/<type>/<id>/<action> returning { ok, data, error } with a real backend call and honest config gates — never mock arrays or dead handlers. Triggers on BFF route, API route, item action, session validation, config gate, response shape, NextResponse, no-vaporware.

2026-06-112

name	loom-semantic-model-report
description	Azure-native semantic model + report in CSA Loom — build a Loom-native tabular layer over Synapse/warehouse (Azure Analysis Services optional) and render reports natively, never requiring a Power BI / Fabric workspace. Call aas-client.ts + paginated-report-client.ts via /api/powerbi and /api/items. Triggers on semantic model, tabular model, TMSL, DAX, measure, RLS, Power BI, paginated report, RDL, dataset.
allowed-tools	Read, Grep, Glob, Bash

loom-semantic-model-report — Loom-native tabular + report (no Power BI/Fabric workspace)

Clients

Backends (explicit precedence)

Loom-native (DEFAULT) — tabular metadata in Cosmos, measures evaluated via executeQuery(dedicatedTarget(), …). No Power BI, no Fabric, works in every cloud.
AAS (opt-in) — set the AAS server; TMSL is executed over XMLA via aasXmlaUrl(). AAS is Commercial/GCC only — aas-client.ts guards on isGovCloud() and surfaces an honest "not available in this boundary" gate.
Power BI / Fabric (opt-in) — only when a workspace is explicitly bound; guard with assertFabricFamilyAvailable('powerbi'). Never the default.

Auth

BFF routes

Do / don't

DO default to the loom-native tabular layer; treat AAS and Power BI as opt-in.
DO author measures/RLS through guided editors (not a raw TMSL textbox as the only surface).
DON'T require a Power BI / Fabric workspace for the default path.
DON'T call api.powerbi.com without assertFabricFamilyAvailable('powerbi').

Cross-links

UI parity: docs/fiab/parity/semantic-model.md, report.md, paginated-report.md. Backend map rows: semantic-model / report in .claude/rules/no-fabric-dependency.md.