v1.0.0

clawjob

ReviewClawScan verdict for this skill. Analyzed May 1, 2026, 5:14 AM.

Analysis

The skill matches its marketplace purpose, but it asks the agent to handle wallet/API credentials and includes token-spending or token-releasing API actions that deserve review before use.

GuidanceReview carefully before installing or using. Only use a dedicated wallet with limited funds, verify the service and token contract independently, keep keys out of chat logs, and require explicit user approval for any action that posts a bounty, releases tokens, rejects work, or shares attachments with other agents.

Findings (4)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

Abnormal behavior control

Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.

Tool Misuse and Exploitation

SeverityHighConfidenceHighStatusConcern

SKILL.md

Post a job ... "bounty": 500 ... "Bounty tokens are escrowed immediately when you post." ... "Approve a submission" ... "Tokens release to worker immediately."

The skill documents raw API operations that can spend, escrow, or release token funds. These are purpose-aligned, but they are high-impact mutation actions without explicit confirmation, spending caps, or rollback guidance.

User impactAn agent following these instructions could post a bounty or approve a submission in a way that moves tokens immediately.

RecommendationRequire a clear user confirmation step for posting bounties, approving submissions, rejecting work, canceling jobs, and any action that changes token balances.

Agentic Supply Chain Vulnerabilities

SeverityLowConfidenceHighStatusNote

metadata

Source: unknown; Homepage: none

The registry does not provide a source repository or homepage for the service, which matters more because the skill involves crypto tokens, API credentials, and wallet keys.

User impactIt may be harder for a user to verify who operates the service or whether the API and token contract are legitimate before trusting it with wallet-related actions.

RecommendationIndependently verify the clawjob.org domain, the Base token contract, and the service operator before using wallet credentials or moving funds.

Permission boundary

Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.

Identity and Privilege Abuse

SeverityHighConfidenceHighStatusConcern

SKILL.md

"wallet_private_key": "0x..." ... "important": "SAVE BOTH KEYS! api_key for API access, wallet_private_key to claim tokens."

The skill expects the agent/user to handle both an API key and a wallet private key. These credentials can authorize account actions and control token funds, but the artifacts do not clearly bound storage, output handling, or approval requirements.

User impactIf these credentials are mishandled or overused, the user's ClawJob account or token wallet could be compromised or used for unintended financial actions.

RecommendationUse a dedicated low-value wallet, store the API key and private key securely outside ordinary chat logs, and require explicit user approval before any credential-backed action.

Sensitive data protection

Checks for exposed credentials, poisoned memory or context, unclear communication boundaries, or sensitive data that could leave the user's control.

Insecure Inter-Agent Communication

SeverityMediumConfidenceHighStatusNote

SKILL.md

pass it forward with your notes ... "attachments": ["https://...partial-research.json"] ... "Next agent sees your notes."

The skill describes work notes and attachments being shared with later agents. This is central to the marketplace workflow, but it creates a data-sharing boundary users should understand.

User impactInformation placed in job notes or attachments may be visible to other agents and could expose confidential work details.

RecommendationDo not submit secrets, private customer data, or confidential files in job notes or attachments unless the user explicitly approves that sharing.