Salesforce architecture diagrams in Mermaid
Generate text-based Mermaid diagrams with ASCII fallback — OAuth flows, ERDs, integration sequences, Agentforce behavior maps — for Salesforce systems
- What
- Generate text-based Mermaid diagrams with ASCII fallback — OAuth flows, ERDs, integration sequences, Agentforce behavior maps — for Salesforce systems
- Cost
- Free
- Needs
- a diagramming need for a Salesforce system (OAuth flow, ERD, integration sequence, landscape, role hierarchy, or Agentforce map); a Mermaid renderer (GitHub, Confluence, docs) or plain-text need for the ASCII fallback — no accounts or keys required
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @forcedotcom's diagram-generation skill for Salesforce systems: text-based Mermaid diagrams (with ASCII fallback for plain-text docs and terminals) covering OAuth/auth flows, ERDs and data models, integration sequences, system landscapes, role/access hierarchies, and Agentforce behavior maps. Ships seven copy-ready OAuth flow templates (Authorization Code, PKCE, JWT Bearer, Client Credentials, Device Flow, Refresh Token, User-Agent/Social Sign-On), fourteen data-model ERD templates (core, Sales, Service, B2B Commerce, Campaigns, Consent, Files, Forecasting, FSL, Party model, Quote/Order, Revenue Cloud, Scheduler, Territory Management), plus architecture, integration-sequence, agent-flow and role-hierarchy templates — all governed by consistency conventions, a color-blind-friendly palette, ERD layout rules, and a built-in score guide (72–80 = production-ready). By @forcedotcom, listed here with credit to its creator. Honest caveats: Salesforce scope only — for non-Salesforce systems use a general diagramming skill; ERDs grounded on a real org schema should be paired with a custom-object discovery skill first; split oversized ERDs into sub-diagrams by domain. Apache-2.0 licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a diagramming need for a Salesforce system (OAuth flow, ERD, integration sequence, landscape, role hierarchy, or Agentforce map); a Mermaid renderer (GitHub, Confluence, docs) or plain-text need for the ASCII fallback — no accounts or keys required Install "Salesforce architecture diagrams in Mermaid" for me. It teaches the agent @forcedotcom's diagram workflow: gather the diagram type, scope and output preference first; pick the right Mermaid structure (sequenceDiagram for time-ordered flows, flowchart LR for ERDs and capability maps); ground ERDs on real org metadata when available; load the matching OAuth/ERD/architecture asset template; generate Mermaid first, add an ASCII fallback when useful, and explain the diagram briefly — with high-signal rules for sequences (autonumber), ERDs (simple cards, split by domain) and output format. Repository: https://github.com/forcedotcom/sf-skills/blob/main/skills/external-diagram-mermaid-generate/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "external-diagram-mermaid-generate". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. nothing to run yet — just ask the agent for the diagram type you need; for grounded ERDs, have your org metadata handy). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.