ClawHub
Skill flagged — suspicious patterns detected

ClawHub Security flagged this skill as suspicious. Review the scan results before using.

Salesforce Skill

v1.0.0

Query and manage Salesforce CRM data via the Salesforce CLI (`sf`). Run SOQL/SOSL queries, inspect object schemas, create/update/delete records, bulk import/export, execute Apex, deploy metadata, and make raw REST API calls.

⭐ 0· 2.6k·7 current·10 all-time
by@arvorco
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Suspicious
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name and description describe Salesforce CLI operations; the skill requires the 'sf' binary and provides an npm install for @salesforce/cli which legitimately supplies that binary. No unrelated binaries, env vars, or config paths are requested.
ℹ
Instruction Scope
SKILL.md contains detailed sf CLI commands for queries, record create/update/delete, Apex execution, metadata deploys, and multiple authentication flows. These instructions are within the skill's stated scope. They explicitly reference sensitive actions and outputs (access tokens, refresh tokens, JWT key files) and correctly note that authentication is required and that some commands reveal sensitive info. The agent will be able to run commands that read local auth files (e.g., server.key, authUrl.txt) and display tokens — this is expected behavior but important for users to know.
✓
Install Mechanism
Install uses the official-looking npm package @salesforce/cli to provide the 'sf' binary, and the README also points to developer.salesforce.com. Installing via npm is a standard, reasonable approach. Note: a global npm install may require elevated permissions and runs package postinstall scripts like any npm package.
ℹ
Credentials
The skill declares no required environment variables or config paths, which is consistent because authentication is performed via the CLI at runtime. However, the instructions reference local credential artifacts (JWT key files, sfdx auth URL files) and commands that surface tokens; those are sensitive but appropriate for a Salesforce CLI integration. Users should be aware the agent will be able to access any credential files it is directed to use.
✓
Persistence & Privilege
always:false and user-invocable:true (with normal autonomous invocation allowed) — typical and appropriate. The skill does not request system-wide persistence or modification of other skills. Caution: if the agent is granted Salesforce credentials, autonomous invocation could allow it to perform destructive changes in the org; that is an operational risk, not an incoherence.
Assessment
This skill appears to be what it says: a wrapper around the Salesforce CLI. Before installing, consider: 1) The CLI will require you to authenticate to a Salesforce org; those credentials (access tokens, refresh tokens, JWT key files, sfdx auth URLs) are sensitive — avoid exposing them to an agent you don't trust. 2) The skill can run destructive operations (create/update/delete, deploy, execute Apex). Only enable autonomous invocation if you want the agent to act on your org without manual approval. 3) Installing @salesforce/cli via npm may require elevated privileges and will run normal npm install scripts — if you prefer, install the official CLI yourself from developer.salesforce.com and keep credential files under your control. 4) If you need higher assurance, verify the npm package source and ownership before installing and prefer interactive (web) login flows over embedding keys in files where possible.

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

latestvk97a68g4c3ykt7afs4hqf77t41800857

License

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

Runtime requirements

☁️ Clawdis
Binssf

Install

Install Salesforce CLI (npm)
Bins: sf
npm i -g @salesforce/cli

Comments