google agents cli scaffold

AI Community

Skill notes

Prerequisite: Clarify Requirements (MANDATORY for new projects)

Before scaffolding a new project, load /google-agents-cli-workflow and complete Phase 0 — clarify the user's requirements before running any scaffold create command. Ask what the agent should do, what tools/APIs it needs, and whether they want a prototype or full deployment.

Step 1: Choose Architecture

Mapping user choices to CLI flags: Choice · CLI flag RAG with vector search · --agent agentic_rag --datastore agent_platform_vector_search RAG with document search · --agent agentic_rag --datastore agent_platform_search A2A protocol · --agent adk_a2a

Product name mapping

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: User may say · CLI value Agent Engine, Vertex AI Agent Engine, Agent Runtime · --deployment-target agent_runtime Vertex AI Search, Agent Search · --datastore agent_platform_search Vertex AI Vector Search, Vector Search · --datastore agent_platform_vector_search

Create a New Project

Constraints: Project name must be 26 characters or less, lowercase letters, numbers, and hyphens only. Do NOT mkdir the project directory before running create — the CLI creates it automatically. If you mkdir first, create will fail or behave unexpectedly. Auto-detect the guidance filename based on the IDE you are running in and pass --agent-guidance-filename accordingly (GEMINI.md for Gemini CLI, CLAUDE.md for Claude Code, AGENTS.md for OpenAI Codex/other).

Reference Files

File · Contents references/flags.md · Full flag reference for create and enhance commands

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Python · Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Choose Architecture

Mapping user choices to CLI flags: Choice · CLI flag RAG with vector search · `--agent agentic_rag --datastore agent_platform_vector_search` RAG with document search · `--agent agentic_rag --datastore agent_platform_search` A2A protocol · `--agent adk_a2a`

02
Step 2: Create or Enhance the Project

Step 2: Create or Enhance the Project

03
Step 3: Load Dev Workflow

After scaffolding, save `DESIGN_SPEC.md` to the project root if it isn't there already. Then immediately load `/google-agents-cli-workflow` — it contains the development workflow, coding guidelines, and operational rules you must follow when implementing the agent. Key files to customize: `app/agent.py` (instruction, tools, model), `app/tools.py` (custom tool functions), `.env` (project ID, location, API keys).

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.