agy-customizations

Create a directory under .agents/skills/ containing a SKILL.md file with YAML frontmatter defining name and description. Add optional scripts/, references/, or resources/ subdirectories and link to them from SKILL.md using relative paths.

Rules are Markdown guidelines loaded hierarchically from GEMINI.md or AGENTS.md files. Skills are on-demand runbooks loaded only when activated. Plugins bundle skills, rules, hooks, and MCP configs into a single shareable unit with a plugin.json manifest.

Hooks execute shell commands at agent lifecycle events like PreToolUse, PostToolUse, PreInvocation, and Stop. Each hook receives a JSON payload on stdin and returns a JSON decision on stdout, such as allowing, denying, or asking about a tool execution.

It searches workspace .agents directories walking up to the repository root, hierarchical GEMINI.md and AGENTS.md files, and the global ~/.gemini/config/ directory. Workspace customizations take the highest priority, followed by declared configs, global discovery, and built-ins.

Yes. Commit skills to a shared repository directory and add a skills.json in .agents/ pointing to that path with a workspace-relative entry. Teammates who clone the repo automatically discover and load the shared skills.

Hooks only support the command type for shell execution, with no HTTP or prompt hooks available. They run synchronously and block the agent loop, so long-running commands directly slow down agent execution.