Stats
Actions
Tags
From rvanbaalen
Offer to open markdown documents in mdreader after writing them. Trigger this skill whenever you write or create a markdown file that is a plan, spec, design document, architecture doc, implementation guide, proposal, RFC, or any substantive document meant to be read (not just a config snippet or small edit). Also trigger when the user asks to "open", "view", or "preview" a markdown file. Do NOT trigger for trivial edits to existing files (like fixing a typo in a README), code comments, or CLAUDE.md updates.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rvanbaalen:open-markdownThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
After writing a markdown document that's meant to be read as a standalone document, offer to open it in mdreader so the user can read it comfortably in a rendered view.
After writing a markdown document that's meant to be read as a standalone document, offer to open it in mdreader so the user can read it comfortably in a rendered view.
This skill applies to markdown files that are substantive, standalone documents someone would want to sit down and read. Think:
This skill does NOT apply to:
The distinction is simple: if you just wrote something the user will want to read through, offer to open it. If it's a quick edit they already know about, don't.
Before offering to open anything, verify mdreader is installed:
which mdreader
If mdreader is not found, install it:
brew install rvanbaalen/tap/mdreader
If brew is not available or the install fails, tell the user mdreader couldn't be installed and provide the GitHub link: https://github.com/rvanbaalen/mdreader
After writing or creating a qualifying markdown document, use AskUserQuestion to ask:
Question: "I've written <filename> — would you like to open it in mdreader?"
Options:
Keep it lightweight. One question, two options. Don't over-explain what mdreader is.
If the user says yes, run:
mdreader <absolute-path-to-file>
mdreader runs as a background process (it opens in the user's default browser), so this won't block the session. After opening, continue with whatever comes next — don't wait for confirmation that it opened.
If you write several qualifying documents in quick succession (e.g., a plan and a spec), batch them into a single question rather than asking repeatedly:
Question: "I've written these documents — want to open any in mdreader?"
Options:
If the user explicitly asks to "open", "view", or "preview" a markdown file, skip the question and open it directly with mdreader. They already told you what they want.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Applies a firm's KYC/AML rules grid to parsed onboarding records: assigns risk rating, checks required documents, outputs rule outcomes with citations, and routes for escalation.
Generates daily or weekly digests of activity from connected sources (chat, email, docs, tasks, CRM), highlighting action items, decisions, mentions, and project updates.
npx claudepluginhub rvanbaalen/skills --plugin open-markdown