CtrlK
BlogDocsLog inGet started
Tessl Logo

salesforce

Use when a focused Sales workflow needs Salesforce-backed CRM reads, links, drafts, notes, account plans, Agentforce assignments, or explicitly requested Salesforce connector/query guidance. Do not use for generic CRM app construction or when another CRM is authoritative.

72

Quality

88%

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

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

A dense, highly actionable operational guide with clear sequenced workflows and write-validation checkpoints. Its main weaknesses are recurring redundancy across sections and a monolithic structure with no reference files for the connector and output-format material.

Suggestions

De-duplicate the repeated "Salesforce-backed reads, links, account plans, assignments, transcript summaries, and writes" enumeration and consolidate write-safety rules into one section to tighten conciseness.

Fix the stray "~~" strikethrough marker on the CRM bullet (line 31).

Extract the connector operation list and the four output-format templates into reference files (e.g. references/connector-operations.md, references/output-formats.md) with one-level-deep links from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

It assumes Claude's competence (no explanation of Salesforce/SOQL/CRM basics), but the Salesforce-backed-reads enumeration and write-safety rules recur across several sections and line 31 has a stray "~~" typo, so it could be tightened.

2 / 3

Actionability

Names exact connector operations (get_record_id_by_name, soql_query, create_record, etc.) with concrete directives such as "Use get_user_info for my, me, or current-owner requests" and "send only changed fields" — specific and directly applicable.

3 / 3

Workflow Clarity

A numbered 1–3 workflow (clarify → first draft → approved action) with explicit validation checkpoints ("verify with a narrow read when the response does not prove the outcome") and feedback loops for the write context.

3 / 3

Progressive Disclosure

No bundle files exist and the ~200-line body keeps connector operation lists and four output-format templates inline that could be split into references; sections are well-organized but content that should be separate stays in one file.

2 / 3

Total

10

/

12

Passed

Description

100%

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 strong, specific description with explicit positive triggers, a concrete action list, and a negative boundary that sharply limits conflict risk. It answers what, when, and when-not concisely.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "CRM reads, links, drafts, notes, account plans, Agentforce assignments...connector/query guidance" — rather than naming only the domain.

3 / 3

Completeness

Explicit "Use when..." trigger answers when, the action list answers what, and a "Do not use for..." clause adds a negative boundary — both clearly present.

3 / 3

Trigger Term Quality

Includes natural terms a user would say ("Salesforce-backed CRM reads", "links", "drafts", "notes", "account plans", "Agentforce assignments") with good coverage.

3 / 3

Distinctiveness Conflict Risk

Scoped to Salesforce within a Sales workflow with an explicit exclusion ("Do not use...when another CRM is authoritative"), giving a clear niche unlikely to conflict.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 8 suspicious

Warning

Total

15

/

16

Passed

Repository
XiaomiMiMo/MiMo-Code
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.