workflow
A "bridge" MCP server with a unique Prompt+Tool design that helps LLMs seamlessly generate and render diagrams. Powered by Kroki to support most popular formats.
Install / Use
npx skills add tohachan/diagram-bridge-mcpInstalls into whichever agent you are using.
Cursor Rules
Cursor IDE rules (v2)
Quality Score
Category
AutomationSupported Platforms
Our assessment of workflow
workflow scores 66/100 on our quality scale, 2684th of 2,853 Automation skills we index.
Its Cursor Rules is 4.3 KB long, well organised into 8 sections with 7 code examples: a solid amount of guidance for an agent.
It has no GitHub stars yet, so there is no community track record; judge it on its content.
Maintenance, license and trust
- We could not determine when the repository was last updated.
- Our last check on 2026-09-16 found the source still online.
- No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
- Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
workflow compared with similar skills
All 4 of these similar skills score higher than workflow; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| workflow (this skill)by tohachan | 66 | 0 | — | Cursor Rules |
| taste-skillby Leonxlnx | 100 | 109.6k | today | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 108.5k | 3d ago | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 78.8k | today | CLAUDE.md |
| CowAgentby zhayujie | 100 | 47.8k | today | CLAUDE.md |
Frequently asked questions
- How do I install workflow?
- Run
npx skills add tohachan/diagram-bridge-mcp. The install tabs above show the steps for each supported agent. - Which AI agents does workflow work with?
- It is written for Cursor, as a Cursor Rules file. Other agents that read the same format can often use it too.
- Is workflow safe to use?
- It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is workflow still maintained?
- We could not determine when the repository was last updated.
Skill content
View source on GitHubDevelopment Workflow Rules
TypeScript Testing & Compilation
typescript:
before_testing:
- always_run: "npm run build"
- compiled_path: "./dist/"
- source_path: "./src/"
module_imports:
- test_files: "use .cjs extension"
- import_style: "const { Class } = require('./dist/path/file.js')"
- avoid: "import statements in test files"
- reason: "project uses ES modules, test files need CommonJS"
compilation_check:
- verify: "dist/ folder exists after build"
- if_missing: "run npm run build first"
- structure: "dist mirrors src structure"
Docker Testing
docker:
container_lifecycle:
- startup: "docker-compose up -d"
- check_status: "docker-compose ps"
- shutdown: "docker-compose down"
- never_forget: "cleanup containers after testing"
mcp_behavior:
- restart_policy: "restart: 'no'"
- normal_behavior: "MCP servers exit when not in use"
- not_http_server: "MCP uses stdin/stdout, not HTTP endpoints"
- testing_method: "test via Kroki direct API"
networking:
- kroki_endpoint: "http://localhost:8000"
- test_formats: "POST to /format/output_type"
- content_type: "text/plain"
- encoding: "send raw code, not base64url"
API Testing Patterns
api_testing:
kroki_direct:
- method: "POST"
- url: "http://localhost:8000/{format}/{output}"
- headers: { "Content-Type": "text/plain" }
- body: "raw diagram code"
- avoid: "base64url encoding for GET requests"
test_file_naming:
- pattern: "test-{feature}-{method}.cjs"
- examples: ["test-d2-kroki-direct.cjs", "test-mermaid-workflow.cjs"]
- cleanup: "delete temporary test files when done"
error_debugging:
- always_check: "response.ok before parsing"
- log_errors: "console.error status + error text"
- incremental: "test simple cases first, then complex"
Template & Configuration Testing
template_testing:
instruction_templates:
- path: "./dist/templates/instruction-template.js"
- test_method: "DiagramInstructionTemplate.generateInstructionPrompt()"
- verify_sections: ["syntaxGuidelines", "commonPitfalls", "examplePatterns"]
config_changes:
- after_edit: "always rebuild with npm run build"
- test_impact: "create focused test for changed format"
- verify_examples: "ensure examples use correct syntax"
validation_flow:
1. "edit config/template"
2. "npm run build"
3. "create test file (.cjs)"
4. "test specific changes"
5. "test full workflow"
6. "cleanup test files"
Common Pitfalls to Avoid
pitfalls:
file_extensions:
- avoid: ".js files for testing (ES module conflicts)"
- use: ".cjs for test files"
- reason: "project has 'type: module' in package.json"
import_paths:
- source_files: "./src/path/file.ts"
- compiled_files: "./dist/path/file.js"
- never_mix: "don't import from src/ in tests"
docker_expectations:
- mcp_servers: "designed to exit when idle"
- not_web_apps: "no persistent HTTP server"
- kroki_testing: "test rendering engines directly"
template_debugging:
- syntax_errors: "usually in instruction templates"
- fix_source: "edit src/resources/diagram-instructions-config.ts"
- not_generated: "don't fix generated code manually"
Quick Commands Reference
commands:
build: "npm run build"
test_all: "npm test"
docker_up: "docker-compose up -d"
docker_down: "docker-compose down"
docker_status: "docker-compose ps"
docker_logs: "docker-compose logs -f"
kroki_health: "curl http://localhost:8000/health"
create_test:
- "touch test-{feature}.cjs"
- "add: const { Class } = require('./dist/path/file.js')"
- "test your changes"
- "rm test-{feature}.cjs"
Emergency Troubleshooting
troubleshooting:
module_not_found:
- check: "npm run build completed"
- verify: "dist/ folder structure"
- ensure: "correct path in require()"
docker_issues:
- restart: "docker-compose down && docker-compose up -d"
- wait: "2-3 seconds for services to start"
- check: "docker-compose ps shows 'healthy' status"
syntax_errors:
- location: "usually in instruction templates"
- fix_in: "src/resources/diagram-instructions-config.ts"
- rebuild: "npm run build after changes"
- test: "create specific test for the format"
Related Skills
taste-skill
109.6kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
108.5kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
headroom
78.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
CowAgent
47.8kOpen-source personal AI assistant & Agent Harness. Plans tasks, runs tools and skills, self-evolves with memory and knowledge. Multi-agent, multi-model, multi-channel. Lightweight, extensible, one-line install.
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
