salesforce-developer
Writes and debugs Apex code, builds Lightning Web Components, optimizes SOQL queries, implements triggers, batch jobs, platform events, and integrations on the Salesforce platform. Use when developing Salesforce applications, customizing CRM workflows, managing governor limits, bulk processing, or setting up Salesforce DX and CI/CD pipelines.
96
100%
Does it follow best practices?
Impact
93%
1.06xAverage score across 6 eval scenarios
Advisory
Suggest reviewing before use
Quality
Discovery
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.
This is an excellent skill description that follows best practices. It provides comprehensive, specific capabilities using third-person voice, includes a well-structured 'Use when...' clause with multiple trigger scenarios, and uses domain-specific terminology that makes it highly distinctive and easy for Claude to select appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Writes and debugs Apex code, builds Lightning Web Components, optimizes SOQL queries, implements triggers, batch jobs, platform events, and integrations.' These are all concrete, actionable capabilities. | 3 / 3 |
Completeness | Clearly answers both what (writes Apex, builds LWC, optimizes SOQL, etc.) AND when with explicit 'Use when...' clause covering multiple trigger scenarios: developing Salesforce applications, customizing CRM workflows, managing governor limits, bulk processing, or setting up Salesforce DX. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Apex code', 'Lightning Web Components', 'SOQL queries', 'triggers', 'batch jobs', 'Salesforce', 'CRM', 'governor limits', 'Salesforce DX', 'CI/CD pipelines'. These are terms developers naturally use when working with Salesforce. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Salesforce-specific terminology (Apex, LWC, SOQL, governor limits, Salesforce DX) that clearly distinguishes it from general coding or other CRM skills. Unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that demonstrates excellent structure and actionability. It provides concrete, executable code patterns for all major Salesforce development scenarios, includes explicit validation checkpoints for governor limits, and uses progressive disclosure effectively with a well-organized reference table. The MUST DO/MUST NOT DO constraints are specific and platform-appropriate.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, avoiding explanations of basic concepts Claude already knows. Every section provides actionable information without padding or unnecessary context about what Salesforce is or how CRM systems work. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples for all major patterns including bulkified triggers, batch Apex, test classes, SOQL queries, and LWC components. The correct vs incorrect trigger pattern comparison is particularly valuable. | 3 / 3 |
Workflow Clarity | The 6-step core workflow is clearly sequenced with an explicit validation checkpoint (step 4: 'Validate governor limits'). The workflow includes specific criteria for proceeding and the test step explicitly mentions bulk scenarios with concrete numbers (200-record batches). | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear reference table pointing to one-level-deep topic files with explicit 'Load When' guidance. The main skill provides essential patterns inline while deferring detailed guidance to appropriate reference files. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- jeffallan/claude-skills
- Commit
5b76101
- 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.