SKILLEMALL.ai

AC salesforce-crm

Complete Salesforce CRM integration for real-time data access, lead management, opportunity tracking, duplicate detection, and bulk operations. One-click OAuth connection with fast, reliable API access.

ClawHub Agent Skills author: Sawera Khadium v1.0.17 MIT-0 12 files body ≈ 4 638 tokens Open the sourceclawhub.ai analyzed 4 d ago

As a process C 53/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency

IntegrationSalesforceSales and CRMtype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
99
Quality 40%
82
Run on models
none yet
Process rating
C
53/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Running it twice w 4
30
the three weakest of ten parameters · all ten

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 1

    ✓ No critical or high findings

    Medium and low: 1
    • low Exfiltration read-dotenv SKILL.md:520
      Reads a .env file
      #    Copy .env.example to .env and fill in your values — see README for details.

    Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    • note frontmatter-key unknown frontmatter key "requires"

    Process rating: all ten parameters 53/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 30Running it twice. 36 mutating operations with no state check
    • 40Consistency. Frontmatter name (salesforce-crm) differs from the folder (salesforce-easy)
    • 60Tools and files. Uses tools (web) that frontmatter does not declare
    • 70When it triggers. States when to use, but not when not to
    • 70Execution cost. Instruction body is 4638 tokens
    • 85Steps. 210 steps, 1 vague phrases
    • 100Failures and branches. 1 branches, has a failure section
    • 100Progress reporting. Reports progress
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
    • low 17 top-level sections: this looks like several domains in one skill

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • -214 emoji in the instructions: noise for the model
    • +2Single-language instructions
    • +3Description length 202: enough signal without eating the budget
    • +4Structure: 60 headings
    • +3Step-by-step instructions: 210 items
    • +4Has examples (22 code blocks)
    • +1License stated

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 82.

    External checks

    ClawHub: suspicious
    This Salesforce skill mostly matches its CRM purpose, but it also has high-impact Salesforce write and automation powers with incomplete safeguards and some overstated safety claims.
    LLM: suspicious (high) · VirusTotal: · 29 May 2026