Gemini & Google tools Give Gemini concrete examples, then choose the right route for chat, coding or structured data. Reviewed 15 November 2026 · Utilising AI Pty Ltd https://www.utilisingai.com/learn/gemini-google-tools Gemini Apps, Gemini CLI and the Gemini API are separate surfaces. CLI commands below belong in an installed terminal tool, not in a Google Docs document or an ordinary Gemini chat. Independent educational guide. Original examples; documentation-based guidance. Product availability varies. No provider integration or AI request is run by this download. Quick start =========== 1. Choose a small task and attach or paste only the relevant, permitted source material. 2. Describe the required output and show one example of the format. 3. Check the result against the source; refine one requirement before reusing the prompt. Practical tips ============== Show the shape of a good answer Google’s prompt guide recommends concrete examples. Demonstrate the fields, length or tone you want, using a consistent format. Include a tricky case as well as an easy one, so the model has a pattern for handling missing information. https://aistudio.google.com/docs/prompting-strategies Give the input a clear boundary Label the source material and the task separately. Specify whether the model should summarise, extract or compare. Keep the requested output format consistent across follow-ups instead of combining several unrelated jobs into one prompt. https://aistudio.google.com/docs/prompting-strategies Inspect sources when they appear Gemini Apps can show related links and sources, but not every response includes them. A source link is a place to investigate, not proof of every sentence in the answer. Open it and find the passage that supports your claim. https://support.google.com/gemini/answer/14143489?hl=en Developer notes =============== Give the CLI a reusable project context Gemini CLI reads GEMINI.md context files. Put the project’s real test commands and relevant conventions there. Use /memory show to inspect loaded instructions and /memory reload after editing them. These are CLI commands, not a universal Gemini Apps feature. https://geminicli.com/docs/cli/gemini-md/ Use a schema when software consumes the answer For API extraction jobs, configure structured output with a supported JSON Schema instead of only asking for JSON in prose. Then validate required fields and business rules in your own application. Matching a schema does not prove the extracted facts are correct. https://aistudio.google.com/docs/structured-output Check the sandbox before allowing edits Gemini CLI supports sandboxing; the -s flag enables it with the available platform setup. Review the configured access and tool actions. Sandbox setup varies by operating system and backend, so follow the official prerequisites for your machine. https://geminicli.com/docs/cli/sandbox/ Original examples to adapt ========================== Extract a useful action list From the notes below, extract actions as a table: action | owner | due date | source line. Use “not stated” for absent values. Example: “Mina to draft menu by Friday” → “Draft menu | Mina | Friday | [line]”. Do not add actions that are not in the notes. Notes: [paste permitted notes] Original business example. Confirm names and dates before assigning work. https://aistudio.google.com/docs/prompting-strategies Gemini CLI context checks /memory show /memory reload Run each separately in an installed Gemini CLI session. The first shows loaded context; the second refreshes it. https://geminicli.com/docs/cli/gemini-md/ A focused coding request Inspect [file or function] and explain the cause of [exact failure]. Use our existing library versions. Propose the smallest change and a test using input [example] with expected output [result]. After the fix, run the relevant test and show its actual outcome. Original coding brief. Use Gemini CLI with project access, or attach the necessary code in chat. https://aistudio.google.com/docs/prompting-strategies Check the result ================ - Do extracted values match the original material? - Are CLI instructions being used in the correct tool? - For API data, do both schema validation and real-world checks pass? Common mistakes =============== - Assuming every Google account has the same connected Workspace features. - Using structured JSON as evidence that the data is true. - Running a pasted shell command before understanding its effects. Sources ======= Google · Gemini prompt design · Official developer documentation https://aistudio.google.com/docs/prompting-strategies Google · Sources in Gemini Apps · Official help https://support.google.com/gemini/answer/14143489?hl=en Google · Gemini CLI project context · Official developer documentation https://geminicli.com/docs/cli/gemini-md/ Google · Structured outputs · Official developer documentation https://aistudio.google.com/docs/structured-output Google · Gemini CLI sandboxing · Official developer documentation https://geminicli.com/docs/cli/sandbox/