What problem does it solve? Deleting resources in Weegloo fails with 422 errors whenever anything still depends on the target, and the platform never force-deletes or cascades upward. This Skill maps the exact dependency order, preconditions, and error codes so teardowns succeed on the first attempt. ## Core Features & Use Cases - Space Teardown Order: Explains that only ContentType, Content, Media, and WebHosting block a Space delete, while every other child resource cascades automatically. - Precondition Handling: Covers the Draft-or-Archived status requirement (unpublish first), busy file/deploy states, and per-resource rules for Locale, SpaceRole, ServiceUserRole, Script, Tag, and Organization. - Error Resolution: Decodes WGL422 error codes into concrete fixes, including the WGL422010 double-bind where a published ContentType cannot be unpublished while Content exists. - Use Case: When cleaning up a demo Space, follow the documented order — delete WebHosting, unpublish and delete all Content, then the ContentType, then Media, then the Space — instead of fighting repeated 422 rejections. ## Quick Start Ask the agent to delete a Weegloo Space and everything in it, and it will unpublish and remove resources in the correct dependency order.