AB alibabacloud-oss-client-tools-diagnosis
Read-only diagnosis of OSS client tool failures. Use when the customer reports an ossbrowser login failure or 403, an ossutil error such as InvalidAccessKeyId, AccessDenied, a missing or expired STS token, a connect timeout while uploading files, or a RequestTimeTooSkewed clock skew, when a client cannot connect to OSS, or when the customer asks which ossbrowser or ossutil version to standardize on. Also use for a troubleshooting plan or information checklist. Triggers: "ossbrowser login failed", "ossbrowser 403", "ossutil AccessDenied", "ossutil InvalidAccessKeyId", "client cannot connect to OSS", "RequestTimeTooSkewed", "SecurityTokenExpired", "SigningContext.Credentials", "region must be set in sign version 4", "The Security Token may be lost". Answers only; runs no client commands, calls no cloud API. Do NOT use for SDK/API errors not naming ossbrowser or ossutil, endpoint selection, presigned URL, billing, or throttling (503/SlowDown).
Read-only diagnosis of OSS client tool failures.
As a process B 71/100 · Nearly there — weak spots: result and completion, running it twice, progress reporting
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: 11. 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 71/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web, python) that frontmatter does not declare
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 28 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3877 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 16 top-level sections: this looks like several domains in one skill
- low The skill ranks results itself: that belongs to the system behind the tool, not the model
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
- +3Description length 954: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 8 example trigger phrases
- +4Description says when NOT to use the skill
- +4Structure: 18 headings
- +3Step-by-step instructions: 28 items
- +4Has examples (1 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 3 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 97.