Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
jaganpro avatar

Sf Docs

  • 1.2k installs
  • 423 repo stars
  • Updated April 27, 2026
  • jaganpro/sf-skills

sf-docs retrieves official Salesforce documentation from JS-heavy developer and help pages.

About

The sf-docs skill retrieves and grounds answers in official Salesforce documentation from developer.salesforce.com, help.salesforce.com, architect.salesforce.com, admin.salesforce.com, and lightningdesignsystem.com without local corpus or PDF fallback. Core goal finds the best official HTML page online and extracts enough content to answer confidently, stating weak evidence clearly instead of forcing answers. Workflow classifies requests into developer docs, help setup articles, architect guidance, or design system references before searching. Optional wrapper scripts extract_salesforce_doc.py routes help URLs to a dedicated extractor and supports stealth mode with playwright-stealth for bot-sensitive pages. No indexing, benchmark workflow, or helper CLI dependency is required for the core playbook. Avoid third-party blogs unless explicitly requested. Classify Apex, LWC, metadata, Agentforce, and setup questions to the right doc family table before fetching. JS-heavy shell-rendered pages need browser-rendered extraction rather than naive fetch. Evidence quality threshold: if extraction is weak, say so rather than hallucinating Salesforce behavior from training data alone.

  • Official Salesforce web docs only; no local corpus or PDF fallback.
  • Classifies developer, help, architect, admin, and SLDS doc families first.
  • Optional extract_salesforce_doc.py wrapper with help-specific extractor.
  • Stealth mode via --stealth when playwright-stealth is installed.
  • States weak evidence clearly instead of forcing low-confidence answers.

Sf Docs by the numbers

  • 1,168 all-time installs (skills.sh)
  • +4 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #233 of 1,879 Documentation skills by installs in the Skillselion catalog
  • Security screen: MEDIUM risk (skills.sh audit)
  • Data as of Aug 4, 2026 (Skillselion catalog sync)
At a glance

sf-docs capabilities & compatibility

Capabilities
doc family classification · browser rendered extraction · help url dedicated extractor · official source enforcement · evidence quality disclosure
Use cases
documentation · research
npx skills add https://github.com/jaganpro/sf-skills --skill sf-docs

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.2k
repo stars423
Security audit2 / 3 scanners passed
Last updatedApril 27, 2026
Repositoryjaganpro/sf-skills

How do I get reliable content from help.salesforce.com or developer.salesforce.com pages?

Retrieve official Salesforce documentation from JS-heavy developer and help pages with browser extraction.

Who is it for?

Developers needing authoritative Salesforce docs when pages are shell-rendered or JS-heavy.

Skip if: Skip when third-party blog summaries are explicitly requested over official docs.

When should I use this skill?

User asks for official Salesforce docs on Apex, LWC, metadata, Agentforce, or setup.

What you get

Grounded answer citing official Salesforce HTML with clear evidence quality assessment.

  • Official Salesforce doc excerpts
  • SLDS reference snippets

By the numbers

  • Covers 5 official Salesforce documentation domains including lightningdesignsystem.com

Files

SKILL.mdMarkdownGitHub ↗

sf-docs

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

This skill is intentionally simple:

  • no local corpus
  • no indexing
  • no benchmark workflow
  • no helper CLI dependency
  • no PDF fallback

Its job is to provide 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.

An optional wrapper script is available at:

  • skills/sf-docs/scripts/extract_salesforce_doc.py

It automatically routes help.salesforce.com URLs into the dedicated Help extractor and supports other official documentation pages such as *.salesforce.com and lightningdesignsystem.com through a generic browser-rendered path. For bot-sensitive pages, it also supports best-effort optional stealth mode via --stealth when playwright-stealth is installed.

The dedicated Help extractor is also available directly at:

  • skills/sf-docs/scripts/extract_help_salesforce.py

Core Goal

Find the best official Salesforce HTML page online and extract enough real content to answer confidently.

If the evidence is weak, say so clearly instead of forcing a weak answer.

When to Use

Use sf-docs when a user asks for:

  • official Salesforce documentation
  • Apex, API, LWC, metadata, Agentforce, setup, or help articles
  • docs from developer.salesforce.com
  • docs from help.salesforce.com
  • pages that look JS-heavy, shell-rendered, or difficult to read with ordinary fetches

Official Sources Only

Prefer Salesforce-owned documentation sources:

  • developer.salesforce.com
  • help.salesforce.com
  • architect.salesforce.com
  • admin.salesforce.com
  • lightningdesignsystem.com
  • other relevant 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.

FamilyTypical SourceUse For
Developer docsdeveloper.salesforce.com/docs/...Apex, APIs, LWC, metadata, Agentforce developer docs
Help docshelp.salesforce.com/...setup, admin, product configuration
Architect/Admin docsarchitect.salesforce.com/..., admin.salesforce.com/...best practices, patterns, well-architected guidance, admin enablement
Design system docslightningdesignsystem.com/...SLDS, Cosmos, design tokens, component and styling guidance
Legacy atlas docsdeveloper.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: 1. identify the most likely official guide root or article 2. if search is needed, restrict it to official Salesforce domains only 3. fetch that official page 4. check whether the exact concept actually appears on the page 5. if not, inspect and follow the most relevant 1–3 official child links 6. 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

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: 1. guide/article title 2. exact official URL 3. source type:

  • developer doc page
  • atlas reference page
  • help article page

4. 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

Cross-Skill Role

Other sf-* skills should use sf-docs when they need authoritative Salesforce documentation instead of relying on generic search alone.

Related skills

Forks & variants (1)

Sf Docs has 1 known copy in the catalog totaling 1 installs. They canonicalize to this original listing.

How it compares

Use sf-docs for live official Salesforce pages; use local doc indexes when you maintain an offline corpus.

FAQ

Does it use a local doc index?

No; online retrieval playbook only with optional browser extraction.

What sources are official?

developer.salesforce.com, help.salesforce.com, architect, admin, and SLDS.

What if the page is JS-heavy?

Use browser-rendered extraction via the optional wrapper scripts.

Is Sf Docs safe to install?

skills.sh reports 2 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.

Documentationdocsintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.