CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

35

Quality

31%

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

18%Scale 1-5

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

This skill is essentially a skeleton or outline with no actionable content. It names several important Salesforce development patterns but provides no code examples, no concrete guidance, and no real information in the Sharp Edges table (all rows contain placeholder 'Issue'/'See docs' text). The skill fails to teach Claude anything it couldn't already infer from the section headings alone.

Suggestions

Add executable code examples for each pattern: a complete @wire decorator example, a bulkified trigger with handler class, and a Queueable Apex implementation.

Replace the placeholder Sharp Edges table with actual Salesforce governor limit issues, specific severity levels, and concrete solutions or workarounds.

Add concrete anti-pattern examples showing the problematic code (SOQL in loops, DML in loops) alongside the corrected version.

Either add detailed content inline or create and reference bundle files (e.g., WIRE_EXAMPLES.md, TRIGGER_PATTERN.md) for each pattern's full implementation.

DimensionReasoningScore

Conciseness

The content is relatively brief but includes placeholder/generic text that wastes tokens (e.g., the 'Sharp Edges' table with repeated 'Issue'/'See docs' entries, and the boilerplate 'When to Use' section). Some descriptions like explaining what bulkification means are borderline unnecessary for Claude.

3 / 5

Actionability

The skill provides zero concrete code, commands, or executable examples. Every section is purely descriptive with no actual wire service syntax, no trigger handler code, no Queueable implementation. The anti-patterns section lists names without showing what to avoid or what to do instead.

1 / 5

Workflow Clarity

There are no sequenced steps, no workflows, no validation checkpoints. The content is entirely declarative headers and brief descriptions with no process guidance for any of the three patterns mentioned.

1 / 5

Progressive Disclosure

The content has some section structure (Patterns, Anti-Patterns, Sharp Edges) but no references to external files, no links to detailed guides, and the Sharp Edges table is entirely placeholder content. Content that clearly needs elaboration (code examples, detailed patterns) is neither inline nor referenced.

2 / 5

Total

7

/

20

Passed

Description

45%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 identifies a specific Salesforce LWC concept (@wire decorator) and explains its purpose, but lacks an explicit 'Use when...' clause that would help Claude know when to select this skill. It reads more like a best-practice recommendation than a skill selection guide, and could benefit from natural trigger terms and clearer activation criteria.

Suggestions

Add an explicit 'Use when...' clause with trigger phrases like 'Use when the user is building LWC components that need to fetch data, query Salesforce records, or call Apex from a Lightning Web Component.'

Include more natural trigger terms and synonyms such as 'wire service', 'LWC data fetching', 'querying records in LWC', 'calling Apex from components', or 'Salesforce Lightning Web Components'.

Expand the 'what' to list more concrete actions, e.g., 'Wires Apex methods and Lightning Data Service adapters to component properties or functions, handles data provisioning and error states, and supports refreshing wired data.'

DimensionReasoningScore

Specificity

Names the domain (LWC/Salesforce) and describes a concrete action ('reactive data binding with Lightning Data Service or Apex methods'), but doesn't list multiple specific actions or cover the full range of what the skill teaches.

3 / 5

Completeness

Has a reasonable 'what' (use @wire for reactive data binding), but there is no explicit 'when' clause or trigger guidance. The description explains why to use it ('fits LWC's reactive architecture') rather than when Claude should select this skill. Missing a 'Use when...' clause caps this at 3, and the weak implicit triggering pushes it to 2.

2 / 5

Trigger Term Quality

Includes relevant technical terms like '@wire', 'LWC', 'Lightning Data Service', 'Apex methods', and 'reactive data binding', but these are more developer jargon than natural user phrases. Missing common variations like 'wire decorator', 'wire service', 'LWC data fetching', or 'Salesforce component data'.

3 / 5

Distinctiveness Conflict Risk

The '@wire decorator' focus is fairly specific and distinct within the Salesforce/LWC ecosystem. However, it could overlap with broader LWC development skills or Apex-related skills. The specific mention of '@wire' and 'reactive data binding' helps differentiate it.

4 / 5

Total

12

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.