Skills/ClawHub/alibabacloud-oss-client-tools-diagnosis

alibabacloud-oss-client-tools-diagnosis@0.0.1

CAUTION

Publisher claims: "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)." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher sdk-team · joined 12 days agoInstalls 195Last detonated 6d ago
What would fix thisWatchDispute verdict

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-10-29 and scored it 67/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Summary: static analysis only — behavior not yet observed.

Behavior trace

Queued for honeypot run · static analysis only
t+CategoryObserved action

This version has not been detonated yet. The score above counts behavior as unknown (50/100), so it cannot read Verified until the honeypot run completes and replaces this verdict.

Static findings

No findings across 1,835 lines in 11 files.

What would make this Verified

13 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. Unclaimed publisher≈ +8 on the totalClaim sdk-team: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  2. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
Publish a new version to ClawHub, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim sdk-team