Update to DeeplyClear

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,35 +1,42 @@
 ---
 name: deeplyclear
-description: Create interactive, editable, shareable mind maps and mindmaps in DeeplyClear. Use whenever the user mentions DeeplyClear or asks to create, generate, visualize, structure, organize, map, or transform a topic, conversation, research, plan, document, codebase, or messy notes into a mind map, mindmap, concept map, knowledge map, systems map, idea map, argument map, research map, visual map, architecture map, or codebase map. Also use for requests to visualize relationships or turn complex information into a navigable map, even without the words "mind map." Return a visual preview and editable link. Do not use when the user specifically asks for a static image, illustration, poster, or infographic.
+description: Create, edit, and resume interactive, saved mind maps in DeeplyClear. Use for mindmap, concept map, research map, architecture map, or codebase map requests, and follow-up requests to refine an existing DeeplyClear map. Also use when the user wants complex information or relationships organized into a navigable map. Do not use for general questions about DeeplyClear, product analytics, troubleshooting without map work, or specifically requested static images, posters, or infographics.
 ---
 
 # DeeplyClear
 
-Create a useful saved map and return both its visual preview and editable DeeplyClear link.
+Help the user create a useful saved map and continue developing it across requests. Return its visual preview and editable link.
 
-## Workflow
+## Choose the right action
 
-1. Inspect the source material before creating the map.
-   - For a topic, conversation, plan, document, research, or notes, identify the main concepts, supporting details, and relationships.
-   - For a repository or codebase, read relevant guidance such as `AGENTS.md`; identify languages, frameworks, manifests, entry points, subsystems, dependencies, data flows, and external services.
-2. Choose a structure that matches the source material.
-   - Use a clear hierarchy with concise node labels and preserve important relationships.
-   - For broad or ambiguous topics, create a useful balanced overview without asking unnecessary setup questions.
-   - For a repository or codebase, use the repository as the root and branch into the important architectural concerns, such as entry points, core services, data and events, external services, and cross-cutting concerns.
-   - Show representative data or control flows as cross-links between those branches.
-   - Do not collapse distinct ideas or code paths into one chain. Use a linear map only when the source genuinely describes one sequence.
-3. Call `deeplyclear_create_map` with a prompt that includes:
-   - a concise map title and purpose;
-   - the important systems or concepts;
-   - their hierarchy and relationships;
-   - key data or control flows;
-   - external dependencies and cross-cutting concerns when relevant.
-   - Keep visibility private unless the user explicitly requests a public map.
-4. Inspect the returned structure and preview.
-   - Confirm the map covers the requested scope and has meaningful branches and relationships.
-   - For a codebase map, confirm the requested architectural dimensions are represented and the result is not unjustifiably linear.
-   - If needed, refine the saved map with `deeplyclear_edit_map`.
-   - If creation did not return a visual preview, call `deeplyclear_preview_map`.
-5. Return the visual preview, editable map link, and a brief statement of the represented scope.
+- **New map:** inspect the available source material and call `deeplyclear_create_map`. Use the conversation or supplied material without asking the user to paste it again. For a broad topic, make a useful balanced overview without unnecessary setup questions.
+- **Follow-up edit:** “simplify it,” “add examples,” “add these notes,” and “expand this branch” normally refer to the current map. Reuse its ID from the current conversation or tool result. Use `deeplyclear_edit_map` for broad changes, `deeplyclear_elaborate_node` for one node, or fetch the map with `deeplyclear_get_map` and use the explicit node or edge tools for exact changes. Preserve unrelated content and visibility. Do not create a replacement unless requested.
+- **Resume saved work:** use `deeplyclear_list_maps` to find the requested map, then `deeplyclear_get_map` to inspect it. Match the user's title or topic; ask a short clarification when several plausible maps remain. Do not assume the newest map is the intended one when the user names another.
+- **Share:** distinguish a link the owner can open from access for other people. Use `deeplyclear_set_map_visibility` only when public or private access is explicitly requested. If the user says “share” without a clear audience or access choice, explain that a private map's link requires owner access and clarify before making it public. Public maps may appear in community discovery. Never promise unlisted or invitation-only sharing unless the tools support it.
 
-Do not substitute Mermaid or a prose-only outline when `deeplyclear_create_map` is available. If DeeplyClear is not connected or authenticated, explain the required connection and retry after access is available.
+For exact changes, use `deeplyclear_create_node`, `deeplyclear_update_node`, `deeplyclear_delete_node`, `deeplyclear_create_edge`, or `deeplyclear_delete_edge`. Each performs one action; use exact IDs from the latest map result. Deleting a node also removes its connected edges but keeps other nodes. Remove nodes or edges only when the user requests it.
+
+Use tools available in the current client. If editing or retrieval tools are unavailable, say so and offer the existing editable link; do not create a duplicate as a workaround.
+
+## Create and refine a useful map
+
+1. Identify the main concepts, supporting details, and relationships from the source. For a repository, read relevant guidance such as `AGENTS.md` and inspect its entry points, systems, dependencies, and data flows.
+2. Choose a clear hierarchy with concise labels. Preserve relationships across branches; do not collapse distinct ideas or code paths into one chain. Use a linear map only for a genuinely sequential source.
+3. Supply the map's purpose, important concepts, hierarchy, and relationships in the creation prompt. For codebases, include representative data/control flows, external dependencies, and cross-cutting concerns. Keep maps private unless public access is explicitly requested.
+4. Inspect the returned structure and preview for scope and meaningful branches. Make a focused correction if needed. Do not repeatedly regenerate a satisfactory map for minor stylistic preferences. If a successful result lacks a preview, use `deeplyclear_preview_map` when available.
+
+Do not substitute Mermaid or a prose-only outline for a requested DeeplyClear map when its creation tool is available.
+
+## Complete the handoff
+
+- Show the preview and editable link. Prefer opening the interactive editor; offer the animated tour when relevant to presenting or exploring the map.
+- Confirm that the map was saved only after a successful tool result. State the actual returned visibility; do not assume an existing map is private.
+- After an edit, briefly say what changed and that it is the same saved map.
+- When helpful, suggest one specific next refinement grounded in its content, such as “You can ask me to expand the risks branch.” Make it an optional suggestion, not an automatic edit or a required question.
+- Explain how to find this map again when the user asks. Use its title and saved link; do not promise that a future conversation remembers its ID.
+
+## Recover without losing the task
+
+If a tool requires authentication or reauthentication, use its returned connection link; otherwise offer [DeeplyClear in ChatGPT](https://chatgpt.com/plugins/plugin_asdk_app_6a571a2e0e7c819184208e1c2d6e8062). Briefly explain the connection step and retain the pending topic or edit and map ID in the current conversation. After the user confirms reconnection, resume that task without asking them to repeat it. If authentication fails again, explain the blocker instead of looping.
+
+For an uncertain creation outcome, check available saved maps before retrying so a response failure does not create duplicates. Never claim a map was saved if the result does not establish that.