Update to Markdown by mdedit.ai
Snapshot Oct 24, 2026 · 12:55 UTC · version 0.2.2
Collection source: downloaded plugin package. These snapshots do not have a confirmed matching collection source. Differences in file lists alone do not establish changes to the package.
Instructions updated for save-mdedit-document
Skill instructions — Now says: ## Authentication Use the host's browser OAuth connection flow when authentication is needed. The hosted server discovers Clerk and supports dynamic client...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Skill instructions
Sep 30, 2026 · 22:55 UTC
- Use an established `workspaceId` only when it came from an earlier mdedit tool result. - Otherwise call `list_workspaces`. - If exactly one workspace is returned, use it. If several are returned, ask the user which returned wo...
Oct 24, 2026 · 12:55 UTC
## Authentication Use the host's browser OAuth connection flow when authentication is needed. The hosted server discovers Clerk and supports dynamic client registration (DCR) and Client ID Metadata Documents (CIMD); a pre-registered host...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -6,15 +6,21 @@ # Save a document to mdedit +## Authentication + +Use the host's browser OAuth connection flow when authentication is needed. The hosted server discovers Clerk and supports dynamic client registration (DCR) and Client ID Metadata Documents (CIMD); a pre-registered host client or API key is not required for an OAuth-capable host. Ask the user to sign in and approve the workspace access shown by mdedit.ai. Available workspaces are selected by default, with read/write access when the request includes write scopes; the user can narrow access before approving. + +Do not ask the user to paste an access token, client secret, authorization code, or API key into chat. Use an existing scoped API-key connection only when the host cannot perform OAuth or the user explicitly chooses it. If a tool reports missing permissions, reconnect through the host to request the needed scopes/workspaces instead of repeatedly retrying the same denied call. + + Create one durable private document from content the user supplied or asked you to draft. 1. Determine the intended title and Markdown content. Ask a focused question if the source material or document boundary is unclear. 2. Resolve the destination workspace: - - Use an established `workspaceId` only when it came from an earlier mdedit tool result. - - Otherwise call `list_workspaces`. - - If exactly one workspace is returned, use it. If several are returned, ask the user which returned workspace name to use. If none are returned, stop. -3. Call `create_article` once with the returned `workspaceId`, title, complete Markdown content, and `collaborative: false` unless the user explicitly asks for live collaboration. -4. Treat the save as successful only when the tool returns `workspaceId`, `articleId`, `contentRevision`, `contentHash`, and `editorUrl`. -5. Report the saved title and exact returned `editorUrl`. State that the document remains private. + - Call `list_workspaces` unless the conversation has already established one by name. + - If exactly one workspace is returned, omit the workspace selector in later calls. If several are returned, ask the user which returned workspace name to use and pass it as `workspaceName`. If none are returned, stop. +3. Generate one globally unique UUID `commandId` for this save, then call `create_article` with that same command ID, the natural workspace selector above, title, complete Markdown content, and `collaborative: false` unless the user explicitly asks for live collaboration. Reuse the exact command ID if the call must be retried. +4. Treat the save as successful only when the tool returns the saved title, `editorUrl`, `contentHash`, and internal `contentRevision` metadata; keep routing, hash, and revision values out of the conversational response. +5. Call `render_article` with `focus: preview` so UI-capable hosts show the saved document. Report the saved title in one short sentence and use the exact returned editor URL when a link is useful. State that the document remains private. Never invent or reconstruct a workspace ID, document ID, revision, hash, or editor URL. Never call a publishing tool as part of this workflow. If creation fails or reports retained partial state, report that bounded failure and do not claim the document was saved.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: save-mdedit-document\ndescription: Create and durably save a private Markdown Document in mdedit. Use when the user explicitly asks to save, persist, archive, or turn conversation content into a document in mdedit. Do not use for generic Markdown writing, formatting, or local-file creation that does not require mdedit storage.\ncompatibility: Requires the mdedit MCP server with list_workspaces and create_article tools.\n---\n\n# Save a document to mdedit\n\nCreate one durable private document from content the user supplied or asked you to draft.\n\n1. Determine the intended title and Markdown content. Ask a focused question if the source material or document boundary is unclear.\n2. Resolve the destination workspace:\n - Use an established `workspaceId` only when it came from an earlier mdedit tool result.\n - Otherwise call `list_workspaces`.\n - If exactly one workspace is returned, use it. If several are returned, ask the user which returned workspace name to use. If none are returned, stop.\n3. Call `create_article` once with the returned `workspaceId`, title, complete Markdown content, and `collaborative: false` unless the user explicitly asks for live collaboration.\n4. Treat the save as successful only when the tool returns `workspaceId`, `articleId`, `contentRevision`, `contentHash`, and `editorUrl`.\n5. Report the saved title and exact returned `editorUrl`. State that the document remains private.\n\nNever invent or reconstruct a workspace ID, document ID, revision, hash, or editor URL. Never call a publishing tool as part of this workflow. If creation fails or reports retained partial state, report that bounded failure and do not claim the document was saved.\n"
"---\nname: save-mdedit-document\ndescription: Create and durably save a private Markdown Document in mdedit. Use when the user explicitly asks to save, persist, archive, or turn conversation content into a document in mdedit. Do not use for generic Markdown writing, formatting, or local-file creation that does not require mdedit storage.\ncompatibility: Requires the mdedit MCP server with list_workspaces and create_article tools.\n---\n\n# Save a document to mdedit\n\n## Authentication\n\nUse the host's browser OAuth connection flow when authentication is needed. The hosted server discovers Clerk and supports dynamic client registration (DCR) and Client ID Metadata Documents (CIMD); a pre-registered host client or API key is not required for an OAuth-capable host. Ask the user to sign in and approve the workspace access shown by mdedit.ai. Available workspaces are selected by default, with read/write access when the request includes write scopes; the user can narrow access before approving.\n\nDo not ask the user to paste an access token, client secret, authorization code, or API key into chat. Use an existing scoped API-key connection only when the host cannot perform OAuth or the user explicitly chooses it. If a tool reports missing permissions, reconnect through the host to request the needed scopes/workspaces instead of repeatedly retrying the same denied call.\n\n\nCreate one durable private document from content the user supplied or asked you to draft.\n\n1. Determine the intended title and Markdown content. Ask a focused question if the source material or document boundary is unclear.\n2. Resolve the destination workspace:\n - Call `list_workspaces` unless the conversation has already established one by name.\n - If exactly one workspace is returned, omit the workspace selector in later calls. If several are returned, ask the user which returned workspace name to use and pass it as `workspaceName`. If none are returned, stop.\n3. Generate one globally unique UUID `commandId` for this save, then call `create_article` with that same command ID, the natural workspace selector above, title, complete Markdown content, and `collaborative: false` unless the user explicitly asks for live collaboration. Reuse the exact command ID if the call must be retried.\n4. Treat the save as successful only when the tool returns the saved title, `editorUrl`, `contentHash`, and internal `contentRevision` metadata; keep routing, hash, and revision values out of the conversational response.\n5. Call `render_article` with `focus: preview` so UI-capable hosts show the saved document. Report the saved title in one short sentence and use the exact returned editor URL when a link is useful. State that the document remains private.\n\nNever invent or reconstruct a workspace ID, document ID, revision, hash, or editor URL. Never call a publishing tool as part of this workflow. If creation fails or reports retained partial state, report that bounded failure and do not claim the document was saved.\n"
Full snapshot data
{
"description": "Create and durably save a private Markdown Document in mdedit. Use when the user explicitly asks to save, persist, archive, or turn conversation content into a document in mdedit. Do not use for generic Markdown writing, formatting, or local-file creation that does not require mdedit storage.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 428
}
],
"name": "save-mdedit-document",
"skill_md_contents": "---\nname: save-mdedit-document\ndescription: Create and durably save a private Markdown Document in mdedit. Use when the user explicitly asks to save, persist, archive, or turn conversation content into a document in mdedit. Do not use for generic Markdown writing, formatting, or local-file creation that does not require mdedit storage.\ncompatibility: Requires the mdedit MCP server with list_workspaces and create_article tools.\n---\n\n# Save a document to mdedit\n\n## Authentication\n\nUse the host's browser OAuth connection flow when authentication is needed. The hosted server discovers Clerk and supports dynamic client registration (DCR) and Client ID Metadata Documents (CIMD); a pre-registered host client or API key is not required for an OAuth-capable host. Ask the user to sign in and approve the workspace access shown by mdedit.ai. Available workspaces are selected by default, with read/write access when the request includes write scopes; the user can narrow access before approving.\n\nDo not ask the user to paste an access token, client secret, authorization code, or API key into chat. Use an existing scoped API-key connection only when the host cannot perform OAuth or the user explicitly chooses it. If a tool reports missing permissions, reconnect through the host to request the needed scopes/workspaces instead of repeatedly retrying the same denied call.\n\n\nCreate one durable private document from content the user supplied or asked you to draft.\n\n1. Determine the intended title and Markdown content. Ask a focused question if the source material or document boundary is unclear.\n2. Resolve the destination workspace:\n - Call `list_workspaces` unless the conversation has already established one by name.\n - If exactly one workspace is returned, omit the workspace selector in later calls. If several are returned, ask the user which returned workspace name to use and pass it as `workspaceName`. If none are returned, stop.\n3. Generate one globally unique UUID `commandId` for this save, then call `create_article` with that same command ID, the natural workspace selector above, title, complete Markdown content, and `collaborative: false` unless the user explicitly asks for live collaboration. Reuse the exact command ID if the call must be retried.\n4. Treat the save as successful only when the tool returns the saved title, `editorUrl`, `contentHash`, and internal `contentRevision` metadata; keep routing, hash, and revision values out of the conversational response.\n5. Call `render_article` with `focus: preview` so UI-capable hosts show the saved document. Report the saved title in one short sentence and use the exact returned editor URL when a link is useful. State that the document remains private.\n\nNever invent or reconstruct a workspace ID, document ID, revision, hash, or editor URL. Never call a publishing tool as part of this workflow. If creation fails or reports retained partial state, report that bounded failure and do not claim the document was saved.\n"
}SHA-256 of public snapshot: eecfb9d815e8bb64e07ca3344299892f6f5dd91eaea21c0b69f2767debab8cf5