← Plugin catalog
Productivity

Markdown by mdedit.ai

Vivek Kumar Maskara v0.2.2

Create and share Markdown docs

Create a free account to save this plugin.

From the developer

Declared capabilities

  • Read
  • Write

Declared limitations

  • The request does not ask to persist, retrieve, revise, or share content in mdedit.
  • Both the target and requested replacement are ambiguous.
  • The user explicitly declined public visibility.

Not specified in the available declarations: pricing & account requirements.

Onboarding example

Turn this conversation into a Markdown document and save it to mdedit.
Sources & dates

Developer declarations; not independently tested. Listing last checked Nov 19, 2026. Package observed Nov 19, 2026.

View package source →

Description

From the marketplace listing

Save conversation content as private Markdown Documents in mdedit, find, revise, and review saved work, and publish a public link only after explicit confirmation.

Language: English · Automatically detected from descriptions.

What changed

· 7 observations

Capabilities & instructions

Skill instructions changed from “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...” to “## Authentication Use the host's browser OAuth connection flow when authentication is needed. The hosted server...

View comparison →
Capabilities & instructions

Skill instructions changed from “Read the current durable content, then apply the smallest unambiguous anchored change. 1. Resolve the workspace and document using `list_workspaces`,...” to “## Authentication Use the host's browser OAuth connection flow when authentication is needed. The hosted server discovers...

View comparison →
Capabilities & instructions

Skill instructions changed from “Public visibility is a separate, explicit action. Never treat saving or editing as permission to publish. 1. Resolve the workspace and document using...” to “## Authentication Use the host's browser OAuth connection flow when authentication is needed. The hosted server discovers...

View comparison →
Capabilities & instructions

Skill instructions changed from “Resolve a real saved document before describing its content. 1. Resolve the workspace with `list_workspaces` unless a `workspaceId` from an earlier mdedit...” to “## Authentication Use the host's browser OAuth connection flow when authentication is needed. The hosted server discovers...

View comparison →
Capabilities & instructions

Is template instance added: “false”. App-6a172ed01fd4819188c0cbd26e01ced6 updated; open the comparison for details. Mdedit updated; open the comparison for details. Full description changed from “Create and save private Markdown documents in mdedit.ai directly from your conversation. Find and revise saved documents...

View comparison →
Capabilities & instructions

Is template instance added: “false”. App-6a172ed01fd4819188c0cbd26e01ced6 updated; open the comparison for details. Mdedit updated; open the comparison for details. Full description changed from “Create and save private Markdown documents in mdedit.ai directly from your conversation. Find and revise saved documents...

View comparison →

Technical updates · 1

Package or technical metadata updated

View technical comparison →

Similar plugins

Finding similar plugins… Results will appear here automatically.

Browse plugins →

Keywords

Files & skills

File archives

Plugin package15 files · 17.3 KBBrowse files →
Skill instructions
find-mdedit-document2.84 KB

View saved version →

---
name: find-mdedit-document
description: Find and read an existing Markdown Document stored in mdedit. Use when the user asks to locate, open, retrieve, quote, summarize, or inspect a saved mdedit document. Do not use for local files, web pages, or generic Markdown questions unrelated to mdedit storage.
compatibility: Requires the mdedit MCP server with workspace and article read tools.
---

# Find and read 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.


Resolve a real saved document before describing its content.

1. Resolve the workspace with `list_workspaces`.
   - If several workspaces could match, ask the user to choose by returned name.
   - If no workspace matches, stop without guessing.
2. Call `list_articles`. If exactly one workspace was returned, omit the workspace selector. If the user chose among several, pass `workspaceName`. When the user gives a title or keywords, pass them as `query`. Work from one bounded page at a time; do not retrieve every page merely to reproduce a long document list in chat.
3. Match the user's title or description against returned document metadata.
   - If there is one clear match, continue.
   - If several documents plausibly match, present only their returned titles and ask the user to choose.
   - If there is no match, say so and stop.
4. Call `read_article` with `articleTitle` and, when needed, `workspaceName`. Do not search local code or ask the user for routing identifiers.
5. For open, show, or preview requests, call `render_article` with `focus: preview`. Answer from the returned saved `content` when a textual answer is also needed. Distinguish exact saved content from any summary or interpretation. Keep `contentRevision`, `contentHash`, `workspaceId`, and `articleId` internal unless the user explicitly asks for diagnostic details.

This workflow is read-only. Do not call create, edit, publish, or unpublish tools. Never infer document content, identifiers, revisions, publication status, or URLs from titles or conversation memory.

Referenced files: 1 — file references are metadata, not package contents.

publish-mdedit-document3.54 KB

View saved version →

---
name: publish-mdedit-document
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.
compatibility: Requires the mdedit MCP server with publishing tools and explicit confirmation fields.
---

# 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`. 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.

Referenced files: 1 — file references are metadata, not package contents.

review-mdedit-document4.05 KB

View saved version →

---
name: review-mdedit-document
description: Review an existing Markdown Document in mdedit with anchored comments and suggestions, or accept or reject an existing suggestion. Use when the user asks to review, critique, proofread, suggest improvements, or decide pending review feedback on a saved mdedit document. Do not use when the user asks for an unrelated direct edit, publishing, or review of local or unsaved content.
compatibility: Requires the mdedit MCP server with article read and review tools.
---

# Review 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 saved document, then leave focused feedback without changing the writer's Markdown.

1. Resolve the workspace and document with `list_workspaces` and `list_articles`. 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 `query` when the user provides a title or keywords, and work from one bounded page at a time instead of retrieving every page. If several returned names plausibly match, ask the user to choose by name. Never ask the user for an internal ID unless troubleshooting requires it.
2. Call `read_article` for the selected document. Use its current saved content as the only source for the review.
3. Call `list_review_threads` so you do not duplicate existing feedback.
4. Add only useful, non-duplicative review items:
   - Use `add_comment` for a question, concern, or explanation.
   - Use `add_suggestion` for a concrete replacement that the writer can accept or reject.
   - Anchor each item to a unique quote with nearby context when needed.
   - Generate one globally unique UUID `commandId` per mutation and reuse that exact value if the same mutation is retried.
5. Call `render_article` with `focus: review` so the user can inspect and triage feedback. Summarize the review conversationally: state how many comments or suggestions were added and the main themes. Do not display `workspaceId`, `articleId`, `threadId`, `commandId`, hashes, revisions, or JSON unless the user explicitly asks for diagnostic details.

When the user asks to accept or reject review feedback:

1. Use the `suggestionId` and `targetId` already returned by `add_suggestion`, or call `list_review_threads` with `status: open` and match the user's description against the returned suggestions. Ask one focused question if more than one suggestion could match.
2. Generate one globally unique UUID `commandId`, then call `accept_suggestion` to atomically apply the replacement and mark it accepted, or `reject_suggestion` to close it without changing the document. Reuse the exact command ID if the same decision is retried. Never simulate acceptance with `edit_article` plus `resolve_thread`.
3. Confirm the decision conversationally only when the tool returns `applied: true`.

Review requests never imply permission to call `edit_article`, publish, or unpublish. Review tools work on ordinary documents; do not ask the user to enable collaboration. Treat a review mutation as successful only 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 1 — file references are metadata, not package contents.

revise-mdedit-document3.24 KB

View saved version →

---
name: revise-mdedit-document
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.
compatibility: Requires the mdedit MCP server with read_article and edit_article tools.
---

# 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`. 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. 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. 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.

Referenced files: 1 — file references are metadata, not package contents.

save-mdedit-document2.94 KB

View saved version →

---
name: save-mdedit-document
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.
compatibility: Requires the mdedit MCP server with list_workspaces and create_article tools.
---

# 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:
   - 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.

Referenced files: 1 — file references are metadata, not package contents.

Release notes

Updates all five skills with browser OAuth sign-in and workspace consent guidance without asking users to paste credentials. Includes the deployed CDN-backed inline Markdown reader, a compact Edit here / external-open / Export / More toolbar, keyboard-accessible menus, and removal of nested reader borders. Retains conflict-aware editing, scoped workspace access, export and review workflows, and explicit confirmation before public visibility changes.

Declared in the saved package. Remote tools may change independently.

Package details

Publisher declarations from the archived package. These are separate from our research and the live service's terms.

Package author
Vivek Kumar Maskara
Keywords
See keywords
Review scenarios
5 positive · 3 negativeScenario counts, not test results.

Declared capabilities

  • Read
  • Write

Package observed Nov 19, 2026.

Technical details
First seen
Sep 30, 2026 · 22:02 UTC
Last seen
Nov 19, 2026 · 12:00 UTC
Latest observed change
Oct 24, 2026 · 12:55 UTC
Collection status
Collected

plugin_asdk_app_6a172ed01fd4819188c0cbd26e01ced6

Download plugin data (JSON)

Plugin details: served from cache. Prepared . Refreshed when plugin data changes or after 6 hours. Your account and Follow status are live.