{"id":40686,"plugin_id":"plugin_asdk_app_6a172ed01fd4819188c0cbd26e01ced6","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T12:55:15.931Z","digest":"7d8904ad596ca47d5af5950eba6014aaf6e51beab317a2d7c7ff08d644c3e0b0","against":null,"payload":{"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.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":428}],"name":"review-mdedit-document","skill_md_contents":"---\nname: review-mdedit-document\ndescription: 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.\ncompatibility: Requires the mdedit MCP server with article read and review tools.\n---\n\n# Review 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 saved document, then leave focused feedback without changing the writer's Markdown.\n\n1. 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.\n2. Call `read_article` for the selected document. Use its current saved content as the only source for the review.\n3. Call `list_review_threads` so you do not duplicate existing feedback.\n4. Add only useful, non-duplicative review items:\n   - Use `add_comment` for a question, concern, or explanation.\n   - Use `add_suggestion` for a concrete replacement that the writer can accept or reject.\n   - Anchor each item to a unique quote with nearby context when needed.\n   - Generate one globally unique UUID `commandId` per mutation and reuse that exact value if the same mutation is retried.\n5. 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.\n\nWhen the user asks to accept or reject review feedback:\n\n1. 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.\n2. 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`.\n3. Confirm the decision conversationally only when the tool returns `applied: true`.\n\nReview 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 when the tool returns `applied: true`. If an anchor is ambiguous or changed, read the document again and ask one focused question instead of guessing.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}