mittwald

# mittwald Use this skill for mittwald mStudio / Kundencenter production-platform work: project inventory, app/runtime inspection, deployment readiness, databases, domains/DNS/SSL/ingress, mail resources, backups, files, containers, SSH/SFTP users, and marketplace/license readouts. ## Default Workflow 1. Read first. Use `mittwald.cjs` to generate allowlisted `http_request` payloads and pass only the emitted `httpRequest` value to the built-in `http_request` tool. 2. Treat `MITTWALD_API_TOKEN` as a SecretRef only. The helper sets `bearerSecretName: "MITTWALD_API_TOKEN"` so the gateway injects `Authorization: Bearer ...` server-side. Never ask the user to paste the token, inspect it, or write raw `Authorization` headers. 3. For prompt/user testing, stop after `plan` or helper `http-request` payload generation. Do not call `http_request` unless live mittwald data is needed for the user's request. 4. For live calls, stop after the first 401 or 403. Report a credential or API role setup problem and ask the operator to verify: `hybridclaw secret set MITTWALD_API_TOKEN "<mittwald-api-token>"`. 5. For 429 responses, report rate-limit guidance from `Retry-After`, `X-RateLimit-Reset`, `X-RateLimit-Remaining`, and `X-RateLimit-Limit` when present. Do not start retry loops. 6. For guarded writes, require exact F8/F14 operator approval for the named target and pass `--operator-grant` only after that approval. The helper includes the target resourc...