ClawHub

Help And Support

v0.1.0

Get help, onboarding guidance, and report issues. Use when you or the user need help with the wallet, have questions about how things work, want a walkthroug...

⭐ 0· 188·0 current·0 all-time
byRachid Jarray@rachidjarray-hk-qa-fdt
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
Name/description (help, onboarding, report issues) align with the runtime instructions which call fdx CLI subcommands (helpNarrative, onboardingAssistant, reportIssue, getAppVersion) and refer to related agent skills. There are no unrelated environment variables, binaries, or config paths requested.
✓
Instruction Scope
SKILL.md confines behavior to running fdx CLI commands and coordinating with other named skills (authenticate, wallet-overview, fund-wallet). It does not instruct reading arbitrary files, other env vars, or exfiltrating data. It does instruct including app version and status in reports (reasonable for bug reports).
✓
Install Mechanism
No install spec and no code files — instruction-only skill. Nothing is downloaded or written to disk by the skill itself.
✓
Credentials
The skill declares no required environment variables, no credentials, and no config paths. The only operational requirement is the fdx CLI and other internal skills, which is proportional to a wallet help/support skill.
✓
Persistence & Privilege
The skill is not marked always:true and model invocation is allowed (the platform default). It does not request persistent system-wide changes or modify other skills' configs.
Assessment
This skill appears coherent and low-risk: it only calls your wallet's CLI for help, onboarding, and bug reports. Before installing, confirm that the fdx CLI and the related skills (authenticate, reportIssue, etc.) are from a trusted source (there is no homepage/source URL in the metadata). Avoid including secrets (private keys, seed phrases, API keys) in any bug report descriptions. If you want extra assurance, review the authenticate and reportIssue skill implementations (or their provenance) to confirm how authentication and report submission are handled.

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

latestvk9726tszsvy09enjgbwmfdp8r982jth7

License

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

Comments