platform-docs-get

Retrieve authoritative Salesforce documentation from official domains with browser-rendered extraction.

Updated Jun 17, 2026
One-click install
npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill platform-docs-get
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: platform-docs-get
Source: https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG/tree/main/.agents/skills/platform-docs-get
Command: npx skills add https://github.com/angryracoon/ARIEF-VISEO-DEV-ORG --skill platform-docs-get

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires playwright, playwright-stealth, and includes scripts (resource) components.

What problem does it solve?

This Skill helps you find and ground answers in authoritative Salesforce documentation when the real answer is buried in JS-heavy pages, shell-rendered help articles, or child pages behind broad guide homepages.

Core Features & Use Cases

  • Official-source retrieval: Targets Salesforce-owned documentation on developer, help, architect, admin, and Lightning Design System domains.
  • Child-link aware extraction: Follows the most relevant official links when the first page is only a landing page or hub.
  • Robust page handling: Uses browser-rendered extraction to handle shell pages, shadow DOM content, and other hard-to-fetch docs.
  • Use case: Ask it to locate the exact Salesforce reference page for an Apex class, LWC feature, setup article, or Agentforce topic and return grounded results from the official source.

Quick Start

Ask the platform-docs-get skill to retrieve the exact official Salesforce documentation page for the concept you need and return the authoritative source details.

Frequently Asked Questions about platform-docs-get

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I retrieve official Salesforce documentation from JS-heavy shell pages?

Retrieving official Salesforce documentation from JS-heavy shell pages requires browser-rendered extraction to fully load shadow DOM content and navigate child links, bypassing shell layouts to access authoritative text directly from developer, help, and architect domains.

What is the best way to find exact Apex class or LWC reference pages on Salesforce help domains?

Finding exact Apex class or LWC reference pages requires targeting official Salesforce-owned domains and following child links, rejecting broad landing pages or third-party summaries to ground answers strictly in authoritative Lightning Design System and developer documentation.

How do I extract Salesforce help articles when the content is hidden behind child links?

Extracting Salesforce help articles hidden behind child links involves identifying the exact concept, fetching the official domain, and following the most relevant official links when the first page is only a landing page or hub, ensuring robust browser-rendered extraction of the target content.

Can I use Playwright to scrape Lightning Design System pages that are dynamically rendered?

Yes, using Playwright with stealth plugins supports scraping dynamically rendered Lightning Design System pages, handling shell pages and shadow DOM content to extract official Salesforce documentation that standard fetching methods cannot reach.

Why does my Salesforce documentation extraction return weak landing pages instead of the full article?

Salesforce documentation extraction returns weak landing pages when the initial URL is a broad guide homepage, requiring the extraction logic to identify and follow the most relevant official child links to reach the specific, authoritative content page.

Does browser-rendered extraction work for Salesforce admin and architect documentation domains?

Browser-rendered extraction works for Salesforce admin and architect documentation domains by loading JS-heavy pages completely, handling shadow DOM content, and targeting official Salesforce-owned sources to return grounded, authoritative results.