gws-modelarmor-sanitize-response
Google Model Armor: Sanitize a model response through a Model Armor template.
Best use case
gws-modelarmor-sanitize-response is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Google Model Armor: Sanitize a model response through a Model Armor template.
Teams using gws-modelarmor-sanitize-response should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/gws-modelarmor-sanitize-response/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How gws-modelarmor-sanitize-response Compares
| Feature / Agent | gws-modelarmor-sanitize-response | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Google Model Armor: Sanitize a model response through a Model Armor template.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# modelarmor +sanitize-response > **PREREQUISITE:** Read `../gws-shared/SKILL.md` for auth, global flags, and security rules. If missing, run `gws generate-skills` to create it. Sanitize a model response through a Model Armor template ## Usage ```bash gws modelarmor +sanitize-response --template <NAME> ``` ## Flags | Flag | Required | Default | Description | |------|----------|---------|-------------| | `--template` | ✓ | — | Full template resource name (projects/PROJECT/locations/LOCATION/templates/TEMPLATE) | | `--text` | — | — | Text content to sanitize | | `--json` | — | — | Full JSON request body (overrides --text) | ## Examples ```bash gws modelarmor +sanitize-response --template projects/P/locations/L/templates/T --text 'model output' model_cmd | gws modelarmor +sanitize-response --template ... ``` ## Tips - Use for outbound safety (model -> user). - For inbound safety (user -> model), use +sanitize-prompt. ## See Also - [gws-shared](../gws-shared/SKILL.md) — Global flags and auth - [gws-modelarmor](../gws-modelarmor/SKILL.md) — All filter user-generated content for safety commands
Related Skills
recipe-collect-form-responses
Retrieve and review responses from a Google Form.
gws-modelarmor
Google Model Armor: Filter user-generated content for safety.
gws-modelarmor-sanitize-prompt
Google Model Armor: Sanitize a user prompt through a Model Armor template.
gws-modelarmor-create-template
Google Model Armor: Create a new Model Armor template.
use-zod
Answer questions about the Zod schema validation library and help build schemas, parsers, refinements, transforms, codecs, and error formatters. Use when developers: (1) ask about Zod APIs like `z.object`, `z.string`, `z.array`, `z.union`, `z.discriminatedUnion`, `parse`, `safeParse`, `z.infer`; (2) define request/response/form schemas in TypeScript; (3) handle `ZodError` or customize error messages; (4) migrate between Zod v3 and v4 (entry-point split, `formatError` → `treeifyError`/`prettifyError`, unified `error` param replacing `message`/`errorMap`). Triggers on: "zod", "z.object", "z.string", "z.array", "z.union", "z.infer", "z.input", "z.output", "ZodError", "$ZodError", "safeParse", "parseAsync", "z.codec", "treeifyError", "prettifyError", "flattenError", "discriminatedUnion", "zod/v4", "zod/v3", "zod/mini", "z.coerce", "superRefine".
workflow
Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow sdk", "queue", "event", "push", "subscribe", or step-based orchestration.
wpds
Use when building UIs leveraging the WordPress Design System (WPDS) and its components, tokens, patterns, etc.
wp-wpcli-and-ops
Use when working with WP-CLI (wp) for WordPress operations: safe search-replace, db export/import, plugin/theme/user/content management, cron, cache flushing, multisite, and scripting/automation with wp-cli.yml.
wp-rest-api
Use when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes, schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing CPTs/taxonomies via show_in_rest.
wp-project-triage
Use when you need a deterministic inspection of a WordPress repository (plugin/theme/block theme/WP core/Gutenberg/full site) including tooling/tests/version hints, and a structured JSON report to guide workflows and guardrails.
wp-plugin-development
Use when developing WordPress plugins: architecture and hooks, activation/deactivation/uninstall, admin UI and Settings API, data storage, cron/tasks, security (nonces/capabilities/sanitization/escaping), and release packaging.
wp-playground
Use for WordPress Playground workflows: fast disposable WP instances in the browser or locally via @wp-playground/cli (server, run-blueprint, build-snapshot), auto-mounting plugins/themes, switching WP/PHP versions, blueprints, and debugging (Xdebug).