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.

Quality

81%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

80%

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

A highly actionable, token-efficient CLI reference with strong safety guardrails, weakened by missing validation feedback loops for batch/destructive work and a monolithic structure with no progressive disclosure.

Suggestions

Add explicit validation checkpoints for risky workflows, e.g. after a deploy run 'sf project deploy report' and only proceed on success; after bulk import, query row counts to verify before declaring done.

Split the long reference into one-level-deep bundle files (e.g. references/soql-patterns.md, references/bulk-api.md, references/rest.md) referenced from SKILL.md so the main file stays an overview.

Add a short ordered 'first run' workflow (check `sf` present → authenticate → set target-org → query) so the entry sequence is explicit rather than implied across sections.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely lean, copy-pasteable `sf` commands with terse comments and no padding or explanation of concepts Claude already knows; every token earns its place.	3 / 3
Actionability	Commands are fully executable and specific (e.g. 'sf data query --query "SELECT Id, Name FROM Contact LIMIT 10" --json'), with concrete flag examples across query, bulk, Apex, and REST sections.	3 / 3
Workflow Clarity	Sequencing exists (authenticate before touching data; confirm before destructive ops) and guardrails are present, but batch/destructive operations lack explicit validate-then-fix-then-retry feedback loops, capping workflow clarity at 2.	2 / 3
Progressive Disclosure	The skill is a single ~375-line monolithic file with no bundle files in references/scripts/assets; well-sectioned but content that could live in separate references (SOQL patterns, REST, Apex) is all inline.	2 / 3
	Total	10 / 12 Passed

Description

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.

A specific, well-scoped description with strong trigger terms and low conflict risk, held back only by the absence of an explicit 'when to use' trigger clause.

Suggestions

Append a 'Use when...' clause naming natural triggers, e.g. 'Use when the user asks to query Salesforce, run SOQL/SOSL, manage CRM records, or deploy Apex/metadata.'

Mirror common phrasings users actually say (e.g. 'find records in Salesforce', 'pull a report from an org') to strengthen trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions — 'Run SOQL/SOSL queries, inspect object schemas, create/update/delete records, bulk import/export, execute Apex, deploy metadata, and make raw REST API calls' — rather than vague language.	3 / 3
Completeness	Clearly answers 'what' but lacks any 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 2 per the rubric guidelines.	2 / 3
Trigger Term Quality	Covers natural Salesforce terms a user would say — 'Salesforce CRM data', 'SOQL/SOSL', 'records', 'bulk import/export', 'Apex', 'metadata', 'REST API'.	3 / 3
Distinctiveness Conflict Risk	The Salesforce CRM / `sf` CLI niche is sharply defined with distinct triggers, making it unlikely to fire for an unrelated skill.	3 / 3
	Total	11 / 12 Passed

Validation

81%

Warnings & errors only

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

Validation — 13 / 16 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	13 / 16 Passed

Repository: jdrhyne/agent-skills
Commit: a4d31ad

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.