ClawHub

Adversarial Robustness Toolbox

v3.0.2

Reference tool for devtools — covers intro, quickstart, patterns and more. Quick lookup for Adversarial Robustness Toolbox concepts, best practices, and impl...

⭐ 0· 295·0 current·0 all-time
bybytesagain4@xueyetianya
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The name/description (Adversarial Robustness Toolbox reference) match the provided files. The SKILL.md and scripts/script.sh both implement only local reference output; there are no unrelated environment variables, binaries, or cloud credentials requested.
ℹ
Instruction Scope
SKILL.md explicitly states outputs are plain-text heredocs with no external API calls. The included script only emits static documentation. Minor inconsistency: the quickstart text mentions 'Required tools and access credentials' as generic guidance, but elsewhere the skill says no API keys or credentials are required — this appears to be documentation phrasing rather than an actual requirement.
✓
Install Mechanism
No install spec is present (instruction-only style). A single bash script is included but it only prints static content; nothing is downloaded or written to arbitrary locations during runtime.
✓
Credentials
The skill requests no environment variables, no credentials, and no config paths. The runtime files do not read environment variables or access external secrets.
✓
Persistence & Privilege
always is false, the skill does not request persistent/system-wide privileges or modify other skills or agent settings. It runs as an on-demand reference tool.
Assessment
This skill appears safe and coherent: it only prints local reference documentation and does not require credentials, network access, or installs. As a general precaution, review the included script before running it and, if you plan to execute it on sensitive systems, consider running it in a sandbox or isolated environment. Note the small documentation wording inconsistency in the quickstart (mentioning "access credentials") — it doesn't change behavior but you may want to confirm there are truly no external dependencies before integrating into automated workflows.

Like a lobster shell, security has layers — review code before you run it.

latestvk97506px0wy4gdpszybjahtnr583gtb7

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments