Agent skill

Platform Docs Get

Official Salesforce documentation retrieval skill. An agent skill from forcedotcom/sf-skills.

Apache-2.0Auto-check passedSales & Support

Install Platform Docs Get

skills CLI

$ npx skills add forcedotcom/sf-skills --skill platform-docs-get -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills platform-docs-get --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/platform-docs-get .claude/skills/platform-docs-get && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "platform-docs-get" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-docs-get into .claude/skills/platform-docs-get/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-docs-get", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-docs-get

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add forcedotcom/sf-skills --skill platform-docs-get -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills platform-docs-get --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/platform-docs-get .agents/skills/platform-docs-get && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "platform-docs-get" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-docs-get into .agents/skills/platform-docs-get/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-docs-get", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add forcedotcom/sf-skills --skill platform-docs-get -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills platform-docs-get --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/platform-docs-get .cursor/skills/platform-docs-get && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "platform-docs-get" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-docs-get into .cursor/skills/platform-docs-get/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-docs-get", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/forcedotcom/sf-skills.git --path skills/platform-docs-get

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add forcedotcom/sf-skills --skill platform-docs-get -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills platform-docs-get --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/platform-docs-get .gemini/skills/platform-docs-get && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "platform-docs-get" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-docs-get into .gemini/skills/platform-docs-get/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-docs-get", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install forcedotcom/sf-skills platform-docs-get

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add forcedotcom/sf-skills --skill platform-docs-get -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/platform-docs-get .github/skills/platform-docs-get && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "platform-docs-get" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-docs-get into .github/skills/platform-docs-get/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-docs-get", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add forcedotcom/sf-skills --skill platform-docs-get -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install forcedotcom/sf-skills platform-docs-get --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/forcedotcom/sf-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/platform-docs-get .opencode/skills/platform-docs-get && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "platform-docs-get" agent skill from https://github.com/forcedotcom/sf-skills/tree/main/skills/platform-docs-get into .opencode/skills/platform-docs-get/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "platform-docs-get", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: platform-docs-get
GitHub stars: 1.1k
Token cost: ~2.3k tokens
SKILL.md length: 1,120 words
Files: 6 (incl. scripts)
Skills in repo: 248
Repo updated: Oct 3, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Official Salesforce documentation retrieval skill. An agent skill from forcedotcom/sf-skills.

Works in 6 steps: Classify the request first → Identify the exact concept → Prefer targeted official retrieval → …
You need authoritative Salesforce docs from developer.salesforce.com
SKILL.md covers Scope, Required Inputs, Official Sources Only and Retrieval Workflow, plus 7 more sections
Runs Python scripts from its folder

What it does

Platform Docs Get is an agent skill from forcedotcom/sf-skills. Official Salesforce documentation retrieval skill. Use when you need authoritative Salesforce docs from developer.salesforce.com, help.salesforce.com, architect.salesforce.com, admin.salesforce.com, or lightningdesignsystem.com, especially when pages are JS-heavy, shell-rendered, or hard to extract with naive fetching. Use to ground answers in official Salesforce sources instead of third-party blogs or summaries. TRIGGER when: user asks for official Salesforce documentation, Apex or API reference, LWC docs…

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts (for example `README.md`, `scripts/extract_help_salesforce.py` and `scripts/extract_salesforce_doc.py`).

It sits in Sales & Support, covering CRM management. It works with Salesforce. The repository describes itself as: Salesforce's curated collection of agent skills for building applications. Optimized for Agentforce Vibes, compatible with all AI tools. The licence is Apache-2.0.

When your agent uses it

You need authoritative Salesforce docs from developer.salesforce.com
Help.salesforce.com
Architect.salesforce.com
Admin.salesforce.com

Example prompts

“/platform-docs-get”

Requirements

Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

Classify the request first
Identify the exact concept
Prefer targeted official retrieval
Do not stop at broad landing pages
For developer.salesforce.com
For help.salesforce.com

What it can do on your machine

Read from SKILL.md and the folder at commit 3c15867. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 4 files in scripts/ (Python), which the agent can run.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Platform Docs Get loads about 2.3k tokens when it runs. Until then it costs about 195 tokens; SKILL.md has 1,120 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~195
When it runs · the whole SKILL.md, loaded when a task matches: ~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.

SKILL.md

The full file from forcedotcom/sf-skills at commit 3c15867, republished under its Apache-2.0 licence (© forcedotcom). 1,120 words, ~2,334 tokens.

Download SKILL.mdSave it as .claude/skills/platform-docs-get/SKILL.md (or your agent's skills folder). This skill also uses 5 other files; get the full folder from GitHub.

name: platform-docs-get
description: Official Salesforce documentation retrieval skill. Use when you need authoritative Salesforce docs from developer.salesforce.com, help.salesforce.com, architect.salesforce.com, admin.salesforce.com, or lightningdesignsystem.com, especially when pages are JS-heavy, shell-rendered, or hard to extract with naive fetching. Use to ground answers in official Salesforce sources instead of third-party blogs or summaries. TRIGGER when: user asks for official Salesforce documentation, Apex or API reference, LWC docs, Agentforce docs, setup or help articles, or any doc from a Salesforce-owned domain. DO NOT TRIGGER when: user is asking for a code change, deployment task, or anything not requiring documentation retrieval — use the appropriate sf-* skill instead.
metadata.version: 1.2
metadata.domains: Platform

platform-docs-get

Use this skill to retrieve and ground answers in official Salesforce documentation on the public web.

This skill provides a reliable online retrieval playbook for Salesforce docs that are hard to fetch, especially help.salesforce.com, JS-heavy developer.salesforce.com, Lightning Design System docs on lightningdesignsystem.com, and other official Salesforce-owned doc pages such as architect.salesforce.com and admin.salesforce.com.

Optional extraction scripts are available in scripts/ — see the Reference File Index below.

Scope


In scope	Official Salesforce doc retrieval: Apex, API, LWC, metadata, Agentforce, setup articles, SLDS, architect/admin guidance
Out of scope	Third-party blogs, PDF fallback, local corpus indexing, benchmark workflows, generating code or metadata

Required Inputs

Before fetching, identify:

The exact concept, identifier, class, method, or feature name being requested
The likely doc family (developer docs, help articles, design system, architect/admin)

No additional setup is required to use the retrieval playbook in this skill. The optional extraction scripts require playwright — see scripts/requirements.txt.

Official Sources Only

Prefer Salesforce-owned documentation sources:

developer.salesforce.com
help.salesforce.com
architect.salesforce.com
admin.salesforce.com
lightningdesignsystem.com
other official Salesforce documentation pages when Salesforce uses them as the source of truth

Avoid third-party blogs, videos, or summary articles unless the user explicitly asks for them.

Do not fall back to PDFs.

Retrieval Workflow

1. Classify the request first

Before fetching anything, identify the likely doc family.

Family	Typical Source	Use For
Developer docs	`developer.salesforce.com/docs/...`	Apex, APIs, LWC, metadata, Agentforce developer docs
Help docs	`help.salesforce.com/...`	setup, admin, product configuration
Architect/Admin docs	`architect.salesforce.com/...`, `admin.salesforce.com/...`	best practices, patterns, well-architected guidance, admin enablement
Design system docs	`lightningdesignsystem.com/...`	SLDS, Cosmos, design tokens, component and styling guidance
Legacy atlas docs	`developer.salesforce.com/docs/atlas.en-us.*`	older official guide and reference docs

2. Identify the exact concept

Extract the real target before you search:

exact API/class/method name
exact feature name
exact product phrase
exact setup concept

Examples:

Lightning Message Service
Wire Service
System.StubProvider
Agentforce Actions
Messaging for In-App and Web allowed domains

3. Prefer targeted official retrieval

Do not broad-crawl Salesforce docs.

Instead:

identify the most likely official guide root or article
if search is needed, restrict it to official Salesforce domains only
fetch that official page
check whether the exact concept actually appears on the page
if not, inspect and follow the most relevant 1–3 official child links
stop once you have grounded evidence

4. Do not stop at broad landing pages

A guide landing page is not enough unless it clearly contains the exact requested concept.

This is especially important for:

LWC docs
Agentforce docs
broad platform guide homepages
help landing pages that link to the real article

5. For `developer.salesforce.com`

Use this playbook:

start with the most likely official guide root
if the page is JS-heavy, prefer browser-rendered extraction
check whether the exact concept appears on the page
if the concept is missing, inspect official child links and follow the best matching 1–3 links
prefer exact concept pages over broad guide roots
legacy atlas pages are valid if they are the real official reference for the concept

6. For `help.salesforce.com`

Help pages often fail with naive fetching.

Use this playbook:

prefer exact articleView?id=... URLs when available
use browser-rendered extraction when plain fetch returns shell content
treat outputs like Loading, Sorry to interrupt, CSS Error, or mostly chrome/navigation text as failed extraction, not evidence
look for the real article body, not just header, nav, or footer text
reject shell pages and soft-404 pages such as:
- "We looked high and low but couldn't find that page"
- generic empty help shells
if starting from a nearby guide or hub page, follow linked Help articles until you reach the real article body
if extraction still fails after targeted retries, return the best official Help URLs you found and explicitly say that article-body extraction was unsuccessful

Acceptance Rules

A page is good enough to answer from only when at least one of these is true:

the exact identifier appears on the page
the exact concept phrase appears on the page
multiple query-specific phrases appear in the correct official context

A page is not good enough when:

it is only a broad landing page
it is a shell page with little real article text
it is from the wrong product area
it does not contain the requested identifier or concept
it is a third-party explanation when an official page should exist

Show full SKILL.md (414 more words)Show less

Rejection Rules

Reject these as final evidence:

broad guide homepages without the exact concept
release notes when a concept/reference page is expected
admin blog posts when developer docs are requested
third-party blogs when official docs are available
shell-rendered pages with no real article body
pages whose titles sound right but whose body does not contain the requested concept

Grounding Requirements

When answering, include:

guide/article title
exact official URL
source type:
- developer doc page
- atlas reference page
- help article page
any caveat if extraction was partial or browser-rendered

If evidence is weak, say so plainly.

Examples

Example: Lightning Message Service

Do not stop at the general LWC guide root. Find the exact LWC page for Lightning Message Service or follow the most relevant child links from the LWC docs until the exact concept appears.

Example: Wire Service

Do not answer from the LWC homepage unless Wire Service is actually present there. Follow the relevant child doc page for wire service or wire adapters.

Example: Agentforce Actions

Do not answer from a broad Agentforce landing page or a blog post. Find the official Agentforce developer page for actions, or follow the best matching child pages from the official Agentforce docs.

Example: Messaging for In-App and Web allowed domains

Prefer official Help articles and browser-rendered extraction. Reject generic help shells. Follow linked Help articles from nearby official messaging docs if needed.

Example: System.StubProvider

Prefer the official Salesforce reference/developer page where the exact identifier appears. Do not substitute a broader Apex landing page if the identifier is absent.

Non-Goals

This skill should not:

maintain a local documentation corpus
rely on a local index
use PDF fallback
run benchmark workflows
depend on repo-specific scripts to be useful

Output Expectations

For each retrieval, include:

Guide or article title
Exact official URL
Source type (developer doc page / atlas reference page / help article page)
Any caveat if extraction was partial or browser-rendered

If evidence is weak, say so plainly rather than forcing an answer.

Reference File Index

File	When to read
`scripts/extract_salesforce_doc.py`	Use to fetch any official Salesforce doc URL; automatically routes `help.salesforce.com` into the dedicated Help extractor and supports browser-rendered extraction for all Salesforce-owned doc hosts
`scripts/extract_help_salesforce.py`	Use directly when targeting `help.salesforce.com` `articleView` URLs; use when the wrapper is not appropriate
`scripts/runtime_bootstrap.py`	Imported by the extraction scripts to resolve the isolated platform-docs-get Python runtime and Playwright browser path; not called directly
`scripts/requirements.txt`	Lists Python dependencies (`playwright`, `playwright-stealth`) needed to run the extraction scripts

Files

SKILL.md and 5 other files (scripts) in skills/platform-docs-get of forcedotcom/sf-skills.

SKILL.md
README.md
scripts/extract_help_salesforce.py
scripts/extract_salesforce_doc.py
scripts/requirements.txt
scripts/runtime_bootstrap.py

Open the folder on GitHubat commit 3c15867

Compare with similar skills

Platform Docs Get next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Platform Docs Get compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Platform Docs Get this skillforcedotcom/sf-skills	1.1k	—	~2.3k	Automated safety check: Pass	Apache-2.0	5 days ago
Soql Lib Query Builderbeyond-the-cloud-dev/soql-lib	154	—	~4.3k	Automated safety check: Pass	MIT	4 days ago
Sf DatacloudJaganpro/sf-skills	424	—	~2.7k	Automated safety check: Pass	MIT	5 mo ago
Soql Lib Selectorbeyond-the-cloud-dev/soql-lib	154	—	~2k	Automated safety check: Pass	MIT	4 days ago
Dev SetupPortwood-Global-Solutions/Portwood	125	—	~1.1k	Automated safety check: Pass	Apache-2.0	2 days ago
Sf FlowJaganpro/sf-skills	424	—	~1.8k	Automated safety check: Pass	MIT	5 mo ago

Similar skills

Soql Lib Query Builder
beyond-the-cloud-dev/soql-lib
Builds Salesforce SOQL queries using the SOQL Lib fluent builder API (SOQL.cls).
154 GitHub stars~4.3k tokensUpdated 4 days ago
Sales & SupportAuto-check passed
Sf Datacloud
Jaganpro/sf-skills
Salesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows.
424 GitHub stars~2.7k tokensUpdated 5 mo ago
Sales & SupportAuto-check passed
Soql Lib Selector
beyond-the-cloud-dev/soql-lib
Creates Salesforce Apex selector classes using the SOQL Lib selector pattern.
154 GitHub stars~2k tokensUpdated 4 days ago
Sales & SupportAuto-check passed
Dev Setup
Portwood-Global-Solutions/Portwood
Get from a fresh clone of Portwood to a working, fully-tested Salesforce org.
125 GitHub stars~1.1k tokensUpdated 2 days ago
Sales & SupportAuto-check passed
Sf Flow
Jaganpro/sf-skills
Creates and validates Salesforce Flows with 110-point scoring.
424 GitHub stars~1.8k tokensUpdated 5 mo ago
Sales & SupportAuto-check passed
Google Maps Export
gmapsscraper/google-maps-agent-skills
Export Google Maps business data to CSV, JSON, or CRM format (HubSpot, Pipedrive, Salesforce).
131 GitHub stars~1.2k tokensUpdated 4 mo ago
Sales & SupportAuto-check passed

Questions about Platform Docs Get

What does Platform Docs Get do?

Official Salesforce documentation retrieval skill. An agent skill from forcedotcom/sf-skills. Platform Docs Get is an agent skill from forcedotcom/sf-skills. Official Salesforce documentation retrieval skill.

When should I use Platform Docs Get?

Platform Docs Get fits situations like: you need authoritative Salesforce docs from developer.salesforce.com; help.salesforce.com; architect.salesforce.com; admin.salesforce.com.

How do I install Platform Docs Get in Claude Code?

Run `npx skills add forcedotcom/sf-skills --skill platform-docs-get -a claude-code`. Or copy the skill folder (skills/platform-docs-get in forcedotcom/sf-skills) into .claude/skills/platform-docs-get in your project. Claude Code loads it when a task matches its description.

How do I install Platform Docs Get in Codex?

Run `npx skills add forcedotcom/sf-skills --skill platform-docs-get -a codex`. Or copy the skill folder (skills/platform-docs-get in forcedotcom/sf-skills) into .agents/skills/platform-docs-get in your project. Codex loads it when a task matches its description.

Can I use Platform Docs Get in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add forcedotcom/sf-skills --skill platform-docs-get -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/platform-docs-get, .gemini/skills/platform-docs-get, .github/skills/platform-docs-get and .opencode/skills/platform-docs-get in your project.

What does Platform Docs Get need to run?

Going by SKILL.md and its folder, Platform Docs Get needs Python for the scripts in its folder. Our summary lists: Python 3.

Does Platform Docs Get access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Platform Docs Get safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Platform Docs Get use?

Platform Docs Get is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Platform Docs Get use?

About 2.3k tokens (SKILL.md is roughly 9.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Platform Docs Get?

Skills that share tags, products or a category with Platform Docs Get: Soql Lib Query Builder (beyond-the-cloud-dev/soql-lib, 154 stars), Sf Datacloud (Jaganpro/sf-skills, 424 stars), Soql Lib Selector (beyond-the-cloud-dev/soql-lib, 154 stars) and Dev Setup (Portwood-Global-Solutions/Portwood, 125 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Platform Docs Get?

forcedotcom (a GitHub organization) maintains it in forcedotcom/sf-skills, which has 1,058 GitHub stars. The repository holds 248 skills in this directory. The repository was last updated on October 3, 2026.

Source: forcedotcom/sf-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Platform Docs Get

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

platform-docs-get

Scope

Required Inputs

Official Sources Only

Retrieval Workflow

1. Classify the request first

2. Identify the exact concept

3. Prefer targeted official retrieval

4. Do not stop at broad landing pages

5. For developer.salesforce.com

6. For help.salesforce.com

Acceptance Rules

Rejection Rules

Grounding Requirements

Examples

Example: Lightning Message Service

Example: Wire Service

Example: Agentforce Actions

Example: Messaging for In-App and Web allowed domains

Example: System.StubProvider

Non-Goals

Output Expectations

Reference File Index

Files

Compare with similar skills

Similar skills

More from forcedotcom/sf-skills

Related

Questions about Platform Docs Get

5. For `developer.salesforce.com`

6. For `help.salesforce.com`