Sanitize an LLM response through Google Model Armor
Run model output through a Model Armor template with the gws CLI for outbound safety checks
- What
- Run model output through a Model Armor template with the gws CLI for outbound safety checks
- Cost
- Free
- Needs
- the gws CLI installed; a Google Cloud project with Model Armor enabled and an existing template; Model Armor screening is a paid GCP service (per-request billing)
- Install
- Copy the installer prompt below into your Muse β your agent does the rest.
π³ **Paid API required** β this skill drives Google Cloud's Model Armor through the gws CLI; Model Armor screening is billed per request, with no usable free tier stated. Curated by Skill Harbor β @googleworkspace's outbound-safety wrapper: sanitize a model response through a Model Armor template with `gws modelarmor +sanitize-response --template projects/PROJECT/locations/LOCATION/templates/TEMPLATE --text 'model output'` (or pipe model output into it, or pass a full JSON body), with companion coverage for inbound safety via `+sanitize-prompt`. By @googleworkspace, listed here with credit to its creator. Honest caveats: requires the gws CLI, a Google Cloud project with Model Armor enabled and an existing template; read the sibling gws-shared skill for auth and security rules before use; Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: the gws CLI installed; a Google Cloud project with Model Armor enabled and an existing template; Model Armor screening is a paid GCP service (per-request billing) Install "Sanitize an LLM response through Google Model Armor" for me. It wraps `gws modelarmor +sanitize-response` to screen model output through a Model Armor template for outbound safety, with `+sanitize-prompt` as its inbound counterpart. Repository: https://github.com/googleworkspace/cli/blob/main/skills/gws-modelarmor-sanitize-response/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "gws-modelarmor-sanitize-response". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. authenticate the gws CLI; create a Model Armor template in the Google Cloud console if none exists yet β remember screening is billed per request). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you β no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the sellerβs own page, usually Stripe.
What does the β next to a creatorβs name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself β always check a build before installing it.