<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/3cdd67b593bb44a9b2113bc3891864b4&quot; frameborder=&quot;0&quot; width=&quot;3434&quot; height=&quot;2575&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>2575</height><width>3434</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>2575</thumbnail_height><thumbnail_width>3434</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/3cdd67b593bb44a9b2113bc3891864b4-fc0cdc76fbfd845c.gif</thumbnail_url><duration>307.11</duration><title>Using the DX CLI</title><description>I walk through how to use the DX CLI from your IDE or command line. I cover setup with npm, running DX init, and generating a personal access token from DX profile settings with the right scopes, then installing required agent skills. Once set up, I show how agents can query the DX catalog and scorecards, and even run self service workflows. For the account service, the agent surfaces missing and failing checks, like a missing Slack team and a failing OpenTelemetry and New Relic migration. I also demonstrate remediating a catalog data cleanliness issue by adding a required Readme local development section, creating a pull request.</description></oembed>