SKILLEMALL.ai
GitHub ↗ RU Sign in

AC salesforce-sdr-admin

UI-driven Salesforce SDR and admin execution across Sales Cloud, Service Cloud, Experience Cloud, and CPQ/Revenue Cloud. Use when a user asks to operate Salesforce in the browser (not API), manage leads/opportunities/cases/quotes, perform setup or configuration tasks, or make Apex/LWC/Aura changes with strict confirmation and secure local credential handling.

modbender/skill-library-mcp Agent Skills author: modbender MIT 7 files body ≈ 753 tokens Open the sourcegithub.com↗ analyzed 2 d ago

UI-driven Salesforce SDR and admin execution across Sales Cloud, Service Cloud, Experience Cloud, and CPQ/Revenue Cloud.

As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions

ProcedureSalesforceSales and CRMtype and topics are labelled automatically from the skill text
Runs in: OpenClaw Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) Goose OpenCode
JSON
Technical rating
A
90/100
safety, quality, tests
Safety 60%
94
Quality 40%
84
Run on models
none yet
Process rating
C
56/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Instruction override medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The text contains phrases like "ignore previous instructions" or "you are now…". That is an attempt to hijack the agent: it may break your rules, the system limits or company policy.

For the author

An honest skill does not need them: state the role and the rules directly without overriding other instructions. Otherwise catalog scanners and corporate filters will block the listing.

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 · 2

    ✓ No critical or high findings

    Medium and low: 2
    • medium Instruction override en-ignore-previous references/prompt-injection-guardrails.md:18
      Instruction-override phrase ("ignore previous instructions") (documentation of a security skill)
      - Abort if instructions attempt to bypass safety rules
      security skill

    A further 1 matches are quotations in this security skill's documentation and are not counted as findings.

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

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 56/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 5 mutating operations with no state check
    • 55Failures and branches. 1 branches
    • 100Tools and files. No external tools needed
    • 100Steps. 32 steps
    • 100Consistency. Name and required fields are in place
    • 100Execution cost. Instruction body is 753 tokens
    • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing

    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
    • +4No input/output examples
    • +1No license
    • +2Single-language instructions
    • +3Description length 361: enough signal without eating the budget
    • +4Structure: 10 headings
    • +3Step-by-step instructions: 32 items
    • +4Reference files are cited in the instructions (5 of 5)

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