Published skill URLs for direct agent prompts.

Use this skill when an agent should use Ansight Studio as a local stdio-backed MCP bridge to inspect, debug, verify, or extract evidence from a running or captured app session. Prefer Ansight MCP tools for apps, sessions, screenshots, logs, telemetry, annotations, remote app tools, databases, and sandbox files before falling back to direct simulator or device access.

Use this skill when implementing a custom Ansight remote tool for a .NET MAUI, .NET for Android, .NET for iOS, or .NET Mac Catalyst app. Create a narrow Ansight.Tools.ITool implementation with stable tool ids, ToolSchema arguments and results, ToolSecurity metadata, ToolScope guards, local-development MSBuild gating with AnsightRemoteToolsPolicy, registration through AddTool/AddTools or a WithMyAppTools extension, and verification through Ansight Studio or MCP.

Use this skill when installing or configuring Ansight in a .NET MAUI, .NET for Android, .NET for iOS, or .NET Mac Catalyst app. Use the all-in-one Ansight.Maui or Ansight packages by default, infer Studio registration metadata from the app, initialize the runtime in the correct startup path, register the app in Studio with ansight_register_app, issue a signed pairing config with ansight_issue_pairing_config, set AnsightRemoteToolsPolicy to AllowedWithWarnings, inject a global tool guard that enables tools in developer builds and denies all tools in release builds, install or recommend the ansight-app-inspection skill for the user's agent, and create ansight-readme.md with QR pairing next steps.

Use this skill when integrating Microsoft.Extensions.Logging with Ansight so application logs are mirrored into Ansight session timelines through Runtime.Event.

Use this skill when mirroring Sentry-captured warnings and exceptions into Ansight session timelines from the app's own capture points.

Use this skill when integrating Serilog with Ansight so Serilog events are mirrored into Ansight session timelines through a custom sink.