response▌

Sanitize model responses through Google Model Armor templates for outbound safety. \n \n Applies Model Armor templates to filter model outputs before delivery to users \n Accepts text input via --text flag or piped stdin, with optional full JSON request body override \n Requires template resource name in format projects/PROJECT/locations/LOCATION/templates/TEMPLATE \n Complements the +sanitize-prompt command for inbound user input safety \n

[Extended thinking: This workflow implements a sophisticated debugging and resolution pipeline that leverages AI-assisted debugging tools and observability platforms to systematically diagnose and resolve production issues. The intelligent debugging strategy combines automated root cause analysis with human expertise, using modern 2024/2025 practices including AI code assistants (GitHub Copilot, Claude Code), observability platforms (Sentry, DataDog, OpenTelemetry), git bisect automation for reg

Orchestrate multi-agent incident response with modern SRE practices for rapid resolution and learning:

Direct Response Copy is copy designed to get a specific action (click, signup, purchase). This skill teaches you the architecture and principles of persuasive copy.

Fast API responses improve overall application performance and user experience. Optimization focuses on payload size, caching, and query efficiency.

Structured approach to detecting, responding to, containing, and recovering from security incidents with comprehensive playbooks and automation.

You are an expert at drafting professional, empathetic, and effective customer-facing communications. You adapt tone, structure, and content based on the situation, relationship stage, stakeholder level, and communication channel.

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

Store and manage API response test fixtures for provider parsing validation. \n \n Fixtures are organized in __fixtures__ subfolders within provider packages, using naming conventions documented in existing examples \n Supports two testing patterns: generateText (log raw response to console and copy into fixture) and streamText (use includeRawChunks and saveRawChunks helper to capture streaming chunks) \n Recommends storing true provider responses unless size constraints require semantic-preserv