CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

salesforce-automation

Automate Salesforce tasks via Rube MCP (Composio): leads, contacts, accounts, opportunities, SOQL queries. Always search tools first for current schemas.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/salesforce-automation/SKILL.md

The canonical home for this skill is salesforce-automation in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

61%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.

A well-structured, mostly lean instruction skill with concrete tool names, parameters, and executable SOQL examples. Its main weaknesses are structural redundancy (the quick-reference table and filler 'When to Use' section) and the absence of validation/verification steps around destructive and batch operations, which caps workflow clarity at 3.

Suggestions

Add explicit validation checkpoints to destructive and batch workflows — e.g., after SALESFORCE_MASS_TRANSFER_OWNERSHIP or SALESFORCE_UPDATE_LEAD, verify the result (query the record back via SOQL) before reporting success, and gate mass transfer on confirming the record list and new owner with the user.

Trim redundancy: either cut the 20-row Quick Reference table (it duplicates tool slugs already listed per-workflow) or compress the workflow tool sequences and keep the table as the single lookup, and delete the vacuous 'When to Use' sentence at the end.

Show one complete representative tool invocation (e.g., a SALESFORCE_CREATE_LEAD call with LastName/Company arguments) so the parameter guidance is fully copy-paste ready, and replace the uniform '[Optional]' tags with guidance on when each tool actually applies.

DimensionReasoningScore

Conciseness

The body is mostly efficient (tool sequences, key parameters, pitfalls, executable SOQL snippets) with no conceptual padding, but the 20-row "Quick Reference" table largely duplicates the tool slugs already enumerated in the workflow sections, and the closing "This skill is applicable to execute the workflow or actions described in the overview" sentence is pure filler. These are more than minor trimmings, matching the 'mostly efficient but could be tightened' anchor rather than the lean anchor at 5 or the 'minor instances' anchor at 4.

3 / 5

Actionability

Concrete tool slugs (e.g. 'SALESFORCE_CREATE_LEAD - Create a new lead'), specific parameter names ('LastName: Required for lead creation', 'Name, StageName, and CloseDate are required for creation'), and copy-paste-ready SOQL ('SELECT Id, Name, Email FROM Contact WHERE LastName = \'Smith\'') give mostly executable guidance. Falls short of 5 because no complete example of an actual tool invocation (e.g., a representative call with arguments) is shown, and every workflow step is tagged '[Optional]' without saying when each applies.

4 / 5

Workflow Clarity

The Setup section has an explicit checkpoint ('Confirm connection status shows ACTIVE before running any workflows') and pagination guidance checks the 'done' field, but the core CRUD workflows and the destructive/batch operations ('SALESFORCE_MASS_TRANSFER_OWNERSHIP', lead/contact updates) include no validation or verification steps (e.g., confirm a record was created before proceeding). Per the rubric, missing validation in destructive/batch workflows caps this at 3 — a clear sequence exists, but checkpoints are absent where they matter most.

3 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, assets/), and the single SKILL.md is well-organized with clear section headers (Prerequisites, Setup, five numbered workflows, Common Patterns, Quick Reference) that make it easy to navigate. Scored 4 rather than 5 because at ~185 lines the large Quick Reference table is borderline content that could live in a separate reference file, and the vestigial 'When to Use' section adds no navigation value.

4 / 5

Total

14

/

20

Passed

Description

66%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.

A specific, well-keyed description that clearly states what the skill does and which Salesforce objects it covers, written in appropriate third-person voice. Its one structural gap is the absence of any 'Use when...' trigger guidance, which caps completeness at 3 despite otherwise strong specificity and distinctiveness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user mentions Salesforce, CRM records, leads, opportunities, or asks to run SOQL queries.'

Name the concrete actions per object (create, search, update, link) rather than the generic 'Automate Salesforce tasks' to lift specificity toward comprehensive.

Include common synonyms such as 'CRM' and 'Salesforce records' so natural user phrasings beyond the exact product name also match.

DimensionReasoningScore

Specificity

The description lists several concrete capability areas — 'leads, contacts, accounts, opportunities, SOQL queries' — plus the specific integration path 'via Rube MCP (Composio)'. It falls short of the 5 anchor because the governing verb 'Automate Salesforce tasks' is generic: the per-object actions (create, search, update) are never named, so coverage of concrete actions has minor gaps.

4 / 5

Completeness

The 'what' is clear (automate Salesforce objects and SOQL via Rube MCP), but there is no 'Use when...' clause or equivalent trigger guidance anywhere; the trailing sentence 'Always search tools first for current schemas' is procedural instruction, not a when-clause. Per the judging guidelines, a missing 'Use when...' clause caps completeness at 3, and the anchor 'has a clear what but when is missing' fits exactly.

3 / 5

Trigger Term Quality

Good keyword coverage: 'Salesforce', 'leads', 'contacts', 'accounts', 'opportunities', 'SOQL' are all natural terms a user working in this domain would say. A few natural terms are missing — 'CRM', 'records', 'pipeline', 'notes/tasks' — so it does not reach the comprehensive-with-synonyms level of the 5 anchor.

4 / 5

Distinctiveness Conflict Risk

The pairing of 'Salesforce' with 'Rube MCP (Composio)' carves a distinct niche — only another Salesforce skill (e.g., one using the direct Salesforce API) could overlap, and the explicit MCP naming mostly disambiguates that. Minor overlap risk with closely related skills keeps it at the 4 anchor rather than the minimal-conflict 5 anchor.

4 / 5

Total

15

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/salesforce-automation/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.