# agents-cli - Doramagic AI Context Pack > Positioning: a pre-install experience and judgment asset. It helps the host AI get off to a good start, but it does not mean the project has already been installed, run, or validated. ## Sufficiency Principle - **Sufficiency over compression**: The AI Context Pack should be sufficient for the host AI to understand the project's value, capability boundaries, entrypoints, risks, and evidence sources before starting work; it may be layered, but it does not aim for the shortest possible summary. - **Compression policy**: Compress only noise and duplication, never context that affects judgment or the quality of the work. ## How the Host AI Should Use This You are reading the AI Context Pack that Doramagic compiled for agents-cli. Treat it as pre-work context: help the user understand who it fits, what it can do, how to start, what must be verified after install, and where the risks are. Do not claim that you have already installed, run, or executed the target project. ## Claim Consumption Rules - **Fact source**: Repo Evidence + Claim/Evidence Graph; the Human Wiki only supplies salience, terminology, and narrative structure. - **Minimum status for a fact**: `supported` - `supported`: May be used as a project fact, but the answer must cite the claim_id and evidence path. - `weak`: Usable only as a low-confidence lead; the user must be asked to keep verifying. - `inferred`: Usable only for risk notes or open questions; must not be packaged as a project fact. - `unverified`: Must not be used as fact; state clearly that evidence is insufficient. - `contradicted`: Must show the conflicting sources and must not force a single version on the user's behalf. ## Who It Fits Best - **Developers already using host AIs such as Claude/Codex/Cursor/Gemini**: The README or plugin config mentions multiple host AIs. Evidence: `README.md` Claim: `clm_0004` supported 0.86 - **Users who want to bring professional workflows into a host AI**: The repo contains Skill documents. Evidence: `skills/google-agents-cli-adk-code/SKILL.md`, `skills/google-agents-cli-deploy/SKILL.md`, `skills/google-agents-cli-eval/SKILL.md`, `skills/google-agents-cli-observability/SKILL.md` et al. Claim: `clm_0005` supported 0.86 ## What It Can Do - **AI Skill / Agent Instruction Asset Library** (Previewable before install): The project contains Skill or Agent instruction files that a host AI can read, useful for bringing professional workflows into hosts like Claude, Codex, or Cursor. Evidence: `skills/google-agents-cli-adk-code/SKILL.md`, `skills/google-agents-cli-deploy/SKILL.md`, `skills/google-agents-cli-eval/SKILL.md`, `skills/google-agents-cli-observability/SKILL.md` et al. Claim: `clm_0001` supported 0.86 - **Multi-Host Install and Distribution** (Verify after install): The project contains plugin or marketplace configuration, indicating it targets install and distribution across one or more AI hosts. Evidence: `.claude-plugin/plugin.json` Claim: `clm_0002` supported 0.86 - **Command-Line Startup or Install Flow** (Verify after install): The project documentation contains runnable commands; real use requires running them in a local or host environment. Evidence: `README.md` Claim: `clm_0003` supported 0.86 ## How to Start - `npx skills add google/agents-cli` Evidence: `README.md` Claim: `clm_0006` supported 0.86 ## Continue-or-Stop Decision Card - **Current recommendation**: Sandbox trial only - **Why**: The project has signals of install commands, host configuration, or local writes; do not go straight into your primary environment—trial it in isolation first. ### 30-Second Read - **What to do now**: Sandbox trial only - **Minimum safe next step**: Run Prompt Preview first; if you still want to install, trial only in an isolated environment - **Do not trust yet**: Real output quality cannot be trusted before install. - **Continuing will touch**: Command execution, Host AI configuration, Local environment or project files ### What You Can Trust Now - **Target-audience signal: Developers already using host AIs such as Claude/Codex/Cursor/Gemini** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `README.md` Claim: `clm_0004` supported 0.86 - **Target-audience signal: Users who want to bring professional workflows into a host AI** (supported): Backed by a supported claim or project evidence, but that still is not the same as real install results. Evidence: `skills/google-agents-cli-adk-code/SKILL.md`, `skills/google-agents-cli-deploy/SKILL.md`, `skills/google-agents-cli-eval/SKILL.md`, `skills/google-agents-cli-observability/SKILL.md` et al. Claim: `clm_0005` supported 0.86 - **Capability exists: AI Skill / Agent Instruction Asset Library** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `skills/google-agents-cli-adk-code/SKILL.md`, `skills/google-agents-cli-deploy/SKILL.md`, `skills/google-agents-cli-eval/SKILL.md`, `skills/google-agents-cli-observability/SKILL.md` et al. Claim: `clm_0001` supported 0.86 - **Capability exists: Multi-Host Install and Distribution** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `.claude-plugin/plugin.json` Claim: `clm_0002` supported 0.86 - **Capability exists: Command-Line Startup or Install Flow** (supported): You can trust that the project contains signals of this capability; whether it fits your specific task still needs trial or after-install verification. Evidence: `README.md` Claim: `clm_0003` supported 0.86 - **There are Quick Start / install-command signals** (supported): You can trust that the docs mention a startup or install entrypoint; do not run it directly in your primary environment because of that. Evidence: `README.md` Claim: `clm_0006` supported 0.86 ### What You Cannot Trust Yet - **Real output quality cannot be trusted before install.** (unverified): Prompt Preview can only show how it guides you; it cannot prove result quality in the real project. - **Host AI version compatibility cannot be trusted before install.** (unverified): Host loading rules and version differences across Claude, Cursor, Codex, Gemini, and others must be verified in a real environment. - **That it will not pollute your existing host AI's behavior cannot be trusted directly.** (inferred): Skill, plugin, and AGENTS/CLAUDE/GEMINI instructions may change the host AI's default behavior. Evidence: `.claude-plugin/plugin.json`, `skills/google-agents-cli-adk-code/SKILL.md`, `skills/google-agents-cli-deploy/SKILL.md`, `skills/google-agents-cli-eval/SKILL.md` et al. - **Safe rollback cannot be assumed by default.** (unverified): Unless the project clearly provides uninstall and recovery instructions, verify in an isolated environment first. - **After a real install, is it compatible with the user's current host AI version?** (unverified): Compatibility can only be verified in the actual host environment. Evidence: `.claude-plugin/plugin.json` - **Does the project's output quality meet the user's specific task?** (unverified): The pre-install preview can only show flow and boundaries; it cannot replace real evaluation. - **Do the install commands require network access, permissions, or global writes?** (unverified): This affects install risk in both enterprise and personal environments. Evidence: `README.md` ### What Continuing Will Touch - **Command execution**: Package managers, network downloads, the local plugin directory, project config, or the user's home directory. Why: Running the very first command can already change your environment; decide whether it is worth running first. Evidence: `README.md` - **Host AI configuration**: The plugin, Skill, or rule-loading config of hosts like Claude/Codex/Cursor/Gemini/OpenCode. Why: Host configuration changes how the AI works afterward and may conflict with the user's existing rules. Evidence: `.claude-plugin/plugin.json`, `skills/google-agents-cli-adk-code/SKILL.md`, `skills/google-agents-cli-deploy/SKILL.md`, `skills/google-agents-cli-eval/SKILL.md` et al. - **Local environment or project files**: Install results, plugin caches, project config, or local dependency directories. Why: The write scope and rollback path cannot be proven before install and need isolated verification. Evidence: `.claude-plugin/plugin.json`, `README.md` - **Host AI context**: The AI Context Pack, Prompt Preview, Skill routing, risk rules, and project facts. Why: Importing context affects the host AI's later judgment, so avoid packaging unverified items as facts. ### Minimum Safe Next Steps - **Run Prompt Preview first**: Use a pre-install interactive trial to judge whether the way of working fits; it needs no authorization or environment change. (applies when: Applies to any project, especially when output quality is unknown.) - **Trial-install only in an isolated directory or a test account**: Avoid letting install commands pollute your primary host AI, real projects, or home directory. (applies when: When there are signals of command execution, plugin config, or local writes.) - **Back up your host AI configuration first**: Skill, plugin, and rule files may change the default behavior of Claude/Cursor/Codex. (applies when: When there is a plugin manifest, a Skill, or a host rule entrypoint.) - **After install, verify just one minimal task**: Verify loading, compatibility, output quality, and rollback first, then decide whether to use it deeply. (applies when: When moving from a trial into a real workflow.) ### Exit Plan - **Preserve the pre-install state**: Record the original host config and project state so you can later judge whether it is recoverable. - **Be ready to remove the host plugin / Skill / rule entrypoint**: If behavior is off after the trial install, you can restore the host AI to its pre-trial state. - **Record the install commands and written paths**: Without clear uninstall instructions, you at least need to know which directories or configs to clean up manually. - **If there is no rollback path, do not enter your primary environment**: No rollback is a blocker before continuing; do not proceed on trust or luck. ## What Can Only Be Previewed - Explain who the project fits and what it can do - Demonstrate a typical conversation flow based on project docs - Help the user decide whether it is worth installing or researching further ## What Must Be Verified After Install - Actually installing the Skill, plugin, or CLI - Running scripts, modifying local files, or accessing external services - Verifying real output quality, performance, and compatibility ## Boundary & Risk Decision Card - **Mistaking the pre-install preview for a real run**: The user may overestimate how much configuration, permission, and compatibility verification the project has already done. Mitigation: Clearly separate prompt_preview_can_do from runtime_required. Claim: `clm_0007` inferred 0.45 - **Host AI plugin or Skill rule conflicts**: New rules may change how the user's existing host AI behaves. Mitigation: Inspect the plugin manifest and Skill files before installing, and test in isolation if needed. Evidence: `.claude-plugin/plugin.json` Claim: `clm_0008` supported 0.86 - **Command execution will modify the local environment**: Install commands may write to the user's home directory, the host plugin directory, or project configuration. Mitigation: Run in an isolated environment or a test account first. Evidence: `README.md` Claim: `clm_0009` supported 0.86 - **To confirm**: After a real install, is it compatible with the user's current host AI version?. Why: Compatibility can only be verified in the actual host environment. - **To confirm**: Does the project's output quality meet the user's specific task?. Why: The pre-install preview can only show flow and boundaries; it cannot replace real evaluation. - **To confirm**: Do the install commands require network access, permissions, or global writes?. Why: This affects install risk in both enterprise and personal environments. ## Pre-Work Working Context ### Loading Order - First read how_to_use.host_ai_instruction to establish the boundaries of this pre-install judgment asset. - Read claim_graph_summary to confirm facts come from the Claim/Evidence Graph, not the Human Wiki narrative. - Then read intended_users, capabilities, and quick_start_candidates to judge whether the user is a match. - When you need to carry out a concrete task, check role_skill_index first, then evidence_index. - For real install, file modification, network access, performance, or compatibility questions, turn to risk_card and boundaries.runtime_required. ### Task Routes - **AI Skill / Agent Instruction Asset Library**: Use role_skill_index / evidence_index to help the user pick a usable role, Skill, or workflow first. Boundary: Can be experienced via a pre-install Prompt. Evidence: `skills/google-agents-cli-adk-code/SKILL.md`, `skills/google-agents-cli-deploy/SKILL.md`, `skills/google-agents-cli-eval/SKILL.md`, `skills/google-agents-cli-observability/SKILL.md` et al. Claim: `clm_0001` supported 0.86 - **Multi-Host Install and Distribution**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `.claude-plugin/plugin.json` Claim: `clm_0002` supported 0.86 - **Command-Line Startup or Install Flow**: State that this is an after-install capability first, then give a pre-install checklist. Boundary: Must be verified after a real install or run. Evidence: `README.md` Claim: `clm_0003` supported 0.86 ### Context Scale - Total files: 327 - Important-file coverage: 40/327 - Evidence index entries: 80 - Role / Skill entries: 7 ### Handling Insufficient Evidence - **missing_evidence**: State that evidence is insufficient and ask the user for the target file, a README section, or after-install verification records; do not fill in facts. - **out_of_scope_request**: State that the task is beyond the current AI Context Pack's evidence scope and suggest the user check the Human Manual or verify after a real install. - **runtime_request**: Provide a pre-install checklist and command sources, but do not run commands for the user or claim they have been run. - **source_conflict**: Show the conflicting sources side by side, mark them as unverified, and do not force a single version. ## Prompt Recipes ### Fit assessment - Goal: Judge whether this project fits the user's current task. - Expected output: A fit conclusion, key reasons, evidence citations, what can be previewed before install, what must be verified after install, and a next-step recommendation. ```text Based on the AI Context Pack for agents-cli, ask me 3 necessary questions first, then judge whether it fits my task. The answer must cover: who it fits, what it can do, what it cannot do, whether it is worth installing, and where the evidence comes from. Every project fact must cite evidence_refs, source_paths, or a claim_id. ``` ### Pre-install experience - Goal: Let the user feel the core workflow before installing, while avoiding packaging the preview as real capability or a marketing promise. - Expected output: An experience script with boundary labels, an after-install verification checklist, and a cautious recommendation; with no real-run promises or strong marketing language. ```text Treat agents-cli as a pre-install experience asset, not an already-installed tool or a real runtime environment. Output exactly four parts: 1. Ask me 3 necessary questions first. 2. Give an "experience script": use the three labels [Previewable before install], [Must verify after install], and [Insufficient evidence] to show how it might guide the workflow. 3. Give an after-install verification checklist: list which capabilities can only be confirmed after a real install, real host loading, and a real project run. 4. Give a cautious recommendation: only "worth researching/trialing further", "add information before deciding", or "not recommended to continue"; do not endorse the project. Hard boundaries: - Do not claim you have installed, run, executed tests, modified files, or produced real results. - Do not write promise-like phrasing such as "auto-adapts", "guarantees passing", "perfect fit", or "strongly recommend installing". - If you describe how it works after install, you must use a conditional such as "if installed successfully and the host loads the Skill correctly, it might...". - The experience script may only be written as "example lines / hypothetical flow": use "might ask / might suggest / might show", not "has written, has generated, has passed, is running, is generating". - Prompt Preview does not hand out install commands; if the user is ready to trial, only prompt them to read Quick Start and the Risk Card first and to verify in an isolated environment. - Every project fact must come from a supported claim, evidence_refs, or source_paths; inferred/unverified items can only be risks or open questions. ``` ### Role / Skill selection - Goal: Pick the best-matching asset from the project's roles or Skills. - Expected output: A list of candidate roles or Skills, each with an applicable scenario, evidence paths, risk boundary, and whether after-install verification is needed. ```text Read role_skill_index and recommend 3-5 of the most relevant roles or Skills for my target task. For each recommendation, state the applicable scenario, likely output, risk boundary, and evidence_refs. ``` ### Risk pre-check - Goal: Identify environment, permission, rule-conflict, and quality risks before installing or adopting. - Expected output: A checklist of environment, permission, dependency, license, host-conflict, quality risk, and unknown items. ```text Based on risk_card, boundaries, and quick_start_candidates, give me a pre-install risk pre-check list. Do not run commands for me; only explain what I should check, why, and what impact a failure would have. ``` ### Host AI kickoff instruction - Goal: Turn the project context into a host AI instruction for the start of a conversation. - Expected output: A pre-work instruction with clear boundaries and clear evidence citations, suitable to copy to a host AI. ```text Based on the AI Context Pack for agents-cli, generate a pre-work instruction I can paste to my host AI. This instruction must obey not_runtime=true and must not claim the project has been installed, run, or produced real results. ``` ## Role / Skill Index - Indexed 7 role / Skill / project-doc entries. - **google-agents-cli-adk-code** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “google-agents-cli-adk-code”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/google-agents-cli-adk-code/SKILL.md` - **google-agents-cli-deploy** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “google-agents-cli-deploy”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/google-agents-cli-deploy/SKILL.md` - **google-agents-cli-eval** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “google-agents-cli-eval”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/google-agents-cli-eval/SKILL.md` - **google-agents-cli-observability** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “google-agents-cli-observability”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/google-agents-cli-observability/SKILL.md` - **google-agents-cli-publish** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “google-agents-cli-publish”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/google-agents-cli-publish/SKILL.md` - **google-agents-cli-scaffold** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “google-agents-cli-scaffold”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/google-agents-cli-scaffold/SKILL.md` - **google-agents-cli-workflow** (skill): Activation hint: When the user's task is highly relevant to the workflow described by “google-agents-cli-workflow”, use it for a pre-install experience first, then decide whether to install. Evidence: `skills/google-agents-cli-workflow/SKILL.md` ## Evidence Index - Indexed 80 evidence entries. - **Get Started** (documentation): agents-cli The CLI and skills for building agents on Gemini Enterprise Agent Platform. Evidence: `README.md` - **ADK Skills** (documentation): Development skills for building agents with Google ADK https://adk.dev . Install into any coding agent via npx skills https://github.com/vercel-labs/skills . Evidence: `skills/README.md` - **Agent Templates** (documentation): This directory contains template implementations for various agents designed to work with the Agents CLI templating system. Feel free to browse through these folders to preview what each template offers. Direct cloning of this repository isn't necessary to utilize these templates. Evidence: `src/google/agents/cli/scaffold/agents/README.md` - **ADK: Minimal Agent Example** (documentation): A basic agent built using the Google Agent Development Kit ADK https://google.github.io/adk-docs/ . This example demonstrates core ADK concepts like agent creation and tool integration in a minimal setup. Evidence: `src/google/agents/cli/scaffold/agents/adk/README.md` - **{{cookiecutter.project name}}** (documentation): A Go agent built with Google's Agent Development Kit ADK . Evidence: `src/google/agents/cli/scaffold/base_templates/go/README.md` - **Load Testing for ADK Go Agent** (documentation): This directory provides load testing for your ADK Go Agent application. Evidence: `src/google/agents/cli/scaffold/base_templates/go/e2e/load_test/README.md` - **{{cookiecutter.project name}}** (documentation): A Java agent built with Google's Agent Development Kit ADK . Evidence: `src/google/agents/cli/scaffold/base_templates/java/README.md` - **{{cookiecutter.project name}}** (documentation): {{cookiecutter.agent description}} Agent generated with agents-cli version {{ cookiecutter.package version }} Evidence: `src/google/agents/cli/scaffold/base_templates/python/README.md` - **{{cookiecutter.project name}}** (documentation): A base ReAct agent built with Google's Agent Development Kit ADK Agent generated with Agents CLI version {{cookiecutter.package version}} Evidence: `src/google/agents/cli/scaffold/base_templates/typescript/README.md` - **ADK Code Reference** (skill_instruction): Before using this skill , activate /google-agents-cli-workflow first — it contains the required development phases and scaffolding steps. Evidence: `skills/google-agents-cli-adk-code/SKILL.md` - **ADK Deployment Guide** (skill_instruction): Requires: agents-cli uv tool install google-agents-cli — install uv https://docs.astral.sh/uv/getting-started/installation/index.md first if needed. Evidence: `skills/google-agents-cli-deploy/SKILL.md` - **Agent Evaluation Guide** (skill_instruction): Requires: agents-cli uv tool install google-agents-cli — install uv https://docs.astral.sh/uv/getting-started/installation/index.md first if needed. Evidence: `skills/google-agents-cli-eval/SKILL.md` - **ADK Observability Guide** (skill_instruction): Cloud Trace works out of the box — no infrastructure needed. Prompt-response logging and BigQuery Agent Analytics require Terraform-provisioned infrastructure service account, GCS bucket, BigQuery dataset . Run agents-cli infra single-project --project PROJECT ID to provision these resources. See references/cloud-trace-and-logging.md for details, env vars, and verification commands. If your project isn't scaffolded yet, see /google-agents-cli-scaffold first. Evidence: `skills/google-agents-cli-observability/SKILL.md` - **Gemini Enterprise Registration** (skill_instruction): Requires: A deployed agent. For Agent Runtime, deployment metadata.json created by agents-cli deploy enables auto-detection. For Cloud Run or GKE, provide the agent card URL and flags directly. Evidence: `skills/google-agents-cli-publish/SKILL.md` - **ADK Project Scaffolding Guide** (skill_instruction): Requires: agents-cli uv tool install google-agents-cli — install uv https://docs.astral.sh/uv/getting-started/installation/index.md first if needed. Evidence: `skills/google-agents-cli-scaffold/SKILL.md` - **Agent Development Workflow & Guidelines** (skill_instruction): Agent Development Workflow & Guidelines Evidence: `skills/google-agents-cli-workflow/SKILL.md` - **Evaluation Datasets** (documentation): This directory contains evaluation datasets for testing agent behavior. Evidence: `src/google/agents/cli/scaffold/agents/adk/tests/eval/datasets/README.md` - **Load Testing for ADK Java Agent** (documentation): This directory provides load testing for your ADK Java Agent application. Evidence: `src/google/agents/cli/scaffold/base_templates/java/src/test/java/{{cookiecutter.java_package_path}}/e2e/load_test/README.md` - **Load Testing** (documentation): This directory provides load testing for the ADK agent. Evidence: `src/google/agents/cli/scaffold/base_templates/typescript/tests/load_test/README.md` - **Robust Load Testing for Generative AI Applications** (documentation): Robust Load Testing for Generative AI Applications Evidence: `src/google/agents/cli/scaffold/deployment_targets/agent_runtime/python/tests/load_test/README.md` - **Robust Load Testing for Generative AI Applications** (documentation): Robust Load Testing for Generative AI Applications Evidence: `src/google/agents/cli/scaffold/deployment_targets/cloud_run/python/tests/load_test/README.md` - **Robust Load Testing for Generative AI Applications** (documentation): Robust Load Testing for Generative AI Applications Evidence: `src/google/agents/cli/scaffold/deployment_targets/gke/python/tests/load_test/README.md` - **Robust Load Testing for Generative AI Applications** (documentation): Robust Load Testing for Generative AI Applications Evidence: `src/google/agents/cli/scaffold/deployment_targets/none/python/tests/load_test/README.md` - **CLI Reference** (documentation): Complete reference for every command in Agents CLI in Agent Platform the agents-cli binary . Evidence: `docs/src/cli/index.md` - **Authentication** (documentation): agents-cli sits on top of multiple tools, each with its own authentication needs. This page breaks down the three distinct levels so you understand exactly what you're authenticating and why. Evidence: `docs/src/guide/authentication.md` - **Getting Started** (documentation): Agents CLI in Agent Platform is a CLI and skills package for building, evaluating, and deploying AI agents on Google Cloud. Agents are built with Google's Agent Development Kit ADK https://google.github.io/adk-docs/ — Agents CLI handles everything around it: scaffolding, evaluation, deployment, and observability. Evidence: `docs/src/guide/getting-started.md` - **Observability** (documentation): Every agents-cli project ships with OpenTelemetry instrumentation that automatically exports traces to Cloud Trace . This gives you: Evidence: `docs/src/guide/observability/index.md` - **Tutorial: Build Your First Agent** (documentation): For beginners who want to build, evaluate, and deploy an agent using a coding agent. Evidence: `docs/src/guide/quickstart-tutorial.md` - **agents-cli** (documentation): .md-typeset h1 { display: none; } .md-content inner { padding-top: 0; padding-bottom: 0; margin-bottom: 0; } .md-content { padding-bottom: 0; } Evidence: `docs/src/index.md` - **Reference** (documentation): See CLI Reference ../cli/index.md and Skills skills.md . Evidence: `docs/src/reference/index.md` - **Contributing to agents-cli** (documentation): We welcome contributions to agents-cli! If you'd like to report a bug, suggest a feature, or discuss a change, please open an issue https://github.com/google/agents-cli/issues on GitHub. Pull requests are not currently accepted. Evidence: `CONTRIBUTING.md` - **Package** (package_manifest): { "name": "{{cookiecutter.project name}}", "version": "1.0.0", "description": "AI Agent built with Google ADK TypeScript ", "type": "module", "main": "{{cookiecutter.agent directory}}/agent.ts", "scripts": { "build": "tsc", "dev": "tsc && npx @google/adk-devtools web -h localhost dist/agent.js", "run": "tsc && npx @google/adk-devtools run dist/agent.js", "test": "vitest run", "lint": "eslint .", "typecheck": "tsc --noEmit" }, "devDependencies": { "@eslint/js": "^9.39.2", "@types/node": "^25.0.3", "dotenv": "^17.2.3", "eslint": "^10.1.0", "tsx": "^4.21.0", "typescript": "^5.9.0", "typescript-eslint": "^8.57.2", "vitest": "^4.1.0" }, "dependencies": { "@google/adk": "^0.3.0", "@google/adk-dev… Evidence: `src/google/agents/cli/scaffold/base_templates/typescript/package.json` - **Plugin** (structured_config): { "name": "google-agents-cli", "version": "1.0.0", "description": "Scaffold, develop, evaluate, and deploy AI agents with Google ADK. Bundles 7 skills for the agent development lifecycle.", "author": { "name": "Google LLC" }, "homepage": "https://github.com/google/agents-cli", "repository": "https://github.com/google/agents-cli", "license": "Apache-2.0" } Evidence: `.claude-plugin/plugin.json` - **License** (source_file): Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ Evidence: `LICENSE` - **CI/CD & Production** (documentation): Set up a CI/CD pipeline that tests on pull request, deploys to staging on merge, and promotes to production with manual approval. Evidence: `docs/src/guide/cicd.md` - **Deployment** (documentation): Deploy your agent to a development environment or production with a CI/CD pipeline. Evidence: `docs/src/guide/deployment.md` - **Development Guide** (documentation): This guide covers the full development workflow — from defining what you're building to monitoring it in production. It follows the same phases your coding agent uses via the google-agents-cli-workflow skill. Evidence: `docs/src/guide/development.md` - **Evaluation Guide** (documentation): Run structured evaluations to confirm your agent calls the right tools, produces quality responses, and handles edge cases. Under the hood, evaluation uses the Gemini Enterprise Agent Platform GenAI Eval SDK https://docs.cloud.google.com/gemini-enterprise-agent-platform/optimize/evaluation/agent-evaluation to grade evaluations. Evidence: `docs/src/guide/evaluation.md` - **Tutorial: Manual Workflow** (documentation): For developers who prefer to type every command themselves, without a coding agent. Evidence: `docs/src/guide/hands-on-tutorial.md` - **The Lifecycle** (documentation): Agents CLI is opinionated about one thing: the loop between "looks good in a notebook" and "live in production." This page is the map. Evidence: `docs/src/guide/lifecycle.md` - **BigQuery Agent Analytics Plugin** (documentation): For teams who want SQL-based analytics on agent behavior, token usage, and conversation patterns. Evidence: `docs/src/guide/observability/bq-agent-analytics.md` - **Cloud Trace** (documentation): For developers who have deployed an agent and want to verify tracing works and inspect telemetry data. Evidence: `docs/src/guide/observability/cloud-trace.md` - **Project Structure** (documentation): For developers who want to understand the layout of a generated agent project. Evidence: `docs/src/guide/project-structure.md` - **Agent Templates** (documentation): agents-cli creates projects from agent templates. Each template provides a working agent with the right dependencies, tools, and project structure for its use case. Evidence: `docs/src/guide/templates.md` - **Use Cases** (documentation): Agents CLI scaffolds, evaluates, and deploys agents from the descriptions you provide to your coding agent. Use it to build: Evidence: `docs/src/guide/use-cases.md` - **About This Project** (documentation): We value your input — it helps us improve agents-cli for the community. Evidence: `docs/src/reference/about.md` - **Migrating Eval Datasets** (documentation): If you started using agents-cli before the eval surface was rebuilt around the Gemini Enterprise Agent Platform GenAI Eval SDK https://docs.cloud.google.com/gemini-enterprise-agent-platform/optimize/evaluation/agent-evaluation , you may have evaluation files under tests/eval/evalsets/ using the older ADK EvalSet schema. Those files are no longer read by agents-cli eval generate or related commands. This page walks through converting them to the new format. Evidence: `docs/src/reference/eval-dataset-migration.md` - **From Agent Starter Pack** (documentation): agents-cli is the successor to Agent Starter Pack ASP . It builds on the same foundation with key improvements. Evidence: `docs/src/reference/from-agent-starter-pack.md` - **Skills Reference** (documentation): Skills are context files installed to coding agents Antigravity CLI, Claude Code, GitHub Copilot via agents-cli setup . They provide domain-specific guidance for working with generated agent projects. Evidence: `docs/src/reference/skills.md` - **Development Commands** (documentation): Phase Commands --- --- Setup setup install skills · update refresh skills Scaffold scaffold create · scaffold enhance . · scaffold upgrade Develop playground web UI · run "prompt" one-shot; -v = JSON events · lint · install Evaluate eval dataset synthesize · eval generate · eval grade · eval compare · eval analyze · eval optimize · eval metric list · eval submit / eval results cloud Deploy deploy needs approval · infra single-project · infra cicd · publish gemini-enterprise Info / Auth info · login --interactive · login --status Evidence: `skills/google-agents-cli-workflow/references/commands.md` - **Agent Spec Template** (documentation): Overview Describe the agent's purpose and how it works. Evidence: `skills/google-agents-cli-workflow/references/spec-template.md` - **Product Name Mapping** (documentation): The platform formerly known as "Vertex AI" is now Gemini Enterprise Agent Platform short: Agent Platform . Users may refer to products by different names. Map them to the correct CLI values: Evidence: `skills/google-agents-cli-workflow/references/terminology.md` - **Genai Logs Schema** (structured_config): { "name": "logName", "type": "STRING", "mode": "NULLABLE" }, { "name": "textPayload", "type": "STRING", "mode": "NULLABLE" }, { "name": "timestamp", "type": "TIMESTAMP", "mode": "NULLABLE" }, { "name": "receiveTimestamp", "type": "TIMESTAMP", "mode": "NULLABLE" }, { "name": "severity", "type": "STRING", "mode": "NULLABLE" }, { "name": "insertId", "type": "STRING", "mode": "NULLABLE" }, { "name": "trace", "type": "STRING", "mode": "NULLABLE" }, { "name": "spanId", "type": "STRING", "mode": "NULLABLE" }, { "name": "traceSampled", "type": "BOOLEAN", "mode": "NULLABLE" }, { "name": "resource", "type": "RECORD", "mode": "NULLABLE", "fields": { "name": "type", "type": "STRING", "mode": "NULLABLE"… Evidence: `src/google/agents/cli/scaffold/base_templates/python/deployment/terraform/shared/genai_logs_schema.json` - **Copyright 2026 Google LLC** (source_file): Copyright 2026 Google LLC Licensed under the Apache License, Version 2.0 the "License" ; you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Evidence: `docs/pyproject.toml` - **Cmd Generate** (source_file): INFERENCE TIMEOUT = 600 ⋮---- INFERENCE RUNNER = " inference runner.py" INFERENCE STAGE DIR = ".agents-cli-scripts" ⋮---- def stage inference runner dest dir: Path - Path ⋮---- runner resource = resources.files "google.agents.cli.eval" .joinpath dest path = dest dir / INFERENCE RUNNER ⋮---- Example: Evidence: `src/google/agents/cli/eval/cmd_generate.py` - **Main** (source_file): def print is project moved tip - None ⋮---- message = ⋮---- class MainGroup LazyGroup ⋮---- def invoke self, ctx: click.Context - None ⋮---- @click.group cls= MainGroup @click.version option version= version , prog name="agents-cli" def main Evidence: `src/google/agents/cli/main.py` - **Agents Cli Manifest** (source_file): name: "{{cookiecutter.project name}}" acli version: "{{cookiecutter.package version}}" agent directory: "{{cookiecutter.agent directory}}" region: "us-east1" base template: "{{cookiecutter.agent name}}" generated at: "{{cookiecutter.generated at}}" language: "{{cookiecutter.language or 'python'}}" create params: deployment target: "{{cookiecutter.deployment target}}" session type: "{{cookiecutter.session type or 'none'}}" cicd runner: "{{cookiecutter.cicd runner}}" {% if cookiecutter.is a2a -%} is a2a: true {%- endif %} agent guidance filename: "{{cookiecutter.agent guidance filename}}" Evidence: `src/google/agents/cli/scaffold/base_templates/_shared/agents-cli-manifest.yaml` - **Copyright 2026 Google LLC** (source_file): Copyright 2026 Google LLC Licensed under the Apache License, Version 2.0 the "License" ; you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Evidence: `src/google/agents/cli/scaffold/base_templates/python/Dockerfile` - **Copyright 2026 Google LLC** (source_file): Copyright 2026 Google LLC Licensed under the Apache License, Version 2.0 the "License" ; you may not use this file except in compliance with the License. You may obtain a copy of the License at https://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. Evidence: `src/google/agents/cli/scaffold/base_templates/python/deployment/terraform/cicd/telemetry.tf` - **Completions** (source_file): WITH log refs AS SELECT insertId AS insert id, timestamp, trace, spanId AS span id, labels.gen ai conversation id AS conversation id, labels.gen ai input messages ref AS input ref, labels.gen ai output messages ref AS output ref, labels.gen ai usage input tokens AS usage input tokens, labels.gen ai usage output tokens AS usage output tokens, labels.gen ai agent name AS agent name, labels.gen ai response finish reasons AS finish reasons, labels.user id FROM ${project id}.${dataset id}.gen ai client inference operation details WHERE labels.gen ai input messages ref IS NOT NULL OR labels.gen ai output messages ref IS NOT NULL , unpivoted refs AS SELECT insert id, timestamp, trace, span id, con… Evidence: `src/google/agents/cli/scaffold/base_templates/python/deployment/terraform/shared/completions.sql` - The remaining 20 evidence entries are in `AI_CONTEXT_PACK.json` or `EVIDENCE_INDEX.json`. ## Rules the Host AI Must Follow - **Treat this asset as pre-work context, not a runtime environment.**: The AI Context Pack contains only an evidence-backed understanding of the project, not the project's executable state. Evidence: `README.md`, `skills/README.md`, `src/google/agents/cli/scaffold/agents/README.md` - **When answering the user, distinguish what can be previewed from what can only be verified after install.**: The consumer value of the pre-install experience comes from reducing bad installs and misjudgments, not from pretending to be a real run. Evidence: `README.md`, `skills/README.md`, `src/google/agents/cli/scaffold/agents/README.md` ## Questions the User Should Answer First - Which host AI or local environment do you plan to use it in? - Do you just want to experience the workflow first, or are you ready to actually install? - What matters most to you: install cost, output quality, or conflicts with your existing rules? ## Acceptance Checks - Every capability claim can be traced back to a file path in evidence_refs. - AI_CONTEXT_PACK.md does not package previews as a real run. - The user can understand who it fits, what it can do, how to start, and the risk boundaries within 3 minutes. --- ## Doramagic Context Augmentation The following sections strengthen the repository context for a host AI. Human Manual data is a reading route, and pitfall notes become operating constraints. ## Human Manual Outline Usage rule: this is only a reading route and salience signal, not factual authority. Concrete claims must still return to repo evidence or Claim Graph. Host AI hard rules: - Do not treat page titles, section order, summaries, or importance values as factual project evidence. - When explaining the Human Manual outline, state that it is only a reading route or salience signal. - Capability, installation, compatibility, runtime state, and risk claims must cite repo evidence, source paths, or Claim Graph. - **Introduction and Installation**: importance `high` - source_paths: README.md, docs/src/index.md, docs/src/guide/getting-started.md, docs/src/guide/quickstart-tutorial.md, docs/src/guide/authentication.md - **CLI Commands and Agent Lifecycle**: importance `high` - source_paths: src/google/agents/cli/main.py, src/google/agents/cli/setup/cmd_setup.py, src/google/agents/cli/scaffold/commands/create.py, src/google/agents/cli/scaffold/commands/enhance.py, src/google/agents/cli/scaffold/commands/upgrade.py - **Agent Skills Reference**: importance `high` - source_paths: skills/README.md, skills/google-agents-cli-workflow/SKILL.md, skills/google-agents-cli-workflow/references/commands.md, skills/google-agents-cli-workflow/references/terminology.md, skills/google-agents-cli-workflow/references/spec-template.md - **Templates, Deployment Targets, and Known Issues**: importance `high` - source_paths: src/google/agents/cli/scaffold/base_templates/_shared/agents-cli-manifest.yaml, src/google/agents/cli/scaffold/base_templates/python/pyproject.toml, src/google/agents/cli/scaffold/base_templates/python/Dockerfile, src/google/agents/cli/scaffold/base_templates/python/deployment/terraform/cicd/telemetry.tf, src/google/agents/cli/scaffold/base_templates/python/deployment/terraform/shared/genai_logs_schema.json ## Repo Inspection Evidence - repo_clone_verified: true - repo_inspection_verified: true - repo_commit: `c40ed19e6d442040286bf7ea3105fab501c99080` - inspected_files: `README.md`, `docs/hooks/skills_reference.py`, `docs/mkdocs.yml`, `docs/pyproject.toml`, `docs/src/cli/index.md`, `docs/src/guide/authentication.md`, `docs/src/guide/cicd.md`, `docs/src/guide/deployment.md`, `docs/src/guide/development.md`, `docs/src/guide/evaluation.md`, `docs/src/guide/getting-started.md`, `docs/src/guide/hands-on-tutorial.md`, `docs/src/guide/lifecycle.md`, `docs/src/guide/observability/bq-agent-analytics.md`, `docs/src/guide/observability/cloud-trace.md`, `docs/src/guide/observability/index.md`, `docs/src/guide/project-structure.md`, `docs/src/guide/quickstart-tutorial.md`, `docs/src/guide/templates.md`, `docs/src/guide/use-cases.md` Host AI hard rules: - Without repo_clone_verified=true, do not claim that the source code has been read. - Without repo_inspection_verified=true, do not write README, docs, or package-file conclusions as facts. - Without quick_start_verified=true, do not claim that the Quick Start path has run successfully. ## Doramagic Pitfall Constraints These rules come from Doramagic discovery, validation, or compilation findings. The host AI must treat them as operating constraints, not background notes. ### Constraint 1: Security or permission risk requires verification - Trigger: Developers should check this security_permissions risk before relying on the project: Add an optional AISP deployment readiness contract for eval, approval, deploy, rollback, and observability gates - Host AI rule: Before packaging this project, run the relevant install/config/quickstart check for: Add an optional AISP deployment readiness contract for eval, approval, deploy, rollback, and observability gates. Context: Observed when using python - Why it matters: Developers may expose sensitive permissions or credentials: Add an optional AISP deployment readiness contract for eval, approval, deploy, rollback, and observability gates - Evidence: failure_mode_cluster:github_issue | https://github.com/google/agents-cli/issues/48 - Hard boundary: Do not present this pitfall as solved, verified, or ignorable unless later evidence explicitly closes it.