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 publish-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
1. Resolve the workspace and document using `list_workspaces`, `list_articles`, and `read_article`. Ask the user to choose when a returned match is ambiguous. 2. Call `get_publish_status` before proposing a mutation. 3. For a status-only...
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,14 +6,20 @@ # Manage Public Document Publishing +## 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. + + Public visibility is a separate, explicit action. Never treat saving or editing as permission to publish. -1. Resolve the workspace and document using `list_workspaces`, `list_articles`, and `read_article`. Ask the user to choose when a returned match is ambiguous. -2. Call `get_publish_status` before proposing a mutation. -3. For a status-only request, report only the returned state and exact returned URL fields, then stop without mutating. -4. Before publishing or updating a public link, warn that anyone with the link can view the document and ask for explicit confirmation. Do not infer confirmation from an earlier save or edit request. -5. After confirmation, call `publish_article` with `confirmPublic: true`. Include a custom slug or SEO metadata only when the user supplied or approved it. -6. Treat publication as successful only when the tool returns `publishId`, `shortUrl`, `fullUrl`, and `publishedAt`. Return the exact tool-provided public URL; prefer `shortUrl` for sharing. -7. Before disabling a public link, identify the current returned link and ask for explicit confirmation. After confirmation, call `unpublish_article` with `confirmUnpublish: true`. +1. Resolve the workspace and document using `list_workspaces`, `list_articles`, and `read_article`. Omit the workspace selector when there is one workspace; otherwise pass the chosen `workspaceName`. Pass the chosen `articleTitle` to later tools instead of asking for internal identifiers. Use `list_articles.query` when the user provides a title or keywords, and work from one bounded page at a time instead of retrieving every page. Ask the user to choose when a returned match is ambiguous. +2. For a status-only request, call `get_publish_status`, then call `render_article` with `focus: publish`. Report only the returned state and exact URL fields, then stop without mutating. +3. Before publishing or updating a public link, warn that anyone with the link can view the document and ask for explicit confirmation. Do not infer confirmation from an earlier save or edit request. +4. After confirmation, generate one globally unique UUID `commandId` and call `publish_article` with that command ID and `confirmPublic: true`. Reuse the exact command ID if the call must be retried. The tool atomically defaults a new link to Live while preserving an existing link's mode, so do not add a status preflight. Include a custom slug or SEO metadata only when the user supplied or approved it. +5. Treat publication as successful only when the tool returns `publishId`, `shortUrl`, `fullUrl`, and `publishedAt`. Call `render_article` with `focus: publish`. Return the exact tool-provided public URL; prefer `shortUrl` for sharing. +6. Before disabling a public link, call `get_publish_status` to identify the current link and ask for explicit confirmation. After confirmation, generate one globally unique UUID `commandId`, call `unpublish_article` with that command ID and `confirmUnpublish: true`, and reuse the same command ID for any retry. Then refresh the publish component with `render_article`. Never construct an `mded.it` URL, expose an editor URL as a public link, or claim publication from a requested slug. On denied permission, failure, or missing result fields, report the bounded error and leave visibility unchanged.
Full technical diff · 1 changed fields
changed /skill_md_contents
"---\nname: publish-mdedit-document\ndescription: Check or change Public Document Publishing for an existing mdedit Markdown Document. Use when the user explicitly asks to publish, unpublish, inspect publication status, or create or update a public mded.it link. Do not use for private editor links, local files, or generic sharing advice.\ncompatibility: Requires the mdedit MCP server with publishing tools and explicit confirmation fields.\n---\n\n# Manage Public Document Publishing\n\nPublic visibility is a separate, explicit action. Never treat saving or editing as permission to publish.\n\n1. Resolve the workspace and document using `list_workspaces`, `list_articles`, and `read_article`. Ask the user to choose when a returned match is ambiguous.\n2. Call `get_publish_status` before proposing a mutation.\n3. For a status-only request, report only the returned state and exact returned URL fields, then stop without mutating.\n4. Before publishing or updating a public link, warn that anyone with the link can view the document and ask for explicit confirmation. Do not infer confirmation from an earlier save or edit request.\n5. After confirmation, call `publish_article` with `confirmPublic: true`. Include a custom slug or SEO metadata only when the user supplied or approved it.\n6. Treat publication as successful only when the tool returns `publishId`, `shortUrl`, `fullUrl`, and `publishedAt`. Return the exact tool-provided public URL; prefer `shortUrl` for sharing.\n7. Before disabling a public link, identify the current returned link and ask for explicit confirmation. After confirmation, call `unpublish_article` with `confirmUnpublish: true`.\n\nNever construct an `mded.it` URL, expose an editor URL as a public link, or claim publication from a requested slug. On denied permission, failure, or missing result fields, report the bounded error and leave visibility unchanged.\n"
"---\nname: publish-mdedit-document\ndescription: Check or change Public Document Publishing for an existing mdedit Markdown Document. Use when the user explicitly asks to publish, unpublish, inspect publication status, or create or update a public mded.it link. Do not use for private editor links, local files, or generic sharing advice.\ncompatibility: Requires the mdedit MCP server with publishing tools and explicit confirmation fields.\n---\n\n# Manage Public Document Publishing\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\nPublic visibility is a separate, explicit action. Never treat saving or editing as permission to publish.\n\n1. Resolve the workspace and document using `list_workspaces`, `list_articles`, and `read_article`. Omit the workspace selector when there is one workspace; otherwise pass the chosen `workspaceName`. Pass the chosen `articleTitle` to later tools instead of asking for internal identifiers. Use `list_articles.query` when the user provides a title or keywords, and work from one bounded page at a time instead of retrieving every page. Ask the user to choose when a returned match is ambiguous.\n2. For a status-only request, call `get_publish_status`, then call `render_article` with `focus: publish`. Report only the returned state and exact URL fields, then stop without mutating.\n3. Before publishing or updating a public link, warn that anyone with the link can view the document and ask for explicit confirmation. Do not infer confirmation from an earlier save or edit request.\n4. After confirmation, generate one globally unique UUID `commandId` and call `publish_article` with that command ID and `confirmPublic: true`. Reuse the exact command ID if the call must be retried. The tool atomically defaults a new link to Live while preserving an existing link's mode, so do not add a status preflight. Include a custom slug or SEO metadata only when the user supplied or approved it.\n5. Treat publication as successful only when the tool returns `publishId`, `shortUrl`, `fullUrl`, and `publishedAt`. Call `render_article` with `focus: publish`. Return the exact tool-provided public URL; prefer `shortUrl` for sharing.\n6. Before disabling a public link, call `get_publish_status` to identify the current link and ask for explicit confirmation. After confirmation, generate one globally unique UUID `commandId`, call `unpublish_article` with that command ID and `confirmUnpublish: true`, and reuse the same command ID for any retry. Then refresh the publish component with `render_article`.\n\nNever construct an `mded.it` URL, expose an editor URL as a public link, or claim publication from a requested slug. On denied permission, failure, or missing result fields, report the bounded error and leave visibility unchanged.\n"
Full snapshot data
{
"description": "Check or change Public Document Publishing for an existing mdedit Markdown Document. Use when the user explicitly asks to publish, unpublish, inspect publication status, or create or update a public mded.it link. Do not use for private editor links, local files, or generic sharing advice.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 423
}
],
"name": "publish-mdedit-document",
"skill_md_contents": "---\nname: publish-mdedit-document\ndescription: Check or change Public Document Publishing for an existing mdedit Markdown Document. Use when the user explicitly asks to publish, unpublish, inspect publication status, or create or update a public mded.it link. Do not use for private editor links, local files, or generic sharing advice.\ncompatibility: Requires the mdedit MCP server with publishing tools and explicit confirmation fields.\n---\n\n# Manage Public Document Publishing\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\nPublic visibility is a separate, explicit action. Never treat saving or editing as permission to publish.\n\n1. Resolve the workspace and document using `list_workspaces`, `list_articles`, and `read_article`. Omit the workspace selector when there is one workspace; otherwise pass the chosen `workspaceName`. Pass the chosen `articleTitle` to later tools instead of asking for internal identifiers. Use `list_articles.query` when the user provides a title or keywords, and work from one bounded page at a time instead of retrieving every page. Ask the user to choose when a returned match is ambiguous.\n2. For a status-only request, call `get_publish_status`, then call `render_article` with `focus: publish`. Report only the returned state and exact URL fields, then stop without mutating.\n3. Before publishing or updating a public link, warn that anyone with the link can view the document and ask for explicit confirmation. Do not infer confirmation from an earlier save or edit request.\n4. After confirmation, generate one globally unique UUID `commandId` and call `publish_article` with that command ID and `confirmPublic: true`. Reuse the exact command ID if the call must be retried. The tool atomically defaults a new link to Live while preserving an existing link's mode, so do not add a status preflight. Include a custom slug or SEO metadata only when the user supplied or approved it.\n5. Treat publication as successful only when the tool returns `publishId`, `shortUrl`, `fullUrl`, and `publishedAt`. Call `render_article` with `focus: publish`. Return the exact tool-provided public URL; prefer `shortUrl` for sharing.\n6. Before disabling a public link, call `get_publish_status` to identify the current link and ask for explicit confirmation. After confirmation, generate one globally unique UUID `commandId`, call `unpublish_article` with that command ID and `confirmUnpublish: true`, and reuse the same command ID for any retry. Then refresh the publish component with `render_article`.\n\nNever construct an `mded.it` URL, expose an editor URL as a public link, or claim publication from a requested slug. On denied permission, failure, or missing result fields, report the bounded error and leave visibility unchanged.\n"
}SHA-256 of public snapshot: 4b0350935a85b7cf3f287db405f0b22007c9b94f427941410a555f4579750c9d