AC openapi-contract-driven
OpenAPI Contract-Driven Development workflow for multi-agent teams. Solves the systemic defect of "frontend invents endpoints, backend forgets to implement" in multi-agent collaboration. Use when: (1) starting a new project or standardizing API collaboration, (2) frequently seeing "blank page / 500 / 502" with no clear root cause, (3) need to establish API contract system across human/AI agent teams. OpenAPI 契约驱动开发工作流。解决多 Agent 协作中「前端自造端点，后端漏实现」 这个系统性缺陷。Use when: (1) 新项目启动或已有项目需要规范 API 协作， (2) 频繁出现"页面空白 / 500 / 502"但找不到根因， (3) 需要在多人/AI agent 团队中建立 API 契约体系。 NOT for: 单人项目、临时脚本、非 REST API 项目。
OpenAPI Contract-Driven Development workflow for multi-agent teams.
As a process C 50/100 · Has gaps — weak spots: result and completion, inputs and preconditions, failures and branches
How to improve
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 14. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 50/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 100Steps. 10 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1306 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 3 example trigger phrases
- +4Description says when NOT to use the skill
- +3Description length 597: enough signal without eating the budget
- +4Structure: 17 headings
- +3Step-by-step instructions: 10 items
- +4Has examples (8 code blocks)
- +4Reference files are cited in the instructions (1 of 1)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 97.