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.
68
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
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 lists specific Salesforce development capabilities, includes abundant natural trigger terms that developers would use, and provides explicit 'Use when' guidance. It is highly distinctive due to its Salesforce-specific terminology and covers both the 'what' and 'when' dimensions thoroughly.
| 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 user would say: 'Apex', 'Lightning Web Components', 'SOQL', 'Salesforce', 'triggers', 'batch jobs', 'governor limits', 'Salesforce DX', 'CI/CD', 'CRM workflows'. These are all terms developers naturally use when seeking Salesforce help. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Salesforce-specific terminology (Apex, LWC, SOQL, governor limits, Salesforce DX) that clearly carves out a niche. Unlikely to conflict with general coding or other platform-specific skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%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, actionable Salesforce development skill with excellent executable code patterns covering the most critical areas (bulkification, batch Apex, testing, SOQL). Its main weaknesses are the lack of concrete validation/verification steps in the workflow (how exactly to check governor limits), missing bundle reference files that the skill explicitly points to, and some inline content that could be delegated to those reference files for better progressive disclosure.
Suggestions
Add concrete governor limit validation steps to the workflow, e.g., using `Limits.getQueries()`, `Limits.getDMLStatements()`, or checking debug logs in Developer Console, with a fix-and-retry feedback loop.
Create the five referenced files (apex-development.md, lightning-web-components.md, etc.) and move detailed code patterns into them, keeping only the bulkified trigger as the primary inline example.
Replace the trivial counter LWC example with a more Salesforce-specific pattern (e.g., wire service calling an Apex method with error handling) that demonstrates platform-specific knowledge Claude wouldn't already have.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some content that could be tightened. The counter LWC example is trivial and doesn't teach Salesforce-specific patterns (wire service, imperative Apex calls). The incorrect trigger example, while useful for contrast, adds bulk. The MUST DO/MUST NOT lists are concise and valuable. | 2 / 3 |
Actionability | 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, annotations, and execution commands (e.g., `Database.executeBatch(new ContactBatchUpdate(), 200)`). | 3 / 3 |
Workflow Clarity | The core workflow lists 6 steps with a validation checkpoint at step 4 (governor limits), but the validation step is vague — it doesn't specify how to verify limits (e.g., `Limits.getQueries()`, debug logs, Developer Console). There's no explicit feedback loop for what to do when governor limits are exceeded, and deployment validation steps are missing. | 2 / 3 |
Progressive Disclosure | The reference table with 'Load When' guidance is well-structured and clearly signaled, but no bundle files were provided, meaning all five referenced files (`references/apex-development.md`, etc.) are missing. The main SKILL.md also inlines substantial code examples that overlap with what the reference files would presumably cover, creating redundancy. | 2 / 3 |
Total | 9 / 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
e8be415
- 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.