Skip to main content

What to use Skills for: examples and what you get

How Swantide Skills can change the way you work

Written by Engineering Swantide

What changes when you use skills

Out of the box the agent follows generic Salesforce best practice with the context of your Salesforce documentation. However, it does not know your team. Skills close that gap in three ways:

  • Consistency. Work arrives already following your standards, instead of arriving generic and needing additional edits.

  • Quality. The library encodes Salesforce platform expertise, so the agent reaches for the right approach without being told.

  • Durability. A skill describes what you want rather than how to phrase it to one particular model, so it keeps working as the models underneath it change.

A simple test: if you have corrected the agent on the same point twice, that correction belongs in a skill.
​

Start with what is already in the library

Before writing anything, switch on what exists. Go to Knowledge then Skills, click Settings, and open the Library filter.

Swantide skills

A short curated set of Salesforce admin practices. These are the habits a careful admin already has, for you to turn on OOTB if you'd like:

Skill

What it does

duplicate-field-check

Looks for a similar existing field before creating a new one, and asks whether to reuse it

metadata-dependency-check

Shows you where a component is used before you edit, rename or delete it

field-access-follow-up

Asks which permission sets get access to a new field, and whether read-only or read/edit, before calling the work done

hardcoded-values-check

Flags hardcoded IDs, emails, URLs and business values in flows, formulas, validation rules and Apex

global-value-set-check

Suggests a global value set when picklist values should stay in sync across objects

backend-field-labeling

Offers to mark a field as [Backend] when it will never appear on a layout or screen

report-duplicate-check

Searches for an existing report before building a new one

report-cleanup-audit

Groups duplicate reports, flags ones built on dead fields, and archives before deleting

org-health-assessment

Runs a structured review of configuration, automation, security, code and clutter, and ranks the fixes

requirements-discovery

Stops and runs a short discovery when a request is vague or large, instead of building the wrong thing

Salesforce skills

A much larger set published by Salesforce as open source, covering Agentforce, Flow, Apex, LWC, CRM Analytics, Omni-Channel, Data Cloud and the wider platform. These lean technical and are aimed at building rather than administering.

They are especially worth switching on if your team does development work. Nothing is lost by turning the set off: the agent still answers normally, it just has fewer specialist procedures to reach for.
​

What to write yourself

The library covers general Salesforce practice. It cannot know anything specific to your team, and that is exactly where your own skills earn their place. See examples of how you can leverage Custom Skills below, to be customized with your organization's standards:
​

1. Your naming conventions

Apply when creating or renaming a custom field, object, or permission set.

Prefix every custom field API name with the owning department code: SLS_ for Sales, SVC_ for Service, FIN_ for Finance. Use PascalCase after the prefix. Labels stay in plain business language with no prefix.

Permission sets are named by function then audience, for example Quoting_ReadOnly.

If the owning department is not clear from the request, ask before creating anything.

What you gain: everything the agent proposes arrives named your way, so nothing needs renaming afterward and your org stays searchable.
​

2. Your documentation and release note format

Apply when writing documentation, a release note, or a change summary.

Use four sections: what changed, who is affected, what they need to do, and how to roll back. Write for an admin who was not in the project. Name components by their label first and API name in brackets. No marketing language.

What you gain: notes that go straight into your release process, instead of prose someone has to restructure.
​

3. Your scoping rules

Useful for consulting teams who scope work repeatedly.

Apply when scoping work, estimating effort, or drafting a statement of work.

Break every estimate into discovery, build, test, and deploy. State assumptions explicitly and list what is out of scope. Flag any dependency on a managed package, a sandbox refresh, or a third-party integration, because those drive timelines more than build effort does.

Give ranges, not single numbers.

What you gain: a consistent starting point for scoping conversations, with the dependencies that cause overruns surfaced up front.
​

4. Who the answer is written for

The smallest skill here and often the most noticeable.

Apply to every explanation.

Default to writing for a Salesforce admin with three years of experience: skip basic platform concepts, but explain anything specific to this org. Lead with the answer, then the reasoning. When the answer depends on something you could not verify in the org, say so instead of assuming.

What you gain: answers pitched at your team rather than at a beginner, which means less scrolling to reach the point.
​

Workspace or personal?

When you create a skill you choose who it is for, and the right answer is usually obvious once you ask one question: would you want a teammate corrected this way too?

Make it a workspace skill

Keep it personal

Naming conventions, documentation format, review standards, scoping rules. Anything where two people doing it differently is a problem.

Your own shortcuts, a document template only you use, a tone you prefer. Anything where your teammate's different answer is fine.

Needs an admin. Applies to everyone immediately.

Anyone can create one. Follows you between workspaces.

If you are not an admin and you write something the whole team should follow, we suggest sending the idea to your Workspace's Admin. A personal skill shapes only your own agent.
​

Skills, Documents and one-off prompts

Three tools that are easy to confuse:

What you have

Use

Why

A rule about how work should be done

A skill

It applies on its own, every time the relevant work comes up

Reference material: a standards doc, a field mapping, a template

Documents, under Knowledge

The agent draws on the content when it is relevant, but it is material rather than an instruction

A question you need answered once

Just ask

Chats will reference knowledge base automatically if the question applies

Knowing it is working

You can see Skills are leveraged in your Agents thinking steps and tools used. You can also see high level usage summaries on the Skills in your library.

Did this answer your question?