{"id":89867,"plugin_id":"plugin_asdk_app_69c597eebdd4819194fd9c4d03acedb6","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-11T00:08:00.201Z","digest":"530d02489c7a9f3c6a711fa149bd39a07365c5fdd66e1da05946e659bc96452a","against":null,"payload":{"description":"Create an editable Lucid flowchart to show the steps and decision branches of a process. Use when a flowchart is the intended diagram type.","included_files":[],"name":"lucid-create-flowchart","skill_md_contents":"---\nname: lucid-create-flowchart\ndescription: 'Create an editable Lucid flowchart to show the steps and decision branches of a process. Use when a flowchart is the intended diagram type.'\nuser-invocable: true\nmetadata:\n    version: 1.0\n    author: 'Lucid Software'\n---\n\n# Create Flowchart\n\nCreate an editable Lucid flowchart faithful to the user's source process.\n\n## Load MCP guidance\n\nUse `get_mcp_resource` to read `lucid://skills/readme`, then `lucid://skills/diagram-layout-flowchart` and its linked `lucid://skills/diagram-layout` resource before building. Follow those resources for flow planning, shape semantics, placement, decision labels, routing, and verification. Load current Script API documentation from `lucid_load_script_documentation` as directed there.\n\n## Creation conventions\n\n- Draw only steps, decisions, and outcomes supported by the source. State inferred steps as assumptions. If a branch's destination is unknown, end it at a terminator labeled with what is known.\n- Use the Flowchart shape library. Use specialized shapes only when the process calls for them, such as data input/output, manual operations, predefined subprocesses, documents, databases, or delays.\n- Show parallel work as branches that rejoin at an explicit join step; these are not decision exits and need no branch labels.\n- Prefer one page. Use off-page links only when the flow is too large to read on one page or multiple pages are requested.\n- Avoid emoji in labels; Lucid can render them as black boxes.\n- Name the document after the process, for example, \"Flowchart: Employee Onboarding\".\n\nUnless the user specifies colors, use these fills consistently:\n\n| Meaning                   | Fill      |\n| ------------------------- | --------- |\n| Start / end               | `#D1E7DD` |\n| Process step              | `#DCE8F7` |\n| Decision                  | `#FFF3CD` |\n| Exception or failure path | `#F8D7DA` |\n\nExplain colors and non-obvious shapes with small matching samples in a container titled \"Legend\", clear of the flow. Use consistent font sizes and centered labels. Include labeled line samples when line styles carry meaning.\n\n## Build and deliver\n\nFollow the loaded MCP guidance to validate and repair the created diagram. Report unresolved issues; if document classification blocks access, stop and share the link.\n\nReturn a brief summary of the flow, assumptions or unresolved source gaps, and the edit link.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}