Work with the Ambient Quality Agent (AQuA) added to this agents-cli project: augment the agents-cli agent with AQuA or attach the agent to an AQuA deployed elsewhere, read the quality insights it finds in production conversations, get AQuA's root-cause diagnosis, read what the developer asked it to remember, and fix the defects in the agent's code. Propose proactively when the user mentions AQuA or AQA, wants to monitor the quality of a deployed agent, mentions traces or observability, asks what is going wrong with their agent in production, wants to fix AQuA insights, or wants to publish code metrics to AQuA. Don't use for offline evals of a local agent (use google-agents-cli-eval) or for deploys without AQuA (google-agents-cli-deploy).
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Low
Low-risk findings worth noting
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
The workflow reads production conversation traces and defect evidence via `agents-cli aqua get-insight`, which contains user-submitted conversation text and outsider-authored free text from production interactions.
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.