invoke_agent functionality to Agent Skills.You can see the detail information here https://github.com/tanaikech/GeminiWithFiles
UrlFetchApp.fetchAll for much faster folder structure retrieval and folder creation.test.js) to allow safe, automated validation of the library’s functionality.You can see the detail information here https://github.com/tanaikech/MoveFolder
As an active researcher and developer in the AI ecosystem, I have seamlessly integrated Agent Skills into daily workflows using tools like Claude Code, Gemini CLI, and Antigravity. However, I observed a pervasive tendency in the developer community—and initially within my own practice—to treat these capabilities as opaque black boxes. There is a distinct lack of granular understanding regarding the internal execution steps and the recursive orchestration occurring within Generative AI models when a skill mandates subagent delegation.
skillFolderId property to the geminiWithFiles constructor to automatically discover skills, register necessary functions (activate_skill, read_skill_resource, run_dynamic_script), and manage the autonomous execution loop.run_dynamic_script tool to dynamically execute .js scripts stored within the skill folders.generateContent to fully support multi-turn function calling loops.You can see the detail information here https://github.com/tanaikech/GeminiWithFiles
As Large Language Model (LLM) agents increasingly integrate numerous external systems, they suffer from Tool Space Interference (TSI), a phenomenon causing context bloat, attention dilution, and degraded reasoning accuracy. In this paper, we introduce the Agent-as-a-Tool paradigm—an evolutionary, practical implementation of the recently proposed Self-Optimizing Tool Caching Network (SOTCN) and Federated Context-Aware Routing Architecture (Federated CARA). By leveraging Retrieval-Augmented Generation (RAG) to dynamically discover and assemble stateful, autonomous sub-agents on the fly, this architecture completely eliminates TSI, enforces Zero-Trust execution boundaries, and achieves infinitely scalable AI orchestration.
A Comparative Study of Agentic Frameworks and Multi-Agent Orchestration
The transition from passive chatbots to autonomous execution environments was cemented at Google Cloud Next ‘26 with the introduction of the Gemini Enterprise Agent Platform. This paper evaluates four cutting-edge AI agent methodologies for Google Workspace automation, developed by leading developers Martin Hawksey, Bruce Mcpherson, and Kanshi Tanaike. We deconstruct their structural approaches—CLI skill chaining, advanced emulation sandboxing, dynamic code generation, and A2A remote delegation—demonstrating how these community-driven innovations anticipated native Next ‘26 features like the official Agent Skills repository and Model Context Protocol (MCP) support. Building upon these foundations, we propose two novel frameworks: the Federated Context-Aware Routing Architecture (Federated CARA) for zero-trust, multi-cloud task routing, and the Self-Optimizing Tool Caching Network (SOTCN) to eliminate Tool Space Interference using dynamic semantic caching. This comparative synthesis maps existing and proposed models against Google’s new enterprise standards, offering a scalable roadmap for secure, highly dynamic multi-agent orchestration.
Welcome to the Agentic Enterprise era. This article explores a paradigm shift in generative AI workflows by introducing an autonomous agent capable of dynamically creating, testing, and executing original tools. Utilizing Google Apps Script, Node.js emulation, and multi-agent orchestration, this architecture overcomes traditional limitations, enabling highly adaptable task execution.
At Google Cloud Next 2026, a clear mandate was delivered: the era of generative AI as a passive assistant is over. We have entered the age of the Agentic Enterprise, where AI has transitioned from a software tool you deploy into an autonomous coworker you onboard. This identity shift is staggering. With models processing over 16 billion tokens per minute via direct API use, we are witnessing an industrial-scale migration toward autonomous workflows. In this new ecosystem, Workspace Intelligence eliminates tab-hopping, allowing users to seamlessly query across Google Drive, Gmail, and third-party platforms. Data has transformed from a reactive archive into a “System of Action,” driven by Deep Research Agents that bridge structured and unstructured data to prevent hallucinations.
Explore how to build and orchestrate production-ready, type-safe AI agents using Google’s TypeScript Agent Development Kit (ADK). This guide provides practical scaffolding patterns, multi-agent coordination strategies, and seamless integration techniques for deploying remote subagents within the Gemini CLI ecosystem.
As the artificial intelligence landscape rapidly evolves, modern generative AI increasingly relies on autonomous agents equipped with sophisticated components, including system instructions, specialized skills, and Model Context Protocol (MCP) servers. To facilitate the development of such AI-driven applications, Google has released the Agent Development Kit (ADK) across multiple programming languages Ref. Among these, the ADK for TypeScript Ref offers distinct advantages for modern engineering paradigms:
This article explores integrating remote subagents built with Google Apps Script into the Gemini CLI using the Agent-to-Agent (A2A) protocol. It demonstrates how bypassing standard authentication via local agent cards enables seamless execution of complex workflows while effectively overcoming Tool Space Interference (TSI) for massive toolsets.
Recently, remote subagent support was introduced to the Gemini CLI. Ref With this feature, the Gemini CLI connects to remote subagents using the Agent-to-Agent (A2A) protocol, expanding its capabilities by delegating tasks to external services. I have previously published several articles discussing the A2A server architecture:
Google Sheets recently introduced the SHEET and SHEETS functions. Because they automatically recalculate upon structural changes, developers can utilize them as custom triggers. This article demonstrates how to leverage these functions to detect sheet insertions, deletions, renames, and movements without requiring cumbersome installable triggers in Google Apps Script.
On February 23, 2026, Google introduced two pivotal built-in functions to Google Sheets: SHEET and SHEETS Ref. The SHEET function returns the index (sheet number) of a specified sheet or reference Ref. Meanwhile, the SHEETS function provides the total count of sheets within a spreadsheet Ref.