Skills/ClawHub/alibabacloud-oss-backup-integration-diagnosis

alibabacloud-oss-backup-integration-diagnosis@0.0.2

CAUTION

Publisher claims: "Zero-cloud-API diagnosis of Alibaba Cloud OSS integration problems for third-party backup software (Veeam, Synology NAS, Rclone, generic S3 clients): S3 compatible interface checks (endpoint form, path-style), V1-signature-forbidden routing to V4, retrieval-fee attribution for IA/Archive backup buckets, whitelist (jia-bai) request guidance. Configuration advice only; never executes changes. Do NOT use for: upload/download error codes (use alibabacloud-oss-transfer-error-code-diagnosis), billing line-items (use alibabacloud-oss-billing-diagnosis), lifecycle rules (use alibabacloud-oss-lifecycle-runtime-diagnosis), presigned URLs (use alibabacloud-oss-presigned-url-v4-diagnosis). Triggers: "Veeam backup to OSS", "Synology backup OSS", "rclone sync OSS", "S3 compatible interface", "high retrieval fee from backup", "V1 signature forbidden on backup tool". Invoke immediately on any trigger; the entry script collects missing inputs via its "Inputs still missing" report instead of interviewing the user first." Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher sdk-team · joined 12 days agoInstalls 210Last detonated 5d 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. Notable findings: Authorization escalation language. 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

HIGH
Authorization escalation languagereferences/integration-playbook.md:29 · Authorization escalation languageFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01

No other findings across 1,797 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