dx-report-integration
Expert skill for embedding DevExpress Reports into applications — NuGet packages, DI registration, viewer/designer wiring, async export, ReportStorageWebExtension, toolbar and parameter editor customization, security, and troubleshooting. Use whenever someone needs to add a DevExpress report viewer or designer to WinForms, WPF, ASP.NET Core MVC, Razor Pages, Angular, React, or Blazor; configure Program.cs for reporting; set up npm packages and bundleconfig.json; export reports to PDF/Excel/Word without a preview; configure ReportStorageWebExtension or IReportProvider; customize viewer toolbar, tab panel, search panel, or parameter editors; implement authorization or CSRF protection; debug errors like "viewer not rendering", "Unable to process binding", "Internal Server Error", "Report not found", 400/404/CORS errors; or upgrade DevExpress versions.
Works with
This skill's source license couldn't be confirmed as safe to mirror here, so it isn't inlined. View the full skill directly on its source repository.
View on GitHubMore Debugging skills
diagnosing-bugs
mattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
explore-code
lllllllama/rigorpilot-skills
Rigor Improve implementation leaf skill for auditable candidate implementation in deep learning research repositories. Use when the researcher explicitly authorizes exploratory work on an isolated branch or worktree to transplant modules, adapt a backbone, add LoRA or adapter layers, replace a head, or stitch together meaningful low-risk migration ideas with rollback-aware records in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline reproduction, conservative debugging, environment setup, verified contribution claims, or default repository analysis.
safe-debug
lllllllama/rigorpilot-skills
Rigor Debug / Rigor Audit skill for deep learning research work. Use when the user pastes a traceback, terminal error, CUDA OOM, checkpoint load failure, shape mismatch, NaN loss symptom, or training failure and wants conservative diagnosis before any patching, with debug fixes clearly separated from research contributions. Do not use for broad refactoring, speculative adaptation, automatic exploratory patching, or general repository familiarization.
