Installs into .claude/skills of the current project.
Are you the author of Tech Api Development Testing Team?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/whyzsm-tech-api-development-testing-team)
---
name: tech-api-development-testing-team
description: "API接口开发测试专家。用于专注接口全生命周期,覆盖端点搭建、自动化测试、OpenAPI 文档生成、Mock 和联调。来源于 WorkBuddy 技术卡片,并转换为 Codex 可安装的专家入口格式。"
metadata:
source: "workbuddy-expert-center/技术/tech-api-development-testing"
workbuddy_card: "API接口开发测试专家"
workbuddy_category: "技术"
---
# API接口开发测试专家
Use this skill as the routing entry point for API接口开发测试专家 work. It packages the WorkBuddy 技术 expert card into a Codex skill entry that can live in this repository without installing WorkBuddy.
## Workflow
1. Read `references/guide.md` to classify the request, source inputs, overlap with existing expert teams, and expected artifacts.
2. Use the narrowest relevant capability module from the guide. For full-package requests, follow `references/workflow.md` in order.
3. Ask only for missing context that blocks a useful next output: target user, scenario, source material, constraints, quality bar, timeline, current evidence, or expected deliverable.
4. Keep WorkBuddy extraction provenance explicit: this package is converted from visible card metadata, not from a hidden expert-detail prompt.
5. Return concrete deliverables, evidence where applicable, open questions, risks, confidence level, and next-step suggestions.
## Source Capability Modules
- `tech-api-development-testing-intake`
- `tech-api-development-testing-strategy`
- `tech-api-development-testing-execution`
- `tech-api-development-testing-quality`
- `tech-api-development-testing-measurement`
- `tech-api-development-testing-handoff`
## Output
Produce only the deliverables relevant to the request. For a full API接口开发测试专家 package, assemble the output set described in `references/workflow.md`.