{"owner":"567-labs","repo":"google","hasSkills":true,"totalSkillsCount":4,"totalTokensCount":1358,"categories":["mcp-config","marketplace","plugin-manifest","cursor-rule"],"hasMcp":true,"mcpConfig":{"mcpServers":{"google":{"command":"npx","args":["-y","@modelcontextprotocol/server-google"]}}},"found":[".cursor/mcp.json",".claude-plugin/marketplace.json",".claude-plugin/plugin.json",".cursorrules (google-adk.mdc)"],"skills":{".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/567-labs/google/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/567-labs/google/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/567-labs/google/HEAD/.claude-plugin/plugin.json)",".cursorrules (google-adk.mdc)":"# Google ADK Rules\n\n## Agent Design\n\n- Keep each agent focused on a clear goal, persona, and tool set.\n- Use LLM agents for flexible reasoning and workflow agents for deterministic orchestration.\n- Write instructions that define task boundaries, tool-use rules, and escalation behavior.\n- Split multi-agent systems by responsibility rather than by implementation convenience.\n- Keep model choices configurable.\n\n## Tools\n\n- Give tools narrow, typed inputs and outputs.\n- Validate tool arguments before performing side effects.\n- Keep secrets, credentials, and privileged APIs out of agent prompts.\n- Handle tool errors explicitly and return actionable failure messages.\n- Be aware of ADK tool limitations; some built-in tools cannot be combined with other tools on the same agent.\n\n## Sessions, State, and Memory\n\n- Use session state for current-conversation data.\n- Use memory for cross-session recall and retrieval.\n- Keep state small and serializable.\n- Do not store large files or binary payloads in session state.\n- Make state keys stable and documented.\n\n## Artifacts\n\n- Use artifacts for generated files, uploaded files, reports, images, audio, and other binary data.\n- Configure an artifact service in the runner before relying on artifact operations.\n- Version artifact filenames intentionally and avoid overwriting semantically different outputs.\n- Store only references or summaries in state when full content belongs in artifacts.\n\n## Evaluation and Deployment\n\n- Add tests for tool behavior, agent routing, prompt regressions, and unsafe tool calls.\n- Use trace or event logs to debug agent decisions.\n- Keep local development, staging, and production configuration separate.\n- Add observability for latency, tool failures, token use, and handoff failures.\n\n## Common Mistakes\n\n- Do not make one agent responsible for every workflow.\n- Do not let tools accept arbitrary shell, SQL, or HTTP input without validation.\n- Do not rely on prompt text for access control.\n- Do not hide important side effects behind generic tool names."},"files":{".cursor/mcp.json":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/567-labs/google/HEAD/.cursor/mcp.json)",".claude-plugin/marketplace.json":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/567-labs/google/HEAD/.claude-plugin/marketplace.json)",".claude-plugin/plugin.json":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/567-labs/google/HEAD/.claude-plugin/plugin.json)",".cursorrules (google-adk.mdc)":"# Google ADK Rules\n\n## Agent Design\n\n- Keep each agent focused on a clear goal, persona, and tool set.\n- Use LLM agents for flexible reasoning and workflow agents for deterministic orchestration.\n- Write instructions that define task boundaries, tool-use rules, and escalation behavior.\n- Split multi-agent systems by responsibility rather than by implementation convenience.\n- Keep model choices configurable.\n\n## Tools\n\n- Give tools narrow, typed inputs and outputs.\n- Validate tool arguments before performing side effects.\n- Keep secrets, credentials, and privileged APIs out of agent prompts.\n- Handle tool errors explicitly and return actionable failure messages.\n- Be aware of ADK tool limitations; some built-in tools cannot be combined with other tools on the same agent.\n\n## Sessions, State, and Memory\n\n- Use session state for current-conversation data.\n- Use memory for cross-session recall and retrieval.\n- Keep state small and serializable.\n- Do not store large files or binary payloads in session state.\n- Make state keys stable and documented.\n\n## Artifacts\n\n- Use artifacts for generated files, uploaded files, reports, images, audio, and other binary data.\n- Configure an artifact service in the runner before relying on artifact operations.\n- Version artifact filenames intentionally and avoid overwriting semantically different outputs.\n- Store only references or summaries in state when full content belongs in artifacts.\n\n## Evaluation and Deployment\n\n- Add tests for tool behavior, agent routing, prompt regressions, and unsafe tool calls.\n- Use trace or event logs to debug agent decisions.\n- Keep local development, staging, and production configuration separate.\n- Add observability for latency, tool failures, token use, and handoff failures.\n\n## Common Mistakes\n\n- Do not make one agent responsible for every workflow.\n- Do not let tools accept arbitrary shell, SQL, or HTTP input without validation.\n- Do not rely on prompt text for access control.\n- Do not hide important side effects behind generic tool names."},"items":[{"name":"marketplace.json","path":".claude-plugin/marketplace.json","rawUrl":"https://raw.githubusercontent.com/567-labs/google/HEAD/.claude-plugin/marketplace.json","title":"Claude Plugin Marketplace Catalog","category":"marketplace","format":"json","content":"# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/567-labs/google/HEAD/.claude-plugin/marketplace.json)","tokens":300,"sizeBytes":194},{"name":"plugin.json","path":".claude-plugin/plugin.json","rawUrl":"https://raw.githubusercontent.com/567-labs/google/HEAD/.claude-plugin/plugin.json","title":"claude-plugin Plugin Manifest","category":"plugin-manifest","format":"json","content":"# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/567-labs/google/HEAD/.claude-plugin/plugin.json)","tokens":300,"sizeBytes":180},{"name":"mcp.json","path":".cursor/mcp.json","rawUrl":"https://raw.githubusercontent.com/567-labs/google/HEAD/.cursor/mcp.json","title":"Model Context Protocol (MCP) Configuration","category":"mcp-config","format":"json","content":"# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/567-labs/google/HEAD/.cursor/mcp.json)","tokens":300,"sizeBytes":173},{"name":".cursorrules","path":".cursorrules (google-adk.mdc)","rawUrl":"https://raw.githubusercontent.com/PatrickJS/awesome-cursorrules/main/rules/google-adk.mdc","title":"Google Agent Development Kit rules for agents, tools, sessions, memory, artifacts, evaluation, and deployment","category":"cursor-rule","format":"markdown","content":"# Google ADK Rules\n\n## Agent Design\n\n- Keep each agent focused on a clear goal, persona, and tool set.\n- Use LLM agents for flexible reasoning and workflow agents for deterministic orchestration.\n- Write instructions that define task boundaries, tool-use rules, and escalation behavior.\n- Split multi-agent systems by responsibility rather than by implementation convenience.\n- Keep model choices configurable.\n\n## Tools\n\n- Give tools narrow, typed inputs and outputs.\n- Validate tool arguments before performing side effects.\n- Keep secrets, credentials, and privileged APIs out of agent prompts.\n- Handle tool errors explicitly and return actionable failure messages.\n- Be aware of ADK tool limitations; some built-in tools cannot be combined with other tools on the same agent.\n\n## Sessions, State, and Memory\n\n- Use session state for current-conversation data.\n- Use memory for cross-session recall and retrieval.\n- Keep state small and serializable.\n- Do not store large files or binary payloads in session state.\n- Make state keys stable and documented.\n\n## Artifacts\n\n- Use artifacts for generated files, uploaded files, reports, images, audio, and other binary data.\n- Configure an artifact service in the runner before relying on artifact operations.\n- Version artifact filenames intentionally and avoid overwriting semantically different outputs.\n- Store only references or summaries in state when full content belongs in artifacts.\n\n## Evaluation and Deployment\n\n- Add tests for tool behavior, agent routing, prompt regressions, and unsafe tool calls.\n- Use trace or event logs to debug agent decisions.\n- Keep local development, staging, and production configuration separate.\n- Add observability for latency, tool failures, token use, and handoff failures.\n\n## Common Mistakes\n\n- Do not make one agent responsible for every workflow.\n- Do not let tools accept arbitrary shell, SQL, or HTTP input without validation.\n- Do not rely on prompt text for access control.\n- Do not hide important side effects behind generic tool names.","frontmatter":{"description":"Google Agent Development Kit rules for agents, tools, sessions, memory, artifacts, evaluation, and deployment","globs":["**/*.py","**/*.ts","**/*.tsx","**/*.go","**/*.java","pyproject.toml","package.json"],"alwaysApply":false},"tokens":458,"sizeBytes":2041}],"systemPromptSnippet":"<yakaai_skills repo=\"567-labs/google\">\n<!-- File: .claude-plugin/marketplace.json (Tokens: ~300 | Category: marketplace) -->\n# Claude Plugin Marketplace Catalog\n\nPath: `.claude-plugin/marketplace.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/567-labs/google/HEAD/.claude-plugin/marketplace.json)\n\n<!-- File: .claude-plugin/plugin.json (Tokens: ~300 | Category: plugin-manifest) -->\n# claude-plugin Plugin Manifest\n\nPath: `.claude-plugin/plugin.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/567-labs/google/HEAD/.claude-plugin/plugin.json)\n\n<!-- File: .cursor/mcp.json (Tokens: ~300 | Category: mcp-config) -->\n# Model Context Protocol (MCP) Configuration\n\nPath: `.cursor/mcp.json`\n\n[View Raw Content on GitHub](https://raw.githubusercontent.com/567-labs/google/HEAD/.cursor/mcp.json)\n\n<!-- File: .cursorrules (google-adk.mdc) (Tokens: ~458 | Category: cursor-rule) -->\n# Google ADK Rules\n\n## Agent Design\n\n- Keep each agent focused on a clear goal, persona, and tool set.\n- Use LLM agents for flexible reasoning and workflow agents for deterministic orchestration.\n- Write instructions that define task boundaries, tool-use rules, and escalation behavior.\n- Split multi-agent systems by responsibility rather than by implementation convenience.\n- Keep model choices configurable.\n\n## Tools\n\n- Give tools narrow, typed inputs and outputs.\n- Validate tool arguments before performing side effects.\n- Keep secrets, credentials, and privileged APIs out of agent prompts.\n- Handle tool errors explicitly and return actionable failure messages.\n- Be aware of ADK tool limitations; some built-in tools cannot be combined with other tools on the same agent.\n\n## Sessions, State, and Memory\n\n- Use session state for current-conversation data.\n- Use memory for cross-session recall and retrieval.\n- Keep state small and serializable.\n- Do not store large files or binary payloads in session state.\n- Make state keys stable and documented.\n\n## Artifacts\n\n- Use artifacts for generated files, uploaded files, reports, images, audio, and other binary data.\n- Configure an artifact service in the runner before relying on artifact operations.\n- Version artifact filenames intentionally and avoid overwriting semantically different outputs.\n- Store only references or summaries in state when full content belongs in artifacts.\n\n## Evaluation and Deployment\n\n- Add tests for tool behavior, agent routing, prompt regressions, and unsafe tool calls.\n- Use trace or event logs to debug agent decisions.\n- Keep local development, staging, and production configuration separate.\n- Add observability for latency, tool failures, token use, and handoff failures.\n\n## Common Mistakes\n\n- Do not make one agent responsible for every workflow.\n- Do not let tools accept arbitrary shell, SQL, or HTTP input without validation.\n- Do not rely on prompt text for access control.\n- Do not hide important side effects behind generic tool names.\n</yakaai_skills>"}