Skip to main content

markdown-documents

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

소스 정보

저장소
agent0ai/agent-zero
최근 소스 활동
2026년 9월 8일 00:37
감지된 SKILL.md 언어
영어
스타
19,486
포크
3,826

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
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.
GitHub에서 보기