doc-to-md
Skill0 starsChanged 5 days agoMITView on GitHub
Use this when project documents (Word, Excel, PowerPoint, PDF, legacy .doc/.xls, HTML) must be turned into Markdown with deterministic tools — not AI rewriting — and saved in the project so later analysis, test design and review read the same text the client wrote.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- Bigsillymao/zotero-obsidian-ai-workflowtheir own version, first seen Oct 25, 2026
- Bigsillymao/doc-to-mdtheir own version, first seen Oct 20, 2026
- JinsYin/skillstheir own version, first seen Oct 11, 2026
- Arronjeck/claude-skilltheir own version, first seen May 15, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- Bigsillymao/doc-to-md★ 2same name
- Bigsillymao/zotero-obsidian-ai-workflow★ 2same name
- JinsYin/skills★ 1same name
- Arronjeck/claude-skill★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
- anatomySkill
- approachSkill
- brainstorm-brseSkill
- business-explainSkill
- change-impactSkill
- code-to-businessSkill
- cross-checkSkill
- detail-design-jpSkill
- diagramSkill
- e2e-test-playwrightSkill
- estimationSkill
- excel-analyzeSkill
- image-analyzeSkill
- jp-vi-translateSkill
- meeting-intakeSkill
- proposal-genSkill
- qa-tone-brseSkill
- report-genSkill
- research-jp-techSkill
- review-gateSkill
- scope-analysisSkill
- testcase-review-jpSkill
- test-designSkill
- verify-outputSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 14
Run <py> ${CLAUDE_PLUGIN_ROOT}/scripts/brse.py config and read its JSON:
- Very specific: line 38
Standard path = ingest: Run <py> ${CLAUDE_PLUGIN_ROOT}/scripts/brse.py kb-ingest (follow commands/ingest.md).
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Before running
<py> below = the Python recorded by /brse-toolkit:setup (runtime.python
in ~/.config/brse-toolkit/config.json — read that file directly), else the
first of python3, python, py -3 that runs. No Python at all → tell the
user to run /brse-toolkit:setup, and continue only with steps that need no
script, saying which checks were skipped.
Run <py> ${CLAUDE_PLUGIN_ROOT}/scripts/brse.py config and read its JSON:
error→ show it to the user and stop; the config file must be fixed first.workspace_rootis null → the folder isn't initialized. Ask once: run/brse-toolkit:initfirst (recommended — memory and knowledge get saved for next time) or continue once without saving. Running as a subagent dispatched by a main agent → the parent already resolved this; proceed.- Otherwise use
config.paths(sources,templates,outputs— relative toworkspace_root),config.style,config.translation, and the files in.brse/memory/long/. Never assume a folder name the config doesn't list. warningsnot empty → mention them in one line (likely a typo in the config).
When to use
First step before analysing a spec, designing test cases or reviewing a document set. Not for translation or summarising — this skill never rewrites a word.
Rules
- Tools only, no AI. Text comes from scripts, never retyped, paraphrased, "cleaned up" or translated. If a conversion is wrong, fix the conversion.
- One place for converted text:
.brse/knowledge/docs/(the same place/brse-toolkit:ingestuses). Never touch the originals.
Steps
- Standard path = ingest. Run
<py> ${CLAUDE_PLUGIN_ROOT}/scripts/brse.py kb-ingest(followcommands/ingest.md). It converts every file underpaths.sources/internal/deliverables, writes the Markdown copies,manifest.jsonand the search index, and skips unchanged files. - Fallback for files ingest marks
unreadable(legacy .doc/.xls/.ppt, .rtf, .odt, odd PDFs): run<py> ${CLAUDE_PLUGIN_ROOT}/scripts/brse.py doc2md <file> --out <workspace_root>/.brse/knowledge/docs/<its source folder>(MarkItDown, LibreOffice round-trip, pdftotext). Say which files used it. Outside an initialized workspace (one-off), the same script with--out <source folder>/docs-md/— and say nothing is indexed. partialfiles (shapes, images, charts, flow sheets, screen images): read them withexcel-analyze/image-analyze; never present the Markdown copy as the complete content.- Scanned PDF with no text → say OCR is needed; never invent the text.
Output
Counts (converted / unchanged / partial / unreadable), the list of partial and unreadable files inline, and the fallback files.
Handoff
Next skills read .brse/knowledge/docs/ and search with brse.py kb-search:
scope-analysis, test-design, business-explain, testcase-review-jp.
Finish with verify-output on the reply.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

