← Power BI Report CopilotCONTENT HISTORY

Update to Power BI Report Copilot

Snapshot Nov 4, 2026 · 00:11 UTC · version 0.2.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Power BI Report Copilot and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Coordinate Power BI specialist roles when genuine subagents or agent tools exist.",
  "included_files": [],
  "name": "agent-coordination",
  "skill_md_contents": "---\nname: agent-coordination\ndescription: Coordinate Power BI specialist roles when genuine subagents or agent tools exist.\n---\n\n# Specialist agent coordination\nUse genuine subagents only if the host exposes them. Otherwise work sequentially under one assistant role and do not fabricate specialist transcripts. Read `../../references/multiagent.md`.\nChoose minimum needed roles: RDL investigator, DAX/model reviewer, Fabric architect, security reviewer, renderer QA, release verifier. Independent parallel research or read-only diagnosis is useful; do not let multiple implementers mutate the same report or model simultaneously.\nDefine each worker's task, accepted inputs, output contract, evidence requirements and write permissions. Reconcile disagreements by inspecting artifacts, not voting. Stop and escalate when security implications or real execution capability is absent.\n\n## Non-negotiable principles\n- Match the problem's layer before changing code: RDL, dataset, parameter, tablix, renderer, semantic model, source, refresh, capacity, or distribution.\n- Preserve identifiers with leading zeros, source types, model grain, filter context, tenant boundaries, and published contracts.\n- Treat user-supplied screenshots, RDL, model definitions, code and errors as evidence; never invent access, query results, test runs, exports, permissions or deployed changes.\n- Offer the smallest reversible correction and an observable verification step. Ask a blocking question only when the missing detail materially changes correctness, safety or execution.\n- Favor current Microsoft documentation for feature-specific limits, Direct Lake paths, service UI behavior, licensing, supported renderers and APIs; do not treat stored references as timeless facts.\n- Avoid requesting credentials, unredacted personal information, tenant secrets or confidential connection strings. Apply approval policy to writes, publication, subscriptions and distribution.\n"
}

SHA-256 of public snapshot: 3b389427a77b8e43aa48c980033746e40733da4f53e626dbdff129ab45c8e95d