{"id":79596,"plugin_id":"plugins_6ab409346c7c8191bacd83080aee170d","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-04T00:11:27.258Z","digest":"c29d71b360c1dd34bd1f937a09ca5f5fa2c2d35f3c0f8133f90d3b9f4c293b5f","against":null,"payload":{"description":"Diagnose paginated PDF, Excel, CSV, Word, print and blank-page/rendering defects.","included_files":[],"name":"export-rendering","skill_md_contents":"---\nname: export-rendering\ndescription: Diagnose paginated PDF, Excel, CSV, Word, print and blank-page/rendering defects.\n---\n\n# Export and rendering correctness\nIdentify actual target renderer. Browser preview may use soft-page breaks; PDF/print have physical page geometry; Excel and CSV differ in cell structure and formatting. Consult `../../references/renderer-matrix.md` and original `../../references/original/paginated_export_delivery_reference.md`.\nFor blank PDF pages calculate body width + margins <= physical page width, but inspect protruding report items and nested rectangles. For Excel investigate merged cells, inconsistent column boundaries, worksheet names and numeric-as-text formatting. CSV is dataset-oriented, not a page representation.\nDo not claim one group page break produces separate output files. Supply a measured layout table and specific adjustments, plus tests for multiple parameter values, long text, narrow and wide pages, locale and file recipients. Never invent actual export evidence.\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":{}}