ClawHub

Salesforce

v0.1.0

Search Salesforce records, inspect supported objects, query CRM data, and perform available actions for accounts, contacts, leads, opportunities, cases, and...

⭐ 0· 33·0 current·0 all-time
by@hith3sh·duplicate of @hith3sh/salesforce-tools

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for hith3sh/salesforce-ops.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Salesforce" (hith3sh/salesforce-ops) from ClawHub.
Skill page: https://clawhub.ai/hith3sh/salesforce-ops
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install salesforce-ops

ClawHub CLI

Package manager switcher

npx clawhub@latest install salesforce-ops
Security Scan
Capability signals
Requires sensitive credentials
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
Name and description match the instructions: the SKILL.md describes searching, inspecting, querying, and performing available Salesforce actions. No unexpected binaries, installs, or unrelated environment variables are requested. The absence of declared credentials is consistent with relying on an external connected Salesforce integration provided by the host platform.
✓
Instruction Scope
Runtime instructions constrain behavior to using the live connected Salesforce toolset, prefer reads before writes, require explicit user confirmation for writes, and explicitly forbid reading local files, secrets, or performing unrelated outbound calls. There is no scope creep in the prose.
✓
Install Mechanism
No install spec and no code files are present (instruction-only), which minimizes on-disk changes. This is proportionate for a wrapper/assistant skill that delegates to an existing integration.
✓
Credentials
The skill declares no required environment variables or credentials and the SKILL.md instructs not to ask the user for tokens or to use unofficial login flows. This is appropriate because authentication should be handled by the host platform's connected Salesforce integration.
✓
Persistence & Privilege
The skill does not request 'always' presence and uses default autonomous invocation capability (normal for skills). It does not instruct modifications to other skills or system-wide settings.
Assessment
This skill is instruction-only and appears coherent: it expects the host platform to provide a Salesforce connection rather than asking for credentials. Before installing, verify how your platform connects to Salesforce (OAuth scopes and permissions) and which actions (read/write/delete) will be allowed. Watch for any runtime prompts that ask you to paste tokens or share sensitive files—SKILL.md forbids that. Also confirm you understand and approve any write/delete operations before the skill performs them.

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

latestvk97e19wy9e2nb5a24f2ndbjf5h85p6z5
33downloads
0stars
1versions
Updated 9h ago
v0.1.0
MIT-0
@hith3sh
latest
Download

Salesforce

Work with Salesforce from chat to search records, inspect supported objects, query CRM data, and perform available actions when they are supported by the connected integration.

Overview

Use this skill for common Salesforce work such as:

  • finding contacts, leads, accounts, opportunities, or cases
  • searching records by name, email, company, or other supported fields
  • inspecting supported objects or available operations
  • checking what Salesforce actions are currently available
  • creating, updating, or deleting records when those actions are exposed and clearly requested

This skill should feel practical and trustworthy. Keep responses concrete, operational, and grounded in what is actually available.

How to work

Use this workflow:

  1. Identify the Salesforce task
  2. Check whether Salesforce is connected
  3. Check which Salesforce tools and actions are currently available
  4. Prefer read, search, query, and inspection actions before writes when they reduce ambiguity
  5. If a write is requested, state clearly what will change before doing it
  6. If multiple records may match, ask the user to disambiguate
  7. If the requested capability is not available, say so plainly

What this helps with

Examples:

  • find a Salesforce contact by email
  • search accounts by company name
  • inspect recent opportunities for a customer
  • look up open cases
  • identify supported object operations
  • create or update a record when the live tool set supports it
  • explain whether a requested Salesforce action is currently available

Connection

Before doing Salesforce work:

  • verify whether Salesforce is connected
  • if it is not connected, guide the user through the available connection flow
  • do not ask the user to paste raw access tokens, refresh tokens, session cookies, passwords, or private credentials into chat
  • do not use unofficial login, scraping, or harvested browser-session flows

Treat the current connection state and live tool catalog as authoritative.

Safety

Operate with a narrow scope:

  • use only the minimum inputs needed for the requested Salesforce task
  • do not access unrelated local files, secrets, environment variables, or configuration data
  • do not perform unrelated outbound calls
  • clearly disclose when an action will create, update, or delete Salesforce data
  • prefer the least risky action that still solves the request

Behavioral rules

Follow these rules every time:

  • use the live Salesforce tool set as the source of truth
  • do not claim full Salesforce coverage
  • do not fabricate unsupported objects, fields, or actions
  • do not imply write support just because read support exists
  • ask clarifying questions when the intended record or action is ambiguous
  • summarize risky or destructive changes before performing them

Example requests

  • Find this contact in Salesforce
  • Search Salesforce for Acme opportunities
  • Show recent open Salesforce cases
  • Look up this lead by email in Salesforce
  • Tell me what Salesforce tools are available
  • Inspect supported Salesforce object operations
  • Update this Salesforce record if supported
  • Create a new Salesforce record
  • Delete this Salesforce item if supported and explicitly requested

Limits

Actual capability depends on:

  • whether the user's Salesforce account is connected
  • which Salesforce actions are currently exposed by the connected tool set
  • the permissions and scopes granted by the connected Salesforce account

If an action is unavailable, say so plainly. Do not pretend the skill can do it anyway.

Response style

Be clear and operational:

  • say what was found
  • say what is supported
  • say when Salesforce must be connected first
  • say when an action will write data
  • say when a capability is unavailable

Keep answers useful, direct, and easy to audit.

Resources

Comments

Loading comments...