# google-agent-skill-design

**Repository Path**: fexeak/google-agent-skill-design

## Basic Information

- **Project Name**: google-agent-skill-design
- **Description**: No description available
- **Primary Language**: Unknown
- **License**: Not specified
- **Default Branch**: master
- **Homepage**: None
- **GVP Project**: No

## Statistics

- **Stars**: 0
- **Forks**: 0
- **Created**: 2026-04-01
- **Last Updated**: 2026-04-01

## Categories & Tags

**Categories**: Uncategorized

**Tags**: None

## README

# 每位ADK开发者都应掌握的5个代理技能设计模式

本文介绍了每个带有正常 ADK 代码的版本

1. Tool Wrapper（工具包装器）：让你的 Agent 瞬间成为某个库的专家 api-expert
2. Generator（生成器）：用可复用模板输出结构化文档 report-generator
3. Reviewer（审查器）：按严重程度对代码逐条打分 code-reviewer
4. Inversion（反转模式）：Agent 先来采访你，再动手做 project-planner
5. Pipeline（流水线）：带检查点的严格多步工作流 doc-pipeline

## Try It

测试这些Queries，以查看每种模式的实际效果:

| Query | Pattern Triggered | What Happens |
|-------|------------------|-------------|
| "Review this Python code: `def ProcessData(input, data=[]): ...`" /code-reviewer review 当前目录下game.py的代码 | Reviewer | Loads checklist, catches 3 bugs, produces scored report |
| "Write a technical report on our API migration" /report-generator 编写一份关于API迁移的技术报告| Generator | Loads template + style guide, fills report sections |
| "Help me plan a new microservice" /project-planner 请帮我规划一个新的微服务| Inversion | Asks 6 structured questions across 3 phases before planning |
| "How should I handle FastAPI dependency injection?" /api-expert 我应该如何处理 FastAPI 依赖注入| Tool Wrapper | Loads FastAPI conventions, applies best practices |
| "Document this Python module" /doc-pipline 为当前目录下的game.py编写文档| Pipeline | 4-step workflow: Parse → Generate → Assemble → Quality Check |