CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

salesforce-development

Use @wire decorator for reactive data binding with Lightning Data Service or Apex methods. @wire fits LWC's reactive architecture and enables Salesforce performance optimizations.

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/salesforce-development/SKILL.md

The canonical home for this skill is salesforce-development in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

36%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body reads as an unfinished template: pattern directives with no code examples, bare-label anti-patterns, an entirely placeholder Sharp Edges table, and a circular 'When to Use' sentence. Its leanness is undermined by placeholder filler, and it offers no executable guidance or workflow validation.

Suggestions

Add executable code examples for each pattern: an @wire usage snippet, a bulkified handler-pattern trigger, and a Queueable class with chaining.

Fill the Sharp Edges table with real issues, severities, and solutions (or link an actual reference file) instead of 'Issue | critical | See docs' placeholder rows.

Replace the circular 'When to Use' filler with concrete applicability conditions, e.g. 'Use when creating or editing LWC components, Apex triggers, or asynchronous Apex'.

DimensionReasoningScore

Conciseness

The pattern blurbs are lean and assume competence, but roughly ten lines are wasted: the Sharp Edges table holds eight unfilled placeholder rows ('Issue | critical | See docs'), the first pattern repeats the frontmatter description verbatim, and the 'When to Use' section is circular filler.

3 / 5

Actionability

There is no code or executable command anywhere; guidance stays at the level of 'Use handler pattern for separation of concerns' and anti-patterns that are bare labels, with 'See docs' pointing nowhere. A few specific facts ('200+ records', '50 jobs per transaction, 1 child job when chaining') keep it above entirely vague.

2 / 5

Workflow Clarity

No multi-step process is sequenced and no validation checkpoints exist, even though the covered areas (bulkified triggers, Queueable chaining) involve batch operations; the 'When to Use' section is placeholder text ('applicable to execute the workflow or actions described in the overview') that clarifies nothing. The Patterns/Anti-Patterns/Sharp Edges layout is coherent but steps are undefined and validation absent.

2 / 5

Progressive Disclosure

Sections are reasonably organized and the skill is short with no bundle files, but 'See docs' is repeated eight times with no documentation anywhere in the bundle — dead, unresolved references rather than clear navigation.

3 / 5

Total

10

/

20

Passed

Description

53%Weight 40%Scale 1-5

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 is concrete and clearly Salesforce-specific, but it describes only the @wire pattern while the skill body covers triggers, Queueable Apex, and bulkification, and it omits any 'Use when...' trigger guidance. Adding explicit trigger scenarios and terms matching the full skill scope would raise it.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building Lightning Web Components, writing Apex triggers, or doing Salesforce development'.

Broaden the 'what' to cover the skill's actual scope (bulkified triggers with handler pattern, Queueable Apex, anti-patterns), not just @wire.

Include natural user phrases such as 'Lightning Web Component' spelled out, 'Apex trigger', and 'Salesforce development' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

The description names the domain and one concrete action ('reactive data binding with Lightning Data Service or Apex methods'), but covers only the @wire pattern rather than the skill's full scope (triggers, Queueable Apex, bulkification), so coverage is not comprehensive.

3 / 5

Completeness

It gives a fairly clear 'what' for the @wire pattern but has no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

It includes relevant keywords ('@wire', 'Lightning Data Service', 'Apex', 'LWC', 'Salesforce') but misses common variations users would naturally say, such as 'Lightning Web Component' spelled out, 'Apex trigger', or 'Salesforce development'.

3 / 5

Distinctiveness Conflict Risk

'@wire', 'Lightning Data Service', and 'LWC' clearly mark the Salesforce LWC niche with minimal conflict risk against non-Salesforce skills; minor overlap remains with a general Apex/Salesforce development skill via 'Apex methods'.

4 / 5

Total

13

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills/skills/salesforce-development/SKILL.md

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.