Generated
Validation
Total
12/16Score
Passed| Criteria | Score |
|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') |
metadata_version | 'metadata' field is not a dictionary |
license_field | 'license' field is missing |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs |
Implementation
Suggestions 3
Score
73%Overall Assessment
This skill provides strong actionable content with executable queries and commands, and good progressive disclosure structure. However, it's somewhat verbose with template placeholders and explanatory content that assumes less of Claude's knowledge. The setup workflow lacks validation steps to confirm successful org connection.
Suggestions
| Dimension | Score | Reasoning |
|---|---|---|
Conciseness | 2/3 | The skill includes some unnecessary explanatory content (e.g., explaining what ACV/ARR/TCV mean, generic record type descriptions) that Claude would already know. The template placeholders and tips sections add bulk that could be trimmed. |
Actionability | 3/3 | Provides fully executable SOQL queries, concrete CLI commands, and copy-paste ready MCP tool invocations. The examples are specific and immediately usable. |
Workflow Clarity | 2/3 | Setup steps are listed but lack validation checkpoints. No guidance on verifying org connection succeeded, no error handling for failed queries, and no feedback loop for troubleshooting authentication issues. |
Progressive Disclosure | 3/3 | Well-structured with clear sections and appropriate references to external files (SALESFORCE_STRUCTURE.md, BUSINESS_LOGIC.md, COMMON_QUERIES.md). Navigation is clear and references are one level deep. |
Activation
Suggestions 3
Score
33%Overall Assessment
The description identifies the Salesforce domain and mentions specific tools (MCP server, SF CLI), which provides some clarity. However, it lacks concrete action examples, natural trigger terms users would say, and critically missing explicit 'Use when...' guidance that would help Claude select this skill appropriately.
Suggestions
| Dimension | Score | Reasoning |
|---|---|---|
Specificity | 2/3 | Names the domain (Salesforce) and mentions two tools (MCP server, SF CLI), but 'query and manage' are fairly generic actions without listing specific concrete capabilities like 'run SOQL queries, deploy metadata, manage users'. |
Completeness | 1/3 | Describes what it does (query and manage Salesforce orgs) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. |
Trigger Term Quality | 2/3 | Includes 'Salesforce', 'orgs', 'MCP server', and 'SF CLI' which are relevant keywords, but misses common user terms like 'SOQL', 'Apex', 'sfdx', 'CRM', or 'Salesforce data'. |
Distinctiveness Conflict Risk | 2/3 | Salesforce-specific focus provides some distinctiveness, but 'query and manage' is vague enough that it could overlap with generic database or CRM skills without clearer boundaries. |
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.