Upload files to catbox.moe (permanent) or litterbox.catbox.moe (temporary).

**Quick judgment** A focused and practical upload skill for Catbox/Litterbox that does exactly what it promises: uploads a file and returns a URL. It’s well-suited for workflows that need simple, ad-hoc file sharing, especially temporary links via Litterbox. Functionality and usability are strong given the clear options (service selection, expiry time, optional userhash), but robustness and safety controls are minimal and entirely delegated to the underlying hosting services. **Key risks / limitations** - **Content & compliance risk:** Catbox/Litterbox are third‑party hosts with their own terms of service. This skill has no built‑in filtering or policy checks, so it can be misused to store or distribute disallowed or sensitive content if the calling agent/user is not constrained by higher‑level safeguards. - **Privacy & data handling:** Files are uploaded to an external service; there is no encryption or access control layer beyond the obscurity of the URL. Anything uploaded should be treated as potentially public. - **Persistence characteristics:** Catbox uploads are effectively permanent; Litterbox uploads expire but only after a selectable window (1h–72h). Mistakenly choosing Catbox or a long duration can lead to unintended long‑term exposure of data. - **Operational dependency:** Reliability is tied to the availability and behavior of catbox.moe/litterbox.catbox.moe (rate limits, outages, or policy changes). The skill description does not mention retries, error classification, or fallback behavior. - **Size limits:** Litterbox supports up to 1 GB and Catbox up to 200 MB; larger artifacts will fail and require separate handling. **Recommended scenarios** - Agent or user workflows that need **quick, temporary sharing** of non‑sensitive files (logs, traces, debug bundles, media) where Litterbox’s 1h–72h window is appropriate. - Lightweight tooling where a **simple public URL** is enough and no authentication or fine‑grained access control is required. - Situations where the team already understands and accepts **Catbox/Litterbox as infrastructure**, including their terms, uptime characteristics, and public visibility model. This skill should be combined with higher‑level policy and validation layers (e.g., content checks, sensitivity classification, and user confirmation for permanent uploads) in any safety‑critical or privacy‑sensitive deployment.