Review A Skill

It walks you through the four step process: preview the content for safety issues, inspect metadata with the info command, validate structure, then decide whether to curate with notes and verification or remove it entirely. The guardrails are smart, especially the reminder to check dependencies before removing anything and always dry run destructive operations. One thing to know is preview only works for vendored skills, not upstream ones, so you'll get limited info for external dependencies. If you're maintaining a curated skill collection or building automated review pipelines, this gives you a repeatable checklist that keeps bad actors and broken skills out of production.