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.
76
73%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/salesforce/SKILL.mdQuality
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong description with excellent specificity and distinctiveness, listing numerous concrete Salesforce-specific actions and using domain-appropriate trigger terms. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill over others.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks about Salesforce, CRM data, SOQL queries, Apex execution, or Salesforce CLI operations.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: SOQL/SOSL queries, inspect object schemas, create/update/delete records, bulk import/export, execute Apex, deploy metadata, and raw REST API calls. | 3 / 3 |
Completeness | Clearly answers 'what does this do' with a comprehensive list of capabilities, but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this dimension at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'Salesforce', 'CRM', 'SOQL', 'SOSL', 'Apex', 'metadata', 'REST API', 'bulk import/export', 'sf' CLI. These cover both high-level and technical terms a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Salesforce-specific terminology (SOQL, SOSL, Apex, Salesforce CLI `sf`). Very unlikely to conflict with other skills due to the clear Salesforce CRM niche. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a thorough, highly actionable reference for Salesforce CLI operations with excellent command coverage and concrete examples. Its main weaknesses are its length (could benefit from splitting into sub-files with a concise overview), some redundancy between sections, and the lack of explicit multi-step workflow sequences with validation checkpoints for destructive operations like bulk deletes and deployments.
Suggestions
Split the content into a concise SKILL.md overview with links to separate reference files (e.g., BULK_OPERATIONS.md, REST_API.md, METADATA.md) to improve progressive disclosure and reduce the main file's token footprint.
Add explicit multi-step workflow sequences with validation checkpoints for destructive operations—e.g., for bulk delete: 1) preview query with LIMIT, 2) confirm with user, 3) execute, 4) verify results with a follow-up query.
Remove the duplicate bulk export examples that appear in both the 'Querying Data' and 'Bulk Data Operations' sections to improve conciseness.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but quite long (~300+ lines). While most content is actionable commands rather than explanatory prose, there's significant redundancy—bulk export examples appear in both the 'Querying Data' section and the 'Bulk Data Operations' section. Some commands are shown with minor variations that could be consolidated. However, it avoids explaining what Salesforce or SOQL is, which is good. | 2 / 3 |
Actionability | Nearly every section provides copy-paste ready CLI commands with realistic arguments and flags. The SOQL patterns section provides concrete SQL examples, and all operations include the `--json` flag as recommended. Commands cover the full spectrum from authentication to CRUD to bulk operations with specific syntax. | 3 / 3 |
Workflow Clarity | While individual commands are clear, multi-step workflows lack explicit sequencing and validation checkpoints. For example, the deployment workflow doesn't show a validate-then-deploy sequence, and bulk operations don't include steps to verify results after import/delete. The safety guardrails section mentions confirmation requirements but doesn't embed them as workflow steps within the destructive operation sections. | 2 / 3 |
Progressive Disclosure | The content is a monolithic document with good section headers but no references to external files for detailed topics. The schema inspection, REST API, and metadata deployment sections could each be separate reference files linked from a concise overview. For a skill this long, the lack of any file splitting or layered navigation is a weakness. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
6768672
Table of Contents
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.