CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

salesforce

Query and manage Salesforce orgs via the official Salesforce MCP server or SF CLI.

55

Quality

69%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/salesforce/SKILL.md

The canonical home for this skill is salesforce in jdrhyne/agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a strong, highly executable reference for read-only Salesforce querying — real commands, seven working SOQL examples, and clear setup — but it under-delivers on its own architecture: the central referenced file is missing from the bundle, and placeholder customization content that should live there is inlined instead. Workflow guidance for the 'manage' half and query-failure handling is absent.

Suggestions

Include the referenced SALESFORCE_STRUCTURE.md (even as a starter template) in the bundle so the skill's primary reference is not broken.

Move the placeholder 'Key Concepts' sections and the Common Queries catalog into SALESFORCE_STRUCTURE.md / COMMON_QUERIES.md to slim SKILL.md to an actionable overview.

Add a short validation/feedback loop (e.g. what to do when a query errors or the org alias is unauthenticated) and either a concrete manage/DML workflow or drop the 'manage' claim from scope.

DimensionReasoningScore

Conciseness

The commands and queries are tight, but placeholder template sections ('Product A — Description', 'Update with your company's product lines') and the seven-query catalog duplicate content the skill itself delegates to SALESFORCE_STRUCTURE.md/COMMON_QUERIES.md. Mostly efficient with noticeable content that could be trimmed or moved, which is the anchor-3 fit rather than the level-4 'minor instances'.

3 / 5

Actionability

Fully executable, copy-paste-ready guidance: 'mcporter call salesforce.run_soql_query …', 'sf data query --query … --target-org my-prod', and seven complete SOQL queries (pipeline, renewals, ARR by account, account/contact lookups) that cover the common cases, plus a concrete MCP tool list. Matches the level-5 anchor.

5 / 5

Workflow Clarity

Setup is clearly sequenced (install CLI → 'sf org login web --alias my-prod' → optional MCP server) and the primary task (run a SOQL query) is unambiguous, with sensible tips. Not 5: no error-handling/feedback loop for failed queries or auth problems, and the claimed 'manage' side has no workflow at all — though the shown operations are read-only, so the destructive-op cap does not apply.

4 / 5

Progressive Disclosure

Section headers are good and references are only one level deep, but the primary referenced file './SALESFORCE_STRUCTURE.md' does not exist in the bundle (no references/ or sibling file), so the main reference is broken. Meanwhile org-specific catalog content that belongs in that file is inlined in the body — matching anchor 3 rather than 4's 'references mostly clear'.

3 / 5

Total

15

/

20

Passed

Description

53%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, names a distinct niche, and identifies the two access mechanisms, but it reads more like a label than a trigger: it lacks any 'use when' guidance and omits the natural vocabulary (SOQL, records, opportunities) users would actually say. It sits squarely at the anchor-3 level on three of four dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions Salesforce, SOQL, orgs, opportunities, or asks to query/manage CRM records.'

Enumerate concrete capabilities instead of the generic 'manage': e.g. 'run SOQL queries, list orgs, inspect opportunities and accounts' to lift specificity.

Include common synonyms such as 'SOQL', 'Salesforce CLI', and 'records' so the skill surfaces for natural user phrasings.

DimensionReasoningScore

Specificity

Names the domain ('Salesforce orgs') and two actions ('Query and manage') plus the two access tools ('official Salesforce MCP server or SF CLI'), but 'manage' is generic and the coverage is not comprehensive — no SOQL, records, or specific operations. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' rather than 4, which requires several specific actions.

3 / 5

Completeness

The 'what' is clear ('Query and manage Salesforce orgs via the official Salesforce MCP server or SF CLI') but there is no 'Use when...' clause or equivalent trigger guidance anywhere, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

'Salesforce', 'orgs', and 'SF CLI' are relevant keywords a user might say, but common natural variations are missing: 'SOQL', 'records', 'opportunities', 'query data', 'Salesforce CLI'. Some relevant keywords but missing common variations, so not the level-4 'good keyword coverage'.

3 / 5

Distinctiveness Conflict Risk

'Salesforce' names a clear niche and the MCP/SF CLI framing makes accidental triggering for other skills unlikely. It falls between anchors 4 and 5: the broad verb 'manage' leaves minor overlap risk with a closely related Salesforce-development skill, so 4 fits better than the level-5 'clear niche with distinct triggers'.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

bap-jorkim/agent-skills-fork-feb-25

Path

skills/salesforce/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.