mermaid-summarizer
Skill2 starsChanged 39 days agoMITView on GitHub
Summarize a source document as a valid Mermaid hierarchy without losing required concepts.
In this repository15 other files it gives its agents.
- notemdproSkill
- batch-processorSkill
- concept-extractorSkill
- content-generatorSkill
- diagram-generatorSkill
- formula-healerSkill
- link-analyzerSkill
- mermaid-healerSkill
- qa-extractorSkill
- selection-processorSkill
- system-architectureSkill
- test-driven-developmentSkill
- text-translatorSkill
- web-researcherSkill
- workflow-runnerSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Read the complete authorized document and identify its core concepts and ownership hierarchy.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Mermaid summarizer
English
Read the complete authorized document and identify its core concepts and ownership hierarchy. Use a Mermaid mindmap for a genuine hierarchy; use diagram-generator when explicit cross-branch relations need a different diagram family.
Generate a single fenced Mermaid block with a mindmap declaration and consistent indentation. Parentheses are valid shape syntax: a root may be root(("Title")). Preserve labels and required concepts; do not delete punctuation or relationships merely to pass parsing. Track any deliberate summarization separately from syntax repair.
Validate with mermaid-healer. Keep the original output if an unknown family or ambiguous incomplete block needs review. Report source coverage and unresolved errors through workflow-runner. Successful Mermaid text generation does not prove that a host rendered or exported it.
中文
阅读完整的已授权文档,确定核心概念及归属层级。真正的层级适合 Mermaid mindmap;跨分支的显式关系需要其他图形类型时,使用 diagram-generator。
生成单个 Mermaid 围栏代码块,包含 mindmap 声明并使用一致缩进。圆括号是有效形状语法,根节点可以写作 root(("Title"))。保留标签及必要概念,不得为了通过解析而删除标点或关系。将有意的内容摘要与语法修复分别记录。
使用 mermaid-healer 验证。遇到未知类型或含义不明确的未闭合代码块时,保留原输出供审阅。通过 workflow-runner 报告来源覆盖和未解决错误。Mermaid 文本生成成功不代表宿主已完成渲染或导出。
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.

