Builder & Platform Playbook

How to Create Skills, Flows, Agents & Workspaces

Step-by-step reference guide for customizing Gemini Enterprise at Hollywood Park—from packaging reusable SKILL.md rulebooks to building automated Flows in Workflow Builder and organizing team Projects, Inbox approvals, and NotebookLM notebooks.

1. Reusable Instructions & Standards

How to Create and Use a Skill

Instead of pasting the same rules or formatting instructions into every chat, save them once as a Skill. Gemini checks the short description of your Skills and automatically loads the full instructions only when your prompt needs them.

Browse existing HWP Skills →
StepLocation in Gemini EnterpriseAction
Step 1Left Navigation → SkillsOpen the Skills page in the Gemini Enterprise web app (ai.hollywoodparkca.com/chat).
Step 2Add (+) → Create skill with Gemini (or Upload)Create a Skill using guided prompts, or upload a SKILL.md or .zip package.
Step 3Name & Description fieldsWrite a clear description of when the Skill applies so Gemini knows when to activate it automatically.
Step 4Main Chat or More options (...) → New chatAsk a matching question in normal chat for automatic activation, or start a dedicated chat from the Skill menu.
Modular Skill Package Structure (.zip)
my-department-skill/
├── SKILL.md          # YAML frontmatter + core rules
├── references/       # Detailed checklists & policies
│   └── style-guide.md
├── assets/           # Output templates & examples
│   └── report-template.md
└── scripts/          # Optional helper scripts
    └── validate.py
💡 Pro Tip: Type @gemini-skill-creator right inside Gemini Chat and ask it to build and package your SKILL.md automatically!
2. Step-by-Step Automated Workflows

Flows: Building Repeatable Sequences in Workflow Builder

When a process requires a strict, repeatable sequence—where Step 1 must always happen before Step 2, or where timers and human approvals are needed—Flows (built in Workflow Builder) map out the exact path an Agent follows.

Component 1

1. Trigger (How it starts)

  • • Manual: Typed in chat via @flow_name.
  • • Schedule: Runs on a timer or Cron schedule (e.g., Mondays at 8:00 AM).
  • • Event: Starts automatically when an app event occurs (e.g., new Jira ticket or email).
Component 2

2. Main Agent & Subagents

Splits complex work across specialized helpers. A Main Agent receives the request and routes subtasks to up to 50 Subagents (1 level deep), such as a Research Subagent and a Drafting Subagent.

Component 3

3. Conditional Logic

Routes work down different branching paths based on data.

“If invoice amount > \$1,000, send to Path A (Manager Escalation); otherwise send to Path B (Standard Log).”

Component 4

4. Human Approval

Pauses the Flow at a review checkpoint until a person approves in Inbox—such as confirming before sending an external email or updating a system of record.

How to Build and Publish a Flow (4 Steps)

Step 1 • Open Workflow Builder

In the Gemini Enterprise web app, click Agents in the left menu, create or open an agent, and select the Flow tab.

Step 2 • Generate or Build on Canvas

Describe the process in plain text to auto-generate a starting Flow, or drag steps directly onto the visual canvas.

Step 3 • Attach Apps, Rules & Subagents

Click any step to connect tools (Drive, Gmail, Jira, Wrike), add if/else rules, or click Add subagent.

Step 4 • Preview & Publish

Test the sequence in the Preview tab, then click Create / Publish (supports up to 100 steps and 20 skills/actions per step).

3. Dedicated Specialists

When & How to Build a Custom Agent

Build an Agent when a use case requires a dedicated role persona, isolated lookup memory, and scoped access to specific internal apps (such as a specific Google Drive folder, Wrike space, Jira project, or BigQuery table).

1. Open No-Code Agent Builder
Left Navigation → Agents → Create

Give your Agent a clear role persona, system instructions, and starter prompts so teammates know what to ask it.

2. Scope Data & Tools
Attach Specific Connectors & Skills

Select which connected data stores (Drive, Wrike, Jira, BigQuery) and which organizational @Skills the Agent is authorized to use.

3. Share with Your Team
Test in Preview & Publish

Keep the Agent private for personal workflows, share it with specific Google Groups, or publish it to the district-wide Agent Gallery.

4. Workspace Organization & Oversight

Projects, Inbox & NotebookLM in Your Sidebar

🗂️ ProjectsLeft Sidebar

Shared Initiative Workspaces

  • • Dedicated File Grounding: Upload PDFs, spreadsheets, docs, or Drive files directly into a Project. Chats inside that Project are automatically grounded in those files without bleeding into unrelated chats.
  • • Team Collaboration: Keep private or share with teammates so everyone chats against the exact same reference set.
  • • Project vs. Agent vs. Skill: Use a Project to gather files for a temporary initiative; a Skill for a reusable task rulebook; an Agent for a permanent role-based assistant.
📥 InboxLeft Sidebar

Autonomous Run Command Center

Monitor scheduled Flows and background Agents across three queues:

  • • Needs your input: Agents or Flows paused at a Human-in-the-Loop checkpoint waiting for you to click Approve (e.g., external email or PO).
  • • Errors: Inspect failed steps to troubleshoot credentials, adjust inputs, or retry the run.
  • • Completed: Review final deliverables, summaries, and execution history.
📓 NotebookLMLeft Sidebar

Source-Locked Research & Audio

  • • Closed-World Synthesis: Upload manuals, contracts, transcripts, or slide decks into a dedicated notebook where every answer is 100% locked to those sources.
  • • Audio Overviews: Generate a 2-host conversational podcast briefing to listen to complex project materials on the go.
  • • Study Guides & Briefing Docs: One-click generation of FAQs, timelines, and executive summaries with pinned passage citations.
5. Putting It All Together

End-to-End Example: Automated Vendor Contract Review

Here is how Flows, Agents, Data Connectors, Skills, and Inbox work together during a single automated workflow:

Stage 1 • Flow
Trigger & Routing

A new vendor PDF is uploaded to Google Drive (Event Trigger). The Flow starts automatically, sends the file to the Contract Review Agent, and checks whether the contract value exceeds \$50,000.

Stage 2 • Agent + Data Connector
Live Data Lookup

The Contract Review Agent uses its authorized Drive & Wrike Data Connectors to read the 40-page agreement and verify prior vendor records.

Stage 3 • Skill
Applying Standards

While reviewing indemnity clauses, the Agent loads the team's Legal Redline Skill (SKILL.md), applying the exact fallback wording required by Legal.

Stage 4 • Inbox
Human Sign-Off

Because the contract exceeds \$50,000, the Flow pauses and places an item in the Legal VP's Inbox under Needs your input. Once approved, the run moves to Completed.