This one helps you catch broken doc comments before your Dart package goes live on pub.dev. It walks you through enabling the comment_references lint and running dart doc with a temp directory so you can validate without cluttering your workspace. The main insight here is using dart doc as a validation tool, not just a generator. You'll catch unresolved references and undefined macros that would otherwise slip through. It's straightforward advice, nothing fancy, but if you've ever published a package and realized your docs were full of dead links, you'll appreciate the prevention step.
npx skills add https://github.com/kevmoo/dash_skills --skill dart-doc-validation