AD dev-find-log-skill
DEV 测试环境服务器日志搜索与分析工具。当用户需要搜索测试环境日志、查找错误、 排查测试环境问题、查询 traceId/requestId/订单号/请求记录、或者说"帮我查一下测试日志"、 "查 dev 日志"、"看看测试环境有没有"、"grep 一下测试服"时，必须使用此 skill。 校验、生单、支付、申请出票等交易场景，按采购侧→平台侧→供应侧→order 分层搜索，且必须并行查询。 平台侧判断为供应底层请求/响应问题时，Agent 必须自动继续查供应侧日志（禁止询问用户是否继续）；确认供应响应报错后必须告知用户并输出底层 HTTP 请求与响应报文。 关键词：测试环境、dev、查日志、搜日志、找日志、grep、traceId、requestId、校验、生单、支付、出票、 export、b2b、agg_deve、adapter_route_deve、adapter_api、ndcAdapter_deve、order_deve、 ota_ztC、adapter_ota_ztC、服务泳道标签、agg_zzr、 供应底层、请求报文、响应报文、supplierChannel。
DEV 测试环境服务器日志搜索与分析工具。当用户需要搜索测试环境日志、查找错误、 排查测试环境问题、查询 traceId/requestId/订单号/请求记录、或者说"帮我查一下测试日志"、 "查 dev 日志"、"看看测试环境有没有"、"grep 一下测试服"时，必须使用此 skill。…
As a process D 43/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when")
Process rating: all ten parameters 43/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
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (dev-find-log-skill) differs from the folder (zzrtest)
- 60Tools and files. Uses tools (bash) that frontmatter does not declare
- 100Steps. 58 steps
- 100Execution cost. Instruction body is 2909 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 4 example trigger phrases
- +3Description length 494: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 58 items
- +4Has examples (11 code blocks)
- +4Reference files are cited in the instructions (1 of 2)
- +3All 1 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.