Skills/ClawHub/alibabacloud-waf-openapi-error-diagnosis

alibabacloud-waf-openapi-error-diagnosis@0.0.1

CAUTION

Publisher claims: "Diagnose why an Alibaba Cloud WAF OpenAPI call failed: find which request parameter's name, format, value, or required-ness disagrees with the official spec, and return a corrected call in the same channel. Covers BOTH generations -- WAF 2.0 (version 2019-09-10) and WAF 3.0 (version 2021-10-01) -- across CLI, SDK, and raw RPC. Read-only: fetches the authoritative parameter spec and diffs the request; never runs a write action and needs no credentials for the core diff. Use when a call returns InvalidParameter / MissingParameter / a malformed-parameter error, when parameters filled per the docs still fail, when a CLI action is "not available in the current API version", or when asked which parameter is wrong. Not for: credential/signature, RAM denials, throttling, not-purchased, server 5xx, rule-not-effective, or why one request was blocked. Triggers: "WAF OpenAPI 报错", "InvalidParameter", "MissingParameter", "参数格式错误", "哪个参数错了", "not available in the current API version", "which parameter is wrong"" Observed in sandbox: static analysis only — behavior not yet observed.

Registry ClawHubPublisher sdk-team · joined 13 days agoInstalls 209Last detonated 1 h ago
What would fix thisWatchDispute verdict

Is [email protected] safe to install?

KillerSkills analysed it statically (a sandbox run is pending) on 2026-11-04 and scored it 62/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: Privileged sudo command; 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

MEDIUM
Python subprocess execution detectedscripts/diagnose_openapi_error.py:227 · Python subprocess execution detectedFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
HIGH
Privileged sudo commandSKILL.md:118 · Privileged sudo command — agent may execute with elevated privilegesFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
HIGH
Authorization escalation languagereferences/cli-installation-guide.md:70 · Authorization escalation languageFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.
AST01

What would make this Verified

18 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. Privileged sudo command≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
  3. 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.
  4. Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
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