CtrlK
BlogDocsLog inGet started
Tessl Logo

salesforce

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.

58

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The skill is highly actionable with concrete executable commands and a clear safety/guardrail framing, but its monolithic length works against conciseness and progressive disclosure, and destructive/batch workflows lack explicit validation checkpoints.

Suggestions

Add explicit validation/confirmation checkpoints to destructive and batch workflows (e.g. dry-run describe → user confirm → execute → verify result) to lift workflow clarity.

Split the exhaustive command catalogs (REST API, metadata deployment, bulk tree import) into reference files and link to them from a leaner SKILL.md overview to improve both conciseness and progressive disclosure.

DimensionReasoningScore

Conciseness

The body is mostly efficient copy-paste commands with light comments and avoids explaining concepts Claude already knows, but it runs ~370 lines of fairly exhaustive CLI examples that exceed what a lean overview needs and could be tightened or moved to references.

2 / 3

Actionability

Nearly every section gives concrete, executable `sf` commands with real flags and realistic example values, organized by task — copy-paste ready with no pseudocode.

3 / 3

Workflow Clarity

Sequencing for setup (install → login → query) is clear and Guardrails add validation, but destructive/batch operations (delete, bulk delete, bulk import, deploy) lack explicit validate→confirm→execute checkpoints with error-recovery loops, so the workflow cannot reach 3.

2 / 3

Progressive Disclosure

Content is well-sectioned, but it is a single monolithic SKILL.md with no bundle files and no one-level-deep references; much of the exhaustive command catalog (REST API, metadata deploy, tree import) could be split into reference files.

2 / 3

Total

9

/

12

Passed

Description

72%

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 highly specific and occupies a clear, distinctive niche, but it omits an explicit 'Use when...' trigger clause and leans on domain jargon, which leaves completeness and trigger-term naturalness just short of full marks.

Suggestions

Append an explicit 'Use when...' trigger clause, e.g. 'Use when querying or modifying Salesforce CRM data, managing records in bulk, or deploying metadata to a Salesforce org.'

Add natural user-facing phrasing alongside the technical terms (e.g. 'query Salesforce', 'export records', 'search Salesforce data') to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Lists many concrete actions: 'Run SOQL/SOSL queries', 'inspect object schemas', 'create/update/delete records', 'bulk import/export', 'execute Apex', 'deploy metadata', and 'raw REST API calls' — a comprehensive, specific action set.

3 / 3

Completeness

It clearly answers 'what does this do' with a thorough capability list, but there is no explicit 'Use when...' clause or trigger guidance, so the 'when should Claude use it' half is only implied — capping completeness at 2 per the rubric.

2 / 3

Trigger Term Quality

It names Salesforce/SOQL/SOSL/Apex which users of the domain would say, but lacks the common natural variations a user might phrase ('query Salesforce', 'export records', 'Salesforce data') and leans on technical jargon over everyday trigger phrasing.

2 / 3

Distinctiveness Conflict Risk

The Salesforce CRM / sf CLI niche is sharply defined with distinct triggers (SOQL, SOSL, Apex, metadata deploy) and is unlikely to overlap with or mis-trigger other skills.

3 / 3

Total

10

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

13

/

16

Passed

Repository
jdrhyne/agent-skills
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.