RustChain Bounty Hunter-v2-1

Automates RustChain bounty hunting by coding, testing, and preparing PRs for low-competition issues with full test coverage and bonus claims.

This skill is missing critical, expected details for its claimed actions. Before installing or using it: - Don’t hand over high-privilege credentials (GitHub tokens with broad repo write access or any private keys/wallet seeds). If you must provide a token, create a scoped, short-lived token limited to a single fork and repository and prefer read-only where possible. - Ask the author how the skill authenticates and what exact permissions it needs (git/GH CLI? OAuth flow? repo scope? wallet signing?). Require a clear list of required env vars and binaries. - Demand transparency: request examples of the exact commands it will run, where tests execute, and how it prepares PRs (drafts only? pushes to a fork?). Prefer an approach where the agent prepares a local branch/patch that you review and push yourself. - Avoid providing private keys or wallet seeds. For claiming on-chain rewards, prefer a manual signing workflow or use a hardware wallet/transaction relay you control. - Test in a sandbox/fork with no valuable access first. Review all diffs produced by the skill before merging or pushing to main repos. - If you want a stronger assurance, ask the publisher for source code or a reproducible runbook so an auditor can verify there is no hidden exfiltration or undisclosed network calls. Given the inconsistencies, treat this skill as untrusted until the author documents exactly how repository and on-chain interactions are performed and which credentials are required.

Type: OpenClaw Skill Name: rustchain-bounty-hunter-v2-1 Version: 1.0.0 The skill bundle contains only metadata and documentation (SKILL.md) for automating software development tasks related to 'RustChain' bounties. It lacks any executable code, scripts, or instructions that would lead to data exfiltration, unauthorized access, or malicious system modifications. The instructions are focused on legitimate development activities like coding, testing, and creating pull requests.