weegloo-resource-deletion

Guides dependency-ordered deletion of Weegloo resources and resolves 422 delete errors.

1|2|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/weeglooapi/weegloo-mcp-plugin --skill weegloo-resource-deletion-weeglooapi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weegloo-resource-deletion
Source: https://github.com/weeglooapi/weegloo-mcp-plugin/tree/main/plugins/weegloo/skills/weegloo-resource-deletion
Command: npx skills add https://github.com/weeglooapi/weegloo-mcp-plugin --skill weegloo-resource-deletion-weeglooapi

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about weegloo-resource-deletion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I delete a Weegloo Space without errors?

Delete a Weegloo Space by first removing the four blocking resource types: WebHosting, Content, ContentType, and Media. Unpublish any Published or Changed resources first, then delete the Space. All other children like roles, tokens, and scripts cascade automatically.

Why does deleting a Weegloo resource return a 422 error?

A 422 error means something still depends on the target resource or a precondition is unmet. Common causes are a Published status requiring unpublish first (WGL422009), existing dependent Content blocking a ContentType (WGL422010), or files still processing (WGL422031).

How do I delete a ContentType that still has Content?

Delete every Content entry of that ContentType first, unpublishing any Published or Changed entries. Then unpublish the ContentType itself with the current version header, and finally delete it. Both the delete and unpublish are blocked while any Content exists.

Can a Personal Access Token delete a Weegloo Organization?

No, a Personal Access Token cannot delete an Organization. Organization deletion requires the OWNER role with CONSOLE_SCOPE, which only a console login session carries. Space deletion works with a Personal Access Token but requires Organization ADMIN and GLOBAL_SCOPE.

What happens to references when I delete a Content or Media item?

Deleting a Content or Media item succeeds even when other Content references it through Refer fields, leaving dangling stubs that expand to nothing. Query inbound references with a filtered contents list before deleting anything that appears linked.