Skip to main content

markdown-documents

Write or edit Markdown notes, reports and plain text; default for non-Office writing.

Source facts

Repository
agent0ai/agent-zero
Last source activity
September 8, 2026 at 00:37
Detected SKILL.md language
English
Stars
19,594
Forks
3,836

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

Showing SKILL.md

SKILL.md
Source instructions · Read-only preview
name
markdown-documents
description
Write or edit Markdown notes, reports and plain text; default for non-Office writing.
version
1.0.0
author
Agent Zero Core Team
tags
["markdown","md","documents","writing","notes","reports","briefs","editor"]
triggers
["markdown","md","note","brief","draft","report","editable writing"]
allowed_tools
["text_editor"]
# Markdown Documents Markdown is the default document format for normal writing, notes, reports, briefs, drafts, and collaborative text work unless the user explicitly asks for a binary office file. When they do ask for a LibreOffice office file, prefer ODF: ODT for Writer, ODS for Spreadsheet/Calc, and ODP for Presentation/Impress. Use DOCX, XLSX, or PPTX only for explicit OOXML compatibility. The Editor surface is user-owned UI. Create or update the saved Markdown file, but never open the Editor automatically. Set `open_in_canvas: true` only when the user explicitly asks to open the canvas/Editor; otherwise already-open Editor sessions refresh automatically. Keep the final response to the saved/updated result and path; do not write faux UI action labels such as "Open document" or "Download file", and do not add a note saying the canvas was not opened automatically unless the user explicitly asks about UI behavior. ## Workflow 1. Decide whether a saved editable artifact is useful. Create one for substantial, reusable, or collaborative writing; do not create one for tiny one-shot edits or answers that can be completed cleanly in chat. 2. Create Markdown with `text_editor` using `action: "write"` and an explicit `.md` path. 3. For edits to an existing Markdown file, read first when content matters, then use `patch` for targeted changes or `write` for deliberate full replacement. 4. Report the saved file path briefly. Do not say it was opened unless the user explicitly opened it. Minimal create: ```json { "tool_name": "text_editor", "tool_args": { "action": "write", "path": "/a0/usr/workdir/Project Brief.md", "content": "# Project Brief\n\nDraft text here." } } ``` Practical rules: - Prefer Markdown over ODT/DOCX for writing unless a binary Writer/Word file is explicitly needed. - Keep agent-only cleanup simple: if the user asks to fix a typo, update the file and finish; do not force a document-editor workflow. - Use clear headings and Markdown tables when they improve editability. - The Markdown Editor surface is available through the response file card.
View on GitHub