首页龙虾技能列表 › Nm Cartograph Architecture Diagram

\ud83e\udd9e Nm Cartograph Architecture Diagram

v1.0.0

Generate Mermaid architecture diagrams from codebase structure. Use for onboarding, PR reviews

0· 54·1 当前·1 累计
by @athola·MIT-0
下载技能包 项目主页
License
MIT-0
最后更新
2026/4/10
安全扫描
VirusTotal
无害
查看报告
OpenClaw
安全
high confidence
The skill's requested actions, lack of installs/credentials, and instructions match its stated purpose of producing Mermaid architecture diagrams from a codebase; no mismatches or unexplained requirements were found.
评估建议
This skill appears coherent and does what it says: it will run a codebase analysis agent (which reads files under the provided scope, defaulting to project root), convert that model to Mermaid, and send the diagram to an MCP renderer. Before using it: (1) avoid running it on repositories containing secrets or sensitive file paths you don't want transmitted to a renderer service; (2) restrict the analysis scope to specific directories when possible; (3) verify you trust the rendering MCP/provider...
详细分析 ▾
用途与能力
The name/description (generate Mermaid architecture diagrams from a codebase) aligns with the runtime instructions: explore the codebase, build a structural model, produce Mermaid flowchart syntax, and render it. No extra binaries, credentials, or unrelated resources are requested.
指令范围
Instructions delegate code analysis to a 'codebase-explorer' agent and call an MCP renderer. This is within scope for generating diagrams, but it means the agent will read project files (default project root if no scope) and send the structural model/mermaid code to the renderer. Users should be aware that repository structure (and any paths or filenames) will be transmitted to the rendering service.
安装机制
There is no install spec and no code files; the skill is instruction-only, so nothing is downloaded or written to disk by the skill itself.
凭证需求
The skill does not require environment variables, credentials, or config paths. That is proportional to the stated purpose.
持久化与权限
always is false and no special persistence or system-wide changes are requested. The default ability for the model to invoke the skill autonomously remains enabled, which is platform default but not elevated by this skill.
安全有层次,运行前请审查代码。

License

MIT-0

可自由使用、修改和再分发,无需署名。

运行时依赖

无特殊依赖

版本

latestv1.0.02026/4/10

- Initial release of the "architecture-diagram" skill. - Generate Mermaid architecture diagrams from codebase structure. - Intended for onboarding, PR reviews, and visualizing component relationships. - Provides workflows for codebase exploration, diagram generation, and rendering. - Follows specific conventions for diagram clarity, such as node grouping and shape usage.

● 无害

安装命令 点击复制

官方npx clawhub@latest install nm-cartograph-architecture-diagram
镜像加速npx clawhub@latest install nm-cartograph-architecture-diagram --registry https://cn.clawhub-mirror.com

技能文档

Night Market Skill — ported from claude-night-market/cartograph. For the full experience with agents, hooks, and commands, install the Claude Code plugin.

# Architecture Diagram

Generate a Mermaid flowchart showing high-level component relationships in a codebase.

When To Use

  • Visualizing how plugins/modules relate to each other
  • Onboarding to understand system structure
  • Documenting architecture for PR reviews
  • Answering "how does this system fit together?"

Workflow

Step 1: Explore the Codebase

Dispatch the codebase explorer agent to analyze the scope:

Agent(cartograph:codebase-explorer)
Prompt: Explore [scope] and return a structural model.
Focus on packages, modules, and their relationships
for an architecture diagram.

If no scope is provided, use the project root.

Step 2: Generate Mermaid Syntax

Transform the structural model into a Mermaid flowchart.

Rules for architecture diagrams:

  • Use flowchart TD (top-down) for hierarchical systems
  • Use flowchart LR (left-right) for pipeline/flow systems
  • Group related modules into subgraphs by package
  • Use descriptive edge labels for relationships
  • Limit to 15-20 nodes maximum (aggregate small modules)
  • Use shapes to distinguish component types:
- [Rectangle] for modules/packages - ([Stadium]) for entry points/commands - [(Database)] for data stores - {Diamond} for decision points

Example output:

flowchart TD
    subgraph sanctum[Sanctum Plugin]
        commit[Commit Messages]
        pr[PR Preparation]
        workspace[Workspace Review]
    end

subgraph leyline[Leyline Plugin] git[Git Platform] patterns[Error Patterns] end

commit --> git pr --> workspace pr --> git workspace --> patterns

Step 3: Render via MCP

Call the Mermaid Chart MCP to render:

mcp__claude_ai_Mermaid_Chart__validate_and_render_mermaid_diagram
  prompt: "Architecture diagram of [scope]"
  mermaidCode: [generated syntax]
  diagramType: "flowchart"
  clientName: "claude-code"

If rendering fails, fix the Mermaid syntax based on the error message and retry (max 2 retries).

Step 4: Present Results

Show the rendered diagram to the user with a brief summary of what it depicts (2-3 sentences).

数据来源:ClawHub ↗ · 中文优化:龙虾技能库
OpenClaw 技能定制 / 插件定制 / 私有工作流定制

免费技能或插件可能存在安全风险,如需更匹配、更安全的方案,建议联系付费定制

了解定制服务