forcedotcom/sf-skills / skills/platform-docs-get
platform-docs-get
VerifiedOfficial 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.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 2.3 KB |
| SKILL.md | skill md | 9.1 KB |
| scripts/extract_help_salesforce.py | script | 18.4 KB |
| scripts/extract_salesforce_doc.py | script | 17.4 KB |
| scripts/requirements.txt | manifest | 30 B |
| scripts/runtime_bootstrap.py | script | 1.7 KB |
scripts/runtime_bootstrap.py
View on GitHubfrom __future__ import annotations
import os
import sys
from pathlib import Path
def sf_docs_runtime_root() -> Path:
return Path.home() / ".claude" / ".fetching-salesforce-docs-runtime"
def sf_docs_runtime_python() -> Path:
root = sf_docs_runtime_root() / "venv"
candidates = [
root / "bin" / "python",
root / "bin" / "python3",
root / "Scripts" / "python.exe",
]
for candidate in candidates:
if candidate.exists():
return candidate
return candidates[0] if os.name != "nt" else candidates[-1]
def prepare_sf_docs_runtime_env(env: dict[str, str] | None = None) -> dict[str, str]:
runtime_root = sf_docs_runtime_root()
target = dict(env or os.environ)
target.setdefault("PLAYWRIGHT_BROWSERS_PATH", str(runtime_root / "ms-playwright"))
target.setdefault("SF_DOCS_RUNTIME_ROOT", str(runtime_root))
return target
def maybe_reexec_in_sf_docs_runtime(script_path: str) -> bool:
runtime_python = sf_docs_runtime_python()
os.environ.update(prepare_sf_docs_runtime_env())
if os.environ.get("SF_DOCS_RUNTIME_ACTIVE") == "1":
return False
if not runtime_python.exists():
return False
try:
current_python = Path(sys.executable).resolve()
target_python = runtime_python.resolve()
if current_python == target_python:
os.environ["SF_DOCS_RUNTIME_ACTIVE"] = "1"
return False
except OSError:
pass
env = prepare_sf_docs_runtime_env()
env["SF_DOCS_RUNTIME_ACTIVE"] = "1"
os.execve(
str(runtime_python),
[str(runtime_python), str(Path(script_path).resolve()), *sys.argv[1:]],
env,
)
return True
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 197k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |