← Markdown by mdedit.aiCONTENT HISTORY

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.

WHAT CHANGED

Instructions updated for revise-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.

Save Markdown by mdedit.ai and check future changes in Following.

Up to 3 plugins free · no card required.

All fields and original values.

Skill instructions

Before

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 workspace or document match is ambiguous. 3. Build one or more `edit_article` operations: 6. Summa...

After

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 JSON

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -6,17 +6,24 @@
 
 # Revise a document in 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.
+
+
 Read the current durable content, then apply the smallest unambiguous anchored change.
 
-1. Resolve the workspace and document using `list_workspaces`, `list_articles`, and `read_article`. Ask the user to choose when a returned workspace or document match is ambiguous.
+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 workspace or document match is ambiguous.
 2. Confirm the requested change is specific enough to apply. Ask a focused question when the target text, section, or replacement is unclear.
-3. Build one or more `edit_article` operations:
+3. Generate one globally unique UUID `commandId` for the revision, then build one or more `edit_article` operations. Reuse the exact command ID if the call must be retried:
    - Prefer a unique `quote` anchor with nearby `context`.
    - Use `afterHeading`, `beforeHeading`, or `inSection` for section changes.
    - Use a numeric range only when it came from current tool-returned content.
    - Avoid whole-document replacement unless the user requests a full rewrite.
 4. Pass the current `contentHash` from `read_article` as `ifContentHash`.
 5. Treat the edit as successful only when the result has no conflicts and returns new durable `content`, `contentRevision`, and `contentHash`.
-6. Summarize what changed and report the returned revision.
+6. Call `render_article` with `focus: preview`, then summarize what changed in one or two conversational sentences. Do not display revisions, hashes, IDs, or JSON unless the user explicitly asks for diagnostic details.
 
 If the tool reports a hash mismatch or any conflict, stop, read the document again, and explain what changed concurrently. Do not retry against a new version without reconciling the user's intent. Never overwrite ambiguity, invent anchors, or claim success from requested text alone.
Full technical diff · 1 changed fields

changed /skill_md_contents

BEFORE
"---\nname: revise-mdedit-document\ndescription: Safely revise an existing Markdown Document stored in mdedit with anchored, conflict-aware edits. Use when the user asks to update, rewrite, correct, insert, remove, or reorganize content in a saved mdedit document. Do not use for unsaved local Markdown, local files, or generic editing advice.\ncompatibility: Requires the mdedit MCP server with read_article and edit_article tools.\n---\n\n# Revise a document in mdedit\n\nRead the current durable content, then apply the smallest unambiguous anchored change.\n\n1. Resolve the workspace and document using `list_workspaces`, `list_articles`, and `read_article`. Ask the user to choose when a returned workspace or document match is ambiguous.\n2. Confirm the requested change is specific enough to apply. Ask a focused question when the target text, section, or replacement is unclear.\n3. Build one or more `edit_article` operations:\n   - Prefer a unique `quote` anchor with nearby `context`.\n   - Use `afterHeading`, `beforeHeading`, or `inSection` for section changes.\n   - Use a numeric range only when it came from current tool-returned content.\n   - Avoid whole-document replacement unless the user requests a full rewrite.\n4. Pass the current `contentHash` from `read_article` as `ifContentHash`.\n5. Treat the edit as successful only when the result has no conflicts and returns new durable `content`, `contentRevision`, and `contentHash`.\n6. Summarize what changed and report the returned revision.\n\nIf the tool reports a hash mismatch or any conflict, stop, read the document again, and explain what changed concurrently. Do not retry against a new version without reconciling the user's intent. Never overwrite ambiguity, invent anchors, or claim success from requested text alone.\n"
AFTER
"---\nname: revise-mdedit-document\ndescription: Safely revise an existing Markdown Document stored in mdedit with anchored, conflict-aware edits. Use when the user asks to update, rewrite, correct, insert, remove, or reorganize content in a saved mdedit document. Do not use for unsaved local Markdown, local files, or generic editing advice.\ncompatibility: Requires the mdedit MCP server with read_article and edit_article tools.\n---\n\n# Revise a document in 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\nRead the current durable content, then apply the smallest unambiguous anchored change.\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 workspace or document match is ambiguous.\n2. Confirm the requested change is specific enough to apply. Ask a focused question when the target text, section, or replacement is unclear.\n3. Generate one globally unique UUID `commandId` for the revision, then build one or more `edit_article` operations. Reuse the exact command ID if the call must be retried:\n   - Prefer a unique `quote` anchor with nearby `context`.\n   - Use `afterHeading`, `beforeHeading`, or `inSection` for section changes.\n   - Use a numeric range only when it came from current tool-returned content.\n   - Avoid whole-document replacement unless the user requests a full rewrite.\n4. Pass the current `contentHash` from `read_article` as `ifContentHash`.\n5. Treat the edit as successful only when the result has no conflicts and returns new durable `content`, `contentRevision`, and `contentHash`.\n6. Call `render_article` with `focus: preview`, then summarize what changed in one or two conversational sentences. Do not display revisions, hashes, IDs, or JSON unless the user explicitly asks for diagnostic details.\n\nIf the tool reports a hash mismatch or any conflict, stop, read the document again, and explain what changed concurrently. Do not retry against a new version without reconciling the user's intent. Never overwrite ambiguity, invent anchors, or claim success from requested text alone.\n"
Full snapshot data
{
  "description": "Safely revise an existing Markdown Document stored in mdedit with anchored, conflict-aware edits. Use when the user asks to update, rewrite, correct, insert, remove, or reorganize content in a saved mdedit document. Do not use for unsaved local Markdown, local files, or generic editing advice.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 411
    }
  ],
  "name": "revise-mdedit-document",
  "skill_md_contents": "---\nname: revise-mdedit-document\ndescription: Safely revise an existing Markdown Document stored in mdedit with anchored, conflict-aware edits. Use when the user asks to update, rewrite, correct, insert, remove, or reorganize content in a saved mdedit document. Do not use for unsaved local Markdown, local files, or generic editing advice.\ncompatibility: Requires the mdedit MCP server with read_article and edit_article tools.\n---\n\n# Revise a document in 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\nRead the current durable content, then apply the smallest unambiguous anchored change.\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 workspace or document match is ambiguous.\n2. Confirm the requested change is specific enough to apply. Ask a focused question when the target text, section, or replacement is unclear.\n3. Generate one globally unique UUID `commandId` for the revision, then build one or more `edit_article` operations. Reuse the exact command ID if the call must be retried:\n   - Prefer a unique `quote` anchor with nearby `context`.\n   - Use `afterHeading`, `beforeHeading`, or `inSection` for section changes.\n   - Use a numeric range only when it came from current tool-returned content.\n   - Avoid whole-document replacement unless the user requests a full rewrite.\n4. Pass the current `contentHash` from `read_article` as `ifContentHash`.\n5. Treat the edit as successful only when the result has no conflicts and returns new durable `content`, `contentRevision`, and `contentHash`.\n6. Call `render_article` with `focus: preview`, then summarize what changed in one or two conversational sentences. Do not display revisions, hashes, IDs, or JSON unless the user explicitly asks for diagnostic details.\n\nIf the tool reports a hash mismatch or any conflict, stop, read the document again, and explain what changed concurrently. Do not retry against a new version without reconciling the user's intent. Never overwrite ambiguity, invent anchors, or claim success from requested text alone.\n"
}

SHA-256 of public snapshot: 87d056f5444e6fd9127e56d6e6ade215b0fafd889a469d9a091735805e7872d8