doc
/doc
Open a file in workshop's preview pane, the center column, where markdown renders, `- [ ]` task boxes are clickable and save to disk, and an edit toggle makes any text file editable in place (⌘S saves). Use INSTEAD OF macOS `open` whenever the user should read, tick off or edit a file: "open the checklist", "show me the notes", "let me edit that", or after you write a plan, checklist or notes file they will work through. The CLI is `node "$WORKSHOP_DOC" open <path> [--line N]`.
- Author
- DoshaLabs ↗
- Repository
- workshop ↗
- Licence
- MIT
- Last repository change
- 12.11.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Open a file in workshop's preview pane, the center column, where markdown renders, `- [ ]` task boxes are clickable and save to disk, and an edit toggle makes any text file editable in place (⌘S saves). Use INSTEAD OF macOS `open` whenever the user should read, tick off or edit a file: "open the checklist", "show me the notes", "let me edit that", or after you write a plan, checklist or notes file they will work through. The CLI is `node "$WORKSHOP_DOC" open <path> [--line N]`.
Triggers from the description
Original author description
Open a file in workshop's preview pane, the center column, where markdown renders, `- [ ]` task boxes are clickable and save to disk, and an edit toggle makes any text file editable in place (⌘S saves). Use INSTEAD OF macOS `open` whenever the user should read, tick off or edit a file: "open the checklist", "show me the notes", "let me edit that", or after you write a plan, checklist or notes file they will work through. The CLI is `node "$WORKSHOP_DOC" open <path> [--line N]`.
How it works
SKILL.md has no level-two headings · 28 lines, 240 words
SKILL.md preview
---
name: doc
description: Open a file in workshop's preview pane, the center column, where markdown renders, `- [ ]` task boxes are clickable and save to disk, and an edit toggle makes any text file editable in place (⌘S saves). Use INSTEAD OF macOS `open` whenever the user should read, tick off or edit a file: "open the checklist", "show me the notes", "let me edit that", or after you write a plan, checklist or notes file they will work through. The CLI is `node "$WORKSHOP_DOC" open <path> [--line N]`.
---
# Put the file in front of them, in workshop
```bash
node "$WORKSHOP_DOC" open notes/checklist.md # relative to your cwd; ~/ and absolute work too
node "$WORKSHOP_DOC" open src/main/index.ts --line 120 # scrolled to line 120, which is marked; path:120 works too
```
It prints JSON, `{ "path": …, "kind": "markdown", "editable": true }`, once the file is up.
On a refusal (no such file, not inside workshop) it says why on stderr and exits 1.
**Use this, not `open`, for a file the user should read or edit.** `open` sends a `.md` to
whatever app macOS picked, away from workshop. The preview pane is where they already are.
What they get there:
- Markdown rendered (a `source` toggle shows it as written); code and plain text in a mono face
with line numbers.
- `- [ ]` / `- [x]` items are checkboxes: a click rewrites that one character on disk and
nothing else, so a checklist you write is one they can tick off.
- `edit` turns the file into a plain editor; ⌘S saves.
- If the file changes on disk while it is open, the pane reloads it, unless they have unsaved
edits: then it says so and leaves their edits alone. So tell them before you rewrite a file
they are editing.
Folders, binaries and files over 2 MB are refused politely; use `open` for those, or when the
user asks for a particular app.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · DoshaLabs/workshop | 96 | MIT |
| boshu2/agentops | 100 | Apache-2.0 |
| davila7/claude-code-templates | 100 | MIT |
| boshu2/agentops | 100 | Apache-2.0 |
| PracticalSwan/agent-skills | 100 | MIT |
| nrdxp/predicate | 100 | MIT |
| tpc-pascal/skillsmith | 90 | MIT |
Database snapshot: 13.11.2026 · package version 9308f01edfc5 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100checklist
Run a **repeatable checklist / to-do list** from a markdown file of `- [ ]` items — execute the open items, tick them `[x]`, and write the file back. Re-running resumes only the still-open items, so the file IS the durable, repeatable state. USE for a generic user to-do that… - 100plan-local-storage
Persist plans to local project storage under .plans and open the saved markdown file in an existing Neovim pane in the current Herdr tab when available. Use when a user asks to save a plan, write a plan file locally, or open a saved plan in Neovim. - 100md-open-local
Use when the user wants to open/view a Markdown file LOCALLY on the Mac (e.g. "이 md 로컬에서 열어줘", "open this md locally") — opens it in the macOS default app via the `open` CLI. For viewing over remote control instead, use md-view-remote. - 100interactive-page
Open what the user must read, approve, tick or choose (a red-pen draft file, an over-to-you checklist, a question with options) as a page in their browser, and write their answers back into the file. Use whenever a skill hands the user a file to edit or tick, and whenever a… - 100obsidian-cli
Drive a running Obsidian instance via the `obsidian` CLI — search vault, open/create/move notes, toggle tasks, edit properties, reload plugins, run JS, capture errors/screenshots. Trigger when the user says "search my vault", "open this note in Obsidian", "list notes tagged X",… - 85interactive-edit
Use when a skill needs the user to interactively edit a file in Neovim mid-workflow, then read their changes back. Takes a window name and the file to edit.