[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CBA17KXN5FNG3YT93HF2WS":3,"skill-same:01M7CBA17KXN5FNG3YT93HF2WS":58},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M7CBA17KXN5FNG3YT93HF2WS","sf-diagram-mermaid",null,"Salesforce architecture diagrams using Mermaid with ASCII fallback. TRIGGER when: user says \"diagram\", \"visualize\", \"ERD\", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG\u002FSVG image output (use sf-diagram-nanobananapro), or asks about non-Salesforce systems.","om-scogo\u002Fskillsh-scraper","om-scogo","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160466840?v=4","01M79AWB6DFVCQ7RK70CS34B96","Om Achrekar","01M79AWB6ZM9SKR8KDH1WSSM22",0,"MIT","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-diagram-mermaid\u002FSkill.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sf-diagram-mermaid\ndescription: >\n  Salesforce architecture diagrams using Mermaid with ASCII fallback.\n  TRIGGER when: user says \"diagram\", \"visualize\", \"ERD\", or asks for sequence\n  diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid.\n  DO NOT TRIGGER when: user wants PNG\u002FSVG image output (use sf-diagram-nanobananapro),\n  or asks about non-Salesforce systems.\nlicense: MIT\ncompatibility: \"Requires Mermaid-capable renderer for diagram previews\"\nmetadata:\n  version: \"1.2.0\"\n  author: \"Jag Valaiyapathy\"\n  scoring: \"80 points across 5 categories\"\n---\n\n# sf-diagram-mermaid: Salesforce Diagram Generation\n\nUse this skill when the user needs **text-based diagrams**: Mermaid diagrams for architecture, OAuth, integration flows, ERDs, or Agentforce structure, plus ASCII fallback when plain-text compatibility matters.\n\n## When This Skill Owns the Task\n\nUse `sf-diagram-mermaid` when the user wants:\n- Mermaid output\n- ASCII fallback diagrams\n- architecture, sequence, flowchart, or ERD views in markdown-friendly form\n- diagrams that can live directly in docs, READMEs, or issues\n\nDelegate elsewhere when the user wants:\n- rendered PNG\u002FSVG images or polished mockups → [sf-diagram-nanobananapro](..\u002Fsf-diagram-nanobananapro\u002FSKILL.md)\n- non-Salesforce systems only → use a more general diagramming skill\n- object discovery before an ERD → [sf-metadata](..\u002Fsf-metadata\u002FSKILL.md)\n\n---\n\n## Supported Diagram Families\n\n| Type | Preferred Mermaid form | Typical use |\n|---|---|---|\n| OAuth \u002F auth flows | `sequenceDiagram` | Authorization Code, JWT, PKCE, Device Flow |\n| ERD \u002F data model | `flowchart LR` | object relationships and sharing context |\n| integration sequence | `sequenceDiagram` | request\u002Fresponse or event choreography |\n| system landscape | `flowchart` | high-level architecture |\n| role \u002F access hierarchy | `flowchart` | users, profiles, permissions |\n| Agentforce behavior map | `flowchart` | agent → topic → action relationships |\n\n---\n\n## Required Context to Gather First\n\nAsk for or infer:\n- diagram type\n- scope and entities \u002F systems involved\n- output preference: Mermaid only, ASCII only, or both\n- whether styling should be minimal, documentation-first, or presentation-friendly\n- for ERDs: whether org metadata is available for grounding\n\n---\n\n## Recommended Workflow\n\n### 1. Pick the right diagram structure\n- use `sequenceDiagram` for time-ordered interactions\n- use `flowchart LR` for ERDs and capability maps\n- keep a single primary story per diagram when possible\n\n### 2. Gather data\nFor ERDs and grounded diagrams:\n- use [sf-metadata](..\u002Fsf-metadata\u002FSKILL.md) when real schema discovery is needed\n- optionally use the local metadata helper script for counts \u002F relationship context when appropriate\n\n### 3. Generate Mermaid first\nApply:\n- accurate labels\n- simple readable node text\n- consistent relationship notation\n- restrained styling that renders cleanly in markdown viewers\n\n### 4. Add ASCII fallback when useful\nProvide an ASCII version when the user wants terminal compatibility or plaintext documentation.\n\n### 5. Explain the diagram briefly\nCall out the key relationships, flow direction, and any assumptions.\n\n---\n\n## High-Signal Rules\n\n### For sequence diagrams\n- use `autonumber` when step order matters\n- distinguish requests vs responses clearly\n- use notes sparingly for protocol detail\n\n### For ERDs\n- prefer `flowchart LR`\n- keep object cards simple\n- use clear relationship arrows\n- avoid field overload unless the user explicitly asks for field-level detail\n- color-code object types only when it improves readability\n\n### For ASCII output\n- keep width reasonable\n- align arrows and boxes consistently\n- optimize for readability over decoration\n\n---\n\n## Output Format\n\n````markdown\n## \u003CDiagram Title>\n\n### Mermaid Diagram\n```mermaid\n\u003Cdiagram>\n```\n\n### ASCII Fallback\n```text\n\u003Cascii>\n```\n\n### Notes\n- \u003Ckey point>\n- \u003Cassumption or limitation>\n````\n\n---\n\n## Cross-Skill Integration\n\n| Need | Delegate to | Reason |\n|---|---|---|\n| real object \u002F field definitions | [sf-metadata](..\u002Fsf-metadata\u002FSKILL.md) | grounded ERD generation |\n| rendered diagram \u002F image output | [sf-diagram-nanobananapro](..\u002Fsf-diagram-nanobananapro\u002FSKILL.md) | visual polish beyond Mermaid |\n| connected-app auth setup context | [sf-connected-apps](..\u002Fsf-connected-apps\u002FSKILL.md) | accurate OAuth flows |\n| Agentforce logic visualization | [sf-ai-agentscript](..\u002Fsf-ai-agentscript\u002FSKILL.md) | source-of-truth behavior details |\n| Flow behavior diagrams | [sf-flow](..\u002Fsf-flow\u002FSKILL.md) | actual Flow logic grounding |\n\n---\n\n## Reference Map\n\n### Start here\n- [references\u002Fdiagram-conventions.md](references\u002Fdiagram-conventions.md)\n- [references\u002Fmermaid-reference.md](references\u002Fmermaid-reference.md)\n- [references\u002Fusage-examples.md](references\u002Fusage-examples.md)\n\n### Styling \u002F ERD specifics\n- [references\u002Fmermaid-styling.md](references\u002Fmermaid-styling.md)\n- [references\u002Fcolor-palette.md](references\u002Fcolor-palette.md)\n- [references\u002Ferd-conventions.md](references\u002Ferd-conventions.md)\n\n### Preview\n- [references\u002Fpreview-guide.md](references\u002Fpreview-guide.md)\n- [scripts\u002Fmermaid_preview.py](scripts\u002Fmermaid_preview.py)\n- [scripts\u002Fquery-org-metadata.py](scripts\u002Fquery-org-metadata.py)\n\n---\n\n## Score Guide\n\n| Score | Meaning |\n|---|---|\n| 72–80 | production-ready diagram |\n| 60–71 | clear and useful with minor polish left |\n| 48–59 | functional but could be clearer |\n| 35–47 | needs structural improvement |\n| \u003C 35 | inaccurate or incomplete |\n","# sf-diagram-mermaid: Salesforce Diagram Generation\n\nUse this skill when the user needs **text-based diagrams**: Mermaid diagrams for architecture, OAuth, integration flows, ERDs, or Agentforce structure, plus ASCII fallback when plain-text compatibility matters.\n\n## When This Skill Owns the Task\n\nUse `sf-diagram-mermaid` when the user wants:\n- Mermaid output\n- ASCII fallback diagrams\n- architecture, sequence, flowchart, or ERD views in markdown-friendly form\n- diagrams that can live directly in docs, READMEs, or issues\n\nDelegate elsewhere when the user wants:\n- rendered PNG\u002FSVG images or polished mockups → [sf-diagram-nanobananapro](..\u002Fsf-diagram-nanobananapro\u002FSKILL.md)\n- non-Salesforce systems only → use a more general diagramming skill\n- object discovery before an ERD → [sf-metadata](..\u002Fsf-metadata\u002FSKILL.md)\n\n---\n\n## Supported Diagram Families\n\n| Type | Preferred Mermaid form | Typical use |\n|---|---|---|\n| OAuth \u002F auth flows | `sequenceDiagram` | Authorization Code, JWT, PKCE, Device Flow |\n| ERD \u002F data model | `flowchart LR` | object relationships and sharing context |\n| integration sequence | `sequenceDiagram` | request\u002Fresponse or event choreography |\n| system landscape | `flowchart` | high-level architecture |\n| role \u002F access hierarchy | `flowchart` | users, profiles, permissions |\n| Agentforce behavior map | `flowchart` | agent → topic → action relationships |\n\n---\n\n## Required Context to Gather First\n\nAsk for or infer:\n- diagram type\n- scope and entities \u002F systems involved\n- output preference: Mermaid only, ASCII only, or both\n- whether styling should be minimal, documentation-first, or presentation-friendly\n- for ERDs: whether org metadata is available for grounding\n\n---\n\n## Recommended Workflow\n\n### 1. Pick the right diagram structure\n- use `sequenceDiagram` for time-ordered interactions\n- use `flowchart LR` for ERDs and capability maps\n- keep a single primary story per diagram when possible\n\n### 2. Gather data\nFor ERDs and grounded diagrams:\n- use [sf-metadata](..\u002Fsf-metadata\u002FSKILL.md) when real schema discovery is needed\n- optionally use the local metadata helper script for counts \u002F relationship context when appropriate\n\n### 3. Generate Mermaid first\nApply:\n- accurate labels\n- simple readable node text\n- consistent relationship notation\n- restrained styling that renders cleanly in markdown viewers\n\n### 4. Add ASCII fallback when useful\nProvide an ASCII version when the user wants terminal compatibility or plaintext documentation.\n\n### 5. Explain the diagram briefly\nCall out the key relationships, flow direction, and any assumptions.\n\n---\n\n## High-Signal Rules\n\n### For sequence diagrams\n- use `autonumber` when step order matters\n- distinguish requests vs responses clearly\n- use notes sparingly for protocol detail\n\n### For ERDs\n- prefer `flowchart LR`\n- keep object cards simple\n- use clear relationship arrows\n- avoid field overload unless the user explicitly asks for field-level detail\n- color-code object types only when it improves readability\n\n### For ASCII output\n- keep width reasonable\n- align arrows and boxes consistently\n- optimize for readability over decoration\n\n---\n\n## Output Format\n\n````markdown\n## \u003CDiagram Title>\n\n### Mermaid Diagram\n```mermaid\n\u003Cdiagram>\n```\n\n### ASCII Fallback\n```text\n\u003Cascii>\n```\n\n### Notes\n- \u003Ckey point>\n- \u003Cassumption or limitation>\n````\n\n---\n\n## Cross-Skill Integration\n\n| Need | Delegate to | Reason |\n|---|---|---|\n| real object \u002F field definitions | [sf-metadata](..\u002Fsf-metadata\u002FSKILL.md) | grounded ERD generation |\n| rendered diagram \u002F image output | [sf-diagram-nanobananapro](..\u002Fsf-diagram-nanobananapro\u002FSKILL.md) | visual polish beyond Mermaid |\n| connected-app auth setup context | [sf-connected-apps](..\u002Fsf-connected-apps\u002FSKILL.md) | accurate OAuth flows |\n| Agentforce logic visualization | [sf-ai-agentscript](..\u002Fsf-ai-agentscript\u002FSKILL.md) | source-of-truth behavior details |\n| Flow behavior diagrams | [sf-flow](..\u002Fsf-flow\u002FSKILL.md) | actual Flow logic grounding |\n\n---\n\n## Reference Map\n\n### Start here\n- [references\u002Fdiagram-conventions.md](references\u002Fdiagram-conventions.md)\n- [references\u002Fmermaid-reference.md](references\u002Fmermaid-reference.md)\n- [references\u002Fusage-examples.md](references\u002Fusage-examples.md)\n\n### Styling \u002F ERD specifics\n- [references\u002Fmermaid-styling.md](references\u002Fmermaid-styling.md)\n- [references\u002Fcolor-palette.md](references\u002Fcolor-palette.md)\n- [references\u002Ferd-conventions.md](references\u002Ferd-conventions.md)\n\n### Preview\n- [references\u002Fpreview-guide.md](references\u002Fpreview-guide.md)\n- [scripts\u002Fmermaid_preview.py](scripts\u002Fmermaid_preview.py)\n- [scripts\u002Fquery-org-metadata.py](scripts\u002Fquery-org-metadata.py)\n\n---\n\n## Score Guide\n\n| Score | Meaning |\n|---|---|\n| 72–80 | production-ready diagram |\n| 60–71 | clear and useful with minor polish left |\n| 48–59 | functional but could be clearer |\n| 35–47 | needs structural improvement |\n| \u003C 35 | inaccurate or incomplete |\n",{"name":5,"license":15,"metadata":24,"description":28,"compatibility":29},{"author":25,"scoring":26,"version":27},"Jag Valaiyapathy","80 points across 5 categories","1.2.0","Salesforce architecture diagrams using Mermaid with ASCII fallback. TRIGGER when: user says \"diagram\", \"visualize\", \"ERD\", or asks for sequence diagrams, flowcharts, class diagrams, or architecture visualizations in Mermaid. DO NOT TRIGGER when: user wants PNG\u002FSVG image output (use sf-diagram-nanobananapro), or asks about non-Salesforce systems.\n","Requires Mermaid-capable renderer for diagram previews","main","8859218955d9504cd18b59e7892100718039d3b4","data\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-diagram-mermaid",1,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper","https:\u002F\u002Fgithub.com\u002Fom-scogo","SDE-1 @ Scogo ","2026-07-18 12:22:46",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add om-scogo\u002Fskillsh-scraper --skill sf-diagram-mermaid",{"tool":44,"command":45},"bunx","bunx skills add om-scogo\u002Fskillsh-scraper --skill sf-diagram-mermaid",{"tool":47,"command":48},"pnpm","pnpm dlx skills add om-scogo\u002Fskillsh-scraper --skill sf-diagram-mermaid","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-diagram-mermaid\u002FSkill.md",true,[52],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"metadata.json","REFERENCE","参考文档",447,"https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fjaganpro-sf-skills\u002Fsf-diagram-mermaid\u002Fmetadata.json",[59,66,71,78,83,90],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M7D6MC9FAAEV4CMNYX8W7JTG","arxiv-search","Search arXiv physics, math, and computer science preprints using natural language queries. Powered by Valyu semantic search.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002Fskills\u002Farxiv-search\u002FSKILL.md",[],[],{"skillNo":67,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7D6M85CKKN87TA98VCQV4H7","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fyorkeccak-scientific-skills\u002Farxiv-search\u002FSkill.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7D4ZTCS4DR3CE4JY06X84T2","working-with-legacy-code","Safely change and test untested codebases using Feathers' \"Working Effectively with Legacy Code\". Use when the user mentions \"legacy code\", \"no tests\", \"untested codebase\", \"how do I test this\", \"seams\", \"characterization tests\", \"golden master\", \"sprout method\", \"afraid to change this code\", \"monster method\", \"dependency breaking\", or \"inherited a messy codebase\". Also trigger when changing code without tests safely, getting a class under test when constructors, statics, or singletons block it, adding features to tangled modules, or planning incremental test coverage for an old codebase. Covers the legacy-code change algorithm, seams, characterization tests, sprout\u002Fwrap, and dependency-breaking techniques. For refactoring code that already has tests, see refactoring-patterns. For day-to-day code quality, see clean-code.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002Fworking-with-legacy-code\u002FSKILL.md",[],[],{"skillNo":79,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M7D4ZHZKJD2RSNGAF63V14P4","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fworking-with-legacy-code\u002FSkill.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M7D4ZB4CJBFW5JE67CPH2QRV","web-typography","Select, pair, and implement typefaces for web projects. Use when the user mentions \"font pairing\", \"which typeface\", \"line height\", \"responsive typography\", \"web font loading\", \"type hierarchy\", \"variable fonts\", \"FOUT\u002FFOIT\", \"typographic scale\", or \"the text is hard to read\". Also trigger when choosing between system fonts and web fonts, optimizing font-loading performance, or designing readable long-form content. Covers readability evaluation, CSS implementation, and performance optimization. For overall UI design systems, see refactoring-ui. For dramatic typographic experiences, see top-design.","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002Fweb-typography\u002FSKILL.md",[],[],{"skillNo":91,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7D4Z4MVYVY3NMJ18BNV6WNA","https:\u002F\u002Fgithub.com\u002Fom-scogo\u002Fskillsh-scraper\u002Fblob\u002Fmain\u002Fdata\u002Fskills\u002Fwondelai-skills\u002Fweb-typography\u002FSkill.md",[],[]]