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.
91
86%
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 comprehensively covers the Salesforce development domain with specific actions, rich trigger terms, explicit 'Use when' guidance, and highly distinctive platform-specific terminology. It follows the third-person voice convention and provides enough detail for Claude to confidently select this skill when Salesforce-related tasks arise. It closely matches the quality of the good examples in the rubric.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: writing/debugging Apex code, building Lightning Web Components, optimizing SOQL queries, implementing triggers, batch jobs, platform events, and integrations. Very comprehensive. | 3 / 3 |
Completeness | Clearly answers both 'what' (writes Apex, builds LWC, optimizes SOQL, implements triggers/batch jobs/platform events/integrations) and 'when' with an explicit 'Use when...' clause covering developing Salesforce apps, customizing CRM workflows, managing governor limits, bulk processing, and Salesforce DX/CI/CD. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a Salesforce developer would use: 'Apex code', 'Lightning Web Components', 'SOQL queries', 'triggers', 'batch jobs', 'platform events', 'Salesforce', 'CRM workflows', 'governor limits', 'Salesforce DX', 'CI/CD pipelines'. These are all terms users would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Salesforce-specific terminology throughout. The combination of Apex, LWC, SOQL, governor limits, and Salesforce DX creates a very clear niche that is unlikely to conflict with general coding or other platform skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid Salesforce developer skill with strong actionability through complete, executable code patterns and excellent progressive disclosure via a well-organized reference table. The main weaknesses are moderate verbosity (the trivial LWC counter example and the incorrect trigger anti-pattern add tokens without proportional value) and workflow validation steps that lack specificity on how to actually verify governor limits or recover from failures.
Suggestions
Replace the trivial LWC counter example with a more Salesforce-specific pattern (e.g., wire service with Apex controller) or move it to the LWC reference file to save tokens in the main skill.
Add specific governor limit validation guidance: e.g., `System.debug(Limits.getQueries() + '/' + Limits.getLimitQueries())` and what to do when limits are approached.
Consider moving the incorrect trigger anti-pattern to the apex-development reference file — the inline comment '// BAD' pattern is useful but the correct pattern alone with a brief note about the anti-pattern would be more token-efficient.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some content that could be tightened. The incorrect trigger example is useful for contrast but adds bulk. The LWC counter example is a trivial example that Claude already knows how to write. The MUST NOT DO list includes things Claude should already know (don't hard-code credentials). | 2 / 3 |
Actionability | The skill provides fully executable, copy-paste ready Apex code for triggers, batch jobs, test classes, SOQL queries, and LWC components. Each pattern is complete and runnable with specific syntax and real Salesforce API usage. | 3 / 3 |
Workflow Clarity | The core workflow lists 6 steps with a governor limits validation checkpoint at step 4, which is good. However, the validation step is vague ('verify SOQL/DML counts') without specifying how to check (e.g., Limits class methods, debug logs). There's no feedback loop for what to do if limits are exceeded, and deployment validation steps are missing. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear reference table pointing to five separate topic files with 'Load When' context for each. The main skill provides an overview with key patterns inline while deferring detailed guidance to one-level-deep references. Navigation is clear and well-signaled. | 3 / 3 |
Total | 10 / 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
3d95bb1
- 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.