{"id":79600,"plugin_id":"plugins_6ab409346c7c8191bacd83080aee170d","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-04T00:11:27.352Z","digest":"54c6a89530b16b16e1f086111d88d64ec877d332bc48a513df1d5229bcbaa11d","against":null,"payload":{"description":"Inspect a supplied RDL report structure, datasets, parameters, grouping and rendering risks without fabricating execution.","included_files":[],"name":"inspect-rdl","skill_md_contents":"---\nname: inspect-rdl\ndescription: Inspect a supplied RDL report structure, datasets, parameters, grouping and rendering risks without fabricating execution.\n---\n\n# Inspect an existing RDL\nLoad the supplied `.rdl` file or paste. Confirm report definition dialect/version, report sections, page/body widths, margins, datasets, data sources, parameter declarations and expressions. Distinguish missing input from an empty report. Treat XML as untrusted; never run arbitrary embedded queries or expressions while inspecting.\nBuild a map: data source → dataset query → dataset fields → parameter mapping → tablix/list/chart → renderer. Mark inferred relationships separately from proven XML links. Read `../../references/paginated-architecture.md` and `../../references/parameter-mapping.md`.\nFor problems, find the earliest broken layer before editing. Offer a bounded RDL diff and non-destructive backups; when execution tools exist, validate XML, static references and render in the requested engine where supported. The `scripts/rdl_lint.py` utility gives *static hints only*; it is not the Report Builder validator.\nReturn: artifact examined; datasets, parameters and regions; numbered findings with evidence; minimal fix; test matrix; unverified behavior.\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"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}