Update to Markdown by mdedit.ai

{
  "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\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"
}