CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agents-cli-aqua

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. Also propose it when traces from an evaluation run are in the telemetry table AQuA reads. Don't use it for scoring a local agent against a golden dataset (use google-agents-cli-eval) or for deploys without AQuA (google-agents-cli-deploy).

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong operational skill: fully executable commands, well-sequenced workflows with explicit validation and confirmation gates for destructive actions, and dense prose that assumes Claude's competence. Its one structural weakness is the absence of any progressive disclosure — everything, including peripheral material like dashboard access details and the task cheat-sheet table, is inlined in a single large file.

Suggestions

Move the Dashboard section's IAP/grant details and the 'Other tasks' cheat-sheet table into a references/ file (e.g. references/dashboard.md, references/tasks.md), keeping a one-line pointer with the essential flag in SKILL.md.

Trim the attach section by showing the --dry-run form once and stating that the same command repeats with --yes, instead of printing every variant twice.

Consider moving the augment-path failure→fix table to a short troubleshooting reference, leaving only the two most common failures inline.

DimensionReasoningScore

Conciseness

The body is information-dense (flags, exit codes, IAM effects, jq projections) and explains nothing Claude already knows, but it could be tightened: the attach section repeats each command variant twice for --dry-run and --yes, and step 3 of the augment path cross-references the other deploy section instead of restating briefly. This matches the level-4 anchor (efficient with minor instances that could be trimmed) rather than the lean level-5 anchor.

4 / 5

Actionability

Every workflow ships copy-paste-ready commands with concrete flags: 'agents-cli aqua attach --dry-run --observed-agent-resource projects/<project>/…', the BigQuery traffic-verification query, jq projections for insight fields, and a failure→fix table. Fully executable and covering the common cases, which is the level-5 anchor.

5 / 5

Workflow Clarity

Both deploy paths and the 8-step fix workflow are clearly sequenced with explicit validation checkpoints and feedback loops: dry-run plan → user go-ahead → --yes; 'expect exit 0 with counters.trajectories_scanned above zero'; 'Confirm after the next investigation' with guidance on judging fixes by conversation timestamps. Destructive operations (detach, destroy, IAM grants) are gated on user confirmation, satisfying the level-5 anchor.

5 / 5

Progressive Disclosure

No bundle files exist and all ~430 lines live in SKILL.md. Section headers and internal anchor links give it real structure, but content that would naturally sit in one-level-deep references — dashboard IAP details, the 'Other tasks' table, the deploy troubleshooting rows — is fully inlined with no references to signal. This matches the level-3 anchor ('content that should be separate is inline'), not level 4, which presumes content is appropriately split with clear references.

3 / 5

Total

17

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: concrete capability enumeration, explicit and natural trigger conditions with the AQA synonym variant, and explicit negative boundaries that route away sibling skills. Every dimension sits at the top anchor without padding or over-claiming.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — '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' — comprehensively covering the skill's capabilities. Level 4 ('minor gaps in coverage') does not apply since every core workflow is named.

5 / 5

Completeness

It explicitly answers both 'what' (the enumerated capability list) and 'when' ('Propose proactively when the user mentions AQuA or AQA…') with concrete trigger phrases, and adds negative boundaries ('Don't use it for scoring a local agent against a golden dataset'). This is the level-5 anchor exactly.

5 / 5

Trigger Term Quality

Natural user phrasings are covered comprehensively: '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', including the AQA spelling variant. This matches the level-5 anchor (synonyms and variations included) rather than level 4's 'a few natural terms missing'.

5 / 5

Distinctiveness Conflict Risk

The niche is unambiguous (AQuA quality monitoring for deployed agents-cli agents) and it explicitly disambiguates sibling skills: 'scoring a local agent against a golden dataset (use google-agents-cli-eval) or for deploys without AQuA (google-agents-cli-deploy)'. Clear distinct triggers with minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 2 missing, 2 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

google/adk-samples

Path

core/python/ambient-quality-agent/skills/agents-cli-aqua/SKILL.md

Reviewed

Table of Contents

Is this your skill?

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.