salesforce-developer
Use when developing Salesforce applications, Apex code, Lightning Web Components, SOQL queries, triggers, integrations, or CRM customizations. Invoke for governor limits, bulk processing, platform events, Salesforce DX.
Install with Tessl CLI
npx tessl i github:jeffallan/claude-skills --skill salesforce-developerOverall
score
61%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
72%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
The description excels at trigger term coverage and distinctiveness with comprehensive Salesforce-specific terminology, making it easy to identify when this skill should be selected. However, it lacks specificity about what actions the skill actually performs - it reads more like a list of topics than a description of capabilities. Adding concrete verbs describing what the skill does (e.g., 'write', 'debug', 'optimize', 'review') would significantly improve it.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Develops, debugs, and optimizes Salesforce applications including Apex code, Lightning Web Components...'
Restructure to clearly separate capabilities (what it does) from triggers (when to use it), e.g., 'Writes and reviews Apex code, builds Lightning Web Components, optimizes SOQL queries, and implements triggers. Use when...'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the Salesforce domain and lists several specific technologies (Apex code, Lightning Web Components, SOQL queries, triggers) but doesn't describe concrete actions - it only lists what it works with, not what it does with them. | 2 / 3 |
Completeness | Has a 'Use when' clause which addresses when to use it, but the 'what does this do' is weak - it lists technologies to work with but never states what actions or capabilities the skill provides (e.g., 'write', 'debug', 'optimize', 'review'). | 2 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Salesforce', 'Apex code', 'Lightning Web Components', 'SOQL queries', 'triggers', 'CRM', 'governor limits', 'bulk processing', 'Salesforce DX' - 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 separates it from general coding or other CRM skills - very unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has good structural organization with clear progressive disclosure through the reference table, but critically lacks actionable content. It reads more like a job description than executable guidance - telling Claude what a Salesforce developer does rather than providing concrete code patterns, SOQL examples, or trigger templates that Claude could actually use.
Suggestions
Add executable Apex code examples showing bulkification patterns (e.g., a trigger handler that processes records in bulk vs. the anti-pattern)
Include concrete SOQL query examples demonstrating selective queries, relationship queries, and governor-limit-safe patterns
Add a sample Lightning Web Component with HTML, JS, and meta.xml files that Claude can use as a template
Include validation checkpoints in the workflow such as 'Run all tests and verify 90%+ coverage before proceeding to deploy'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill contains some unnecessary verbosity like the 'Role Definition' section that restates the description, and the 'Knowledge Reference' section which lists concepts Claude already knows. However, the reference table and constraints are reasonably efficient. | 2 / 3 |
Actionability | The skill provides no executable code examples, no concrete SOQL queries, no sample Apex classes, and no actual LWC component code. It describes what to do ('bulkify Apex code') but never shows how with working examples. | 1 / 3 |
Workflow Clarity | The 5-step core workflow provides a sequence but lacks validation checkpoints. For Salesforce development involving governor limits and deployments, there should be explicit validation steps (e.g., 'run tests before deployment', 'verify governor limit usage'). | 2 / 3 |
Progressive Disclosure | The reference table provides clear one-level-deep navigation to specific topics with explicit 'Load When' guidance. The structure separates overview content from detailed references appropriately. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
75%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 12 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
Total | 12 / 16 Passed | |
- 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.