{"id":89866,"plugin_id":"plugin_asdk_app_69c597eebdd4819194fd9c4d03acedb6","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-11T00:08:00.161Z","digest":"2fedc9cd7802f4bf6f382de2c7a73457e5ca0bc9e9b25172cf28e27badef44b3","against":null,"payload":{"description":"Use when working with Lucidchart or Lucidspark tasks: search/list documents, fetch or summarize content, create or edit diagrams, export, share, comment, or work with Lucid IDs/URLs through the Lucid MCP.","included_files":[],"name":"lucid","skill_md_contents":"---\nname: lucid\ndescription: 'Use when working with Lucidchart or Lucidspark tasks: search/list documents, fetch or summarize content, create or edit diagrams, export, share, comment, or work with Lucid IDs/URLs through the Lucid MCP.'\n---\n\n# Lucid\n\nUse the currently exposed Lucid MCP tools as the source of truth.\n\n## Workflow\n\n1. Match the user's goal to the most specific available Lucid MCP tool.\n2. Prefer stable IDs or URLs. Search/list before asking when discovery is possible.\n3. Read any required `lucid://...` resource before calling a tool that requires it.\n4. Fetch current document/page/item state before editing existing content.\n5. Ask for one missing source artifact when creation or modification depends on unavailable input.\n6. Confirm before destructive actions, bulk changes, broad permission changes, or anonymous share links.\n7. Report the affected document/page/item/thread IDs, returned URLs, exported files, and key assumptions.\n\n## Intent Routing\n\n- For discovery, history, folders, or unknown documents, use search/list tools before asking for an ID.\n- For large documents, search distinctive text first, then fetch only the relevant page or region when possible.\n- For document understanding, fetch the smallest useful scope and summarize only MCP-provided content.\n- For edits, fetch or search first to identify current page/item IDs and nearby context.\n- For creation, use the most specific creator available. For general diagram/import tools, follow all tool prerequisites and required resources.\n- For export, sharing, comments, or collaboration, prefer exact document/thread IDs and report returned files, URLs, roles, or comment IDs.\n\n## Source Dependency Gate\n\n- Before creating or modifying Lucid content, check whether the request depends on an unavailable source artifact such as an uploaded file, link, spreadsheet, PDF, image, selected content, prior diagram, or pasted text.\n- If required source content is missing, ask one concise question for it. Do not generate a generic substitute.\n\n## Guardrails\n\n- Treat MCP responses as ground truth. Do not invent document contents, object IDs, resource names, supported shapes, or tool capabilities.\n- Use Lucid resource libraries when tool descriptions reference them.\n- Read current document state before editing existing content.\n- Re-fetch or otherwise verify after meaningful edits when practical.\n- Confirm first when the operation is destructive, broad, permission-related, anonymous-sharing-related, or ambiguous in scope.\n\n## Reporting\n\n- For read-only work, report the key result, including when nothing matched.\n- For creation or edits, name what changed and include relevant document/page/item/thread IDs, returned URLs or files, and any layout, routing, or source assumptions.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}