{"id":"b276ff18-f087-45b9-a389-f50257a9677a","entityType":"agent","slug":"clawhub-cellcog-diagram-flowchart-cellcog","name":"Flowchart","canonicalUrl":"https://www.xpersona.co/agent/clawhub-cellcog-diagram-flowchart-cellcog","canonicalPath":"/agent/clawhub-cellcog-diagram-flowchart-cellcog","generatedAt":"2026-10-10T07:40:06.488Z","source":"CLAWHUB","claimStatus":"UNCLAIMED","verificationTier":"NONE","summary":{"evidence":{"source":"editorial-content","verified":true,"confidence":"high","updatedAt":"2026-10-09T23:09:36.833Z","emptyReason":null},"description":"AI diagram and flowchart generation powered by CellCog. Flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, network diagrams. Describe your system in plain English, get interactive diagrams or print-ready PDFs. Skill: Flowchart Owner: cellcog Summary: AI diagram and flowchart generation powered by CellCog. Flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, network diagrams. Describe your system in plain English, get interactive diagrams or print-ready PDFs. Tags: latest:1.0.10 Version history: v1.0.10 | 2026-08-24T02:01:52.299Z | user Content updated. v1.0.9 | 2026-08-24T01","descriptionLabel":"Technical summary","evidenceSummary":"Capability contract not published. No trust telemetry is available yet. 1.9K downloads reported by the source. Last updated 10/9/2026.","installCommand":"clawhub skill install s176q1btpn094ats9b4f9hgfwx83knpk:diagram-flowchart-cellcog","sourceUrl":"https://clawhub.ai/cellcog/diagram-flowchart-cellcog","homepage":"https://clawhub.ai/cellcog/skills/diagram-flowchart-cellcog","primaryLinks":[{"label":"View on ClawHub","url":"https://clawhub.ai/cellcog/diagram-flowchart-cellcog","kind":"source"},{"label":"Homepage","url":"https://clawhub.ai/cellcog/skills/diagram-flowchart-cellcog","kind":"homepage"}],"safetyScore":84,"overallRank":62,"popularityScore":66,"trustScore":null,"claimedByName":null,"isOwner":false,"seoDescription":"AI diagram and flowchart generation powered by CellCog. Flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, ne"},"coverage":{"evidence":{"source":"public-profile","verified":false,"confidence":"medium","updatedAt":"2026-10-09T23:09:36.833Z","emptyReason":null},"protocols":[{"protocol":"OPENCLEW","label":"OpenClaw","status":"self-declared","notes":"Declared in the public agent profile."}],"capabilities":[],"verifiedCount":0,"selfDeclaredCount":1,"capabilityMatrix":{"rows":[{"key":"OPENCLEW","type":"protocol","support":"unknown","confidenceSource":"profile","notes":"Listed on profile"}],"flattenedTokens":"protocol:OPENCLEW|unknown|profile"}},"adoption":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T23:09:36.833Z","emptyReason":null},"stars":null,"forks":null,"downloads":1907,"packageName":null,"latestVersion":"1.0.10","tractionLabel":"1.9K downloads"},"release":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"medium","updatedAt":"2026-10-09T23:09:36.236Z","emptyReason":null},"lastUpdatedAt":"2026-10-09T23:09:36.833Z","lastCrawledAt":"2026-10-09T23:09:36.236Z","lastIndexedAt":null,"nextCrawlAt":"2026-10-10T23:09:36.236Z","lastVerifiedAt":null,"highlights":[{"version":"1.0.10","createdAt":"2026-08-24T02:01:52.299Z","changelog":"Content updated.","fileCount":3,"zipByteSize":7521},{"version":"1.0.9","createdAt":"2026-08-24T01:46:20.884Z","changelog":"Content updated.","fileCount":3,"zipByteSize":7454},{"version":"1.0.8","createdAt":"2026-08-03T06:06:34.349Z","changelog":"Content updated.","fileCount":3,"zipByteSize":7321},{"version":"1.0.7","createdAt":"2026-08-02T22:03:30.282Z","changelog":"Display title updated.","fileCount":3,"zipByteSize":7405},{"version":"1.0.6","createdAt":"2026-07-17T03:40:55.189Z","changelog":"- Skill renamed to \"diagram-flowchart-cellcog\" for clarity and consistency. - SKILL.md updated to reflect the new name and description. - Example uses and documentation remain unchanged. - Obsolete skill-card.md file removed.","fileCount":3,"zipByteSize":7388},{"version":"1.0.5","createdAt":"2026-04-14T17:32:10.612Z","changelog":"- Shortened and streamlined the skill description for clarity. - Updated SDK usage instructions to clarify agent support (OpenClaw vs. other agents). - No changes to features or functionality; documentation only.","fileCount":3,"zipByteSize":7422},{"version":"1.0.4","createdAt":"2026-04-13T01:00:42.833Z","changelog":"- Updated the skill description for greater clarity and emphasis on interactive, AI-powered diagram generation. - Improved usage instructions with an explicit import example for modern agent providers. - Enhanced description of key features and differentiated the offering from static-image AI diagram tools. - No code or API changes; documentation and clarity improvements only.","fileCount":2,"zipByteSize":6211},{"version":"1.0.3","createdAt":"2026-04-12T23:35:20.789Z","changelog":"- Significantly condensed and clarified the skill overview and usage instructions. - Updated the description for brevity and focus; emphasized interactive and PDF outputs. - Moved advanced usage and SDK details out; now refers users to the main cellcog skill for those topics. - Retained all diagram type examples, but streamlined explanations for easier reading. - Improved formatting and removed repetitive marketing language for a clearer quickstart.","fileCount":2,"zipByteSize":6124}]},"execution":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No published capability contract is available yet."},"installCommand":"clawhub skill install s176q1btpn094ats9b4f9hgfwx83knpk:diagram-flowchart-cellcog","setupComplexity":"low","setupSteps":["Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.","Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data."],"contract":{"contractStatus":"missing","authModes":[],"requires":[],"forbidden":[],"supportsMcp":false,"supportsA2a":false,"supportsStreaming":false,"inputSchemaRef":null,"outputSchemaRef":null,"dataRegion":null,"contractUpdatedAt":null,"sourceUpdatedAt":null,"freshnessSeconds":null},"invocationGuide":{"preferredApi":{"snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-cellcog-diagram-flowchart-cellcog/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-cellcog-diagram-flowchart-cellcog/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-cellcog-diagram-flowchart-cellcog/trust"},"curlExamples":["curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-cellcog-diagram-flowchart-cellcog/snapshot\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-cellcog-diagram-flowchart-cellcog/contract\"","curl -s \"https://www.xpersona.co/api/v1/agents/clawhub-cellcog-diagram-flowchart-cellcog/trust\""],"jsonRequestTemplate":{"query":"summarize this repo","constraints":{"maxLatencyMs":2000,"protocolPreference":["OPENCLEW"]}},"jsonResponseTemplate":{"ok":true,"result":{"summary":"...","confidence":0.9},"meta":{"source":"CLAWHUB","generatedAt":"2026-10-10T07:40:06.484Z"}},"retryPolicy":{"maxAttempts":3,"backoffMs":[500,1500,3500],"retryableConditions":["HTTP_429","HTTP_503","NETWORK_TIMEOUT"]}},"endpoints":{"dossierUrl":"https://www.xpersona.co/api/v1/agents/clawhub-cellcog-diagram-flowchart-cellcog/dossier","snapshotUrl":"https://www.xpersona.co/api/v1/agents/clawhub-cellcog-diagram-flowchart-cellcog/snapshot","contractUrl":"https://www.xpersona.co/api/v1/agents/clawhub-cellcog-diagram-flowchart-cellcog/contract","trustUrl":"https://www.xpersona.co/api/v1/agents/clawhub-cellcog-diagram-flowchart-cellcog/trust"}},"reliability":{"evidence":{"source":"runtime-metrics","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No trust, reliability, or runtime telemetry is available."},"trust":{"status":"unavailable","handshakeStatus":"UNKNOWN","verificationFreshnessHours":null,"reputationScore":null,"p95LatencyMs":null,"successRate30d":null,"fallbackRate":null,"attempts30d":null,"trustUpdatedAt":null,"trustConfidence":"unknown","sourceUpdatedAt":null,"freshnessSeconds":null},"decisionGuardrails":{"doNotUseIf":["Contract metadata is missing or unavailable for deterministic execution."],"safeUseWhen":[],"riskFlags":["missing_or_unavailable_contract","trust_data_unavailable","schema_references_missing"],"operationalConfidence":"low"},"executionMetrics":{"observedLatencyMsP50":null,"observedLatencyMsP95":null,"estimatedCostUsd":null,"uptime30d":null,"rateLimitRpm":null,"rateLimitBurst":null,"lastVerifiedAt":null,"verificationSource":null},"runtimeMetrics":{"successRate":null,"avgLatencyMs":null,"avgCostUsd":null,"hallucinationRate":null,"retryRate":null,"disputeRate":null,"p50Latency":null,"p95Latency":null,"lastUpdated":null}},"benchmarks":{"evidence":{"source":"no-benchmark-data","verified":false,"confidence":"low","updatedAt":null,"emptyReason":"No benchmark suites or observed failure patterns are available."},"suites":[],"failurePatterns":[]},"artifacts":{"evidence":{"source":"CLAWHUB","verified":false,"confidence":"high","updatedAt":"2026-10-09T23:09:36.833Z","emptyReason":null},"readme":"Skill: Flowchart\n\nOwner: cellcog\n\nSummary: AI diagram and flowchart generation powered by CellCog. Flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, network diagrams. Describe your system in plain English, get interactive diagrams or print-ready PDFs.\n\nTags: latest:1.0.10\n\nVersion history:\n\nv1.0.10 | 2026-08-24T02:01:52.299Z | user\n\nContent updated.\n\nv1.0.9 | 2026-08-24T01:46:20.884Z | user\n\nContent updated.\n\nv1.0.8 | 2026-08-03T06:06:34.349Z | user\n\nContent updated.\n\nv1.0.7 | 2026-08-02T22:03:30.282Z | user\n\nDisplay title updated.\n\nv1.0.6 | 2026-07-17T03:40:55.189Z | auto\n\n- Skill renamed to \"diagram-flowchart-cellcog\" for clarity and consistency.\n- SKILL.md updated to reflect the new name and description.\n- Example uses and documentation remain unchanged.\n- Obsolete skill-card.md file removed.\n\nv1.0.5 | 2026-04-14T17:32:10.612Z | auto\n\n- Shortened and streamlined the skill description for clarity.\n- Updated SDK usage instructions to clarify agent support (OpenClaw vs. other agents).\n- No changes to features or functionality; documentation only.\n\nv1.0.4 | 2026-04-13T01:00:42.833Z | auto\n\n- Updated the skill description for greater clarity and emphasis on interactive, AI-powered diagram generation.\n- Improved usage instructions with an explicit import example for modern agent providers.\n- Enhanced description of key features and differentiated the offering from static-image AI diagram tools.\n- No code or API changes; documentation and clarity improvements only.\n\nv1.0.3 | 2026-04-12T23:35:20.789Z | auto\n\n- Significantly condensed and clarified the skill overview and usage instructions.\n- Updated the description for brevity and focus; emphasized interactive and PDF outputs.\n- Moved advanced usage and SDK details out; now refers users to the main cellcog skill for those topics.\n- Retained all diagram type examples, but streamlined explanations for easier reading.\n- Improved formatting and removed repetitive marketing language for a clearer quickstart.\n\nv1.0.2 | 2026-04-08T05:57:54.345Z | auto\n\n- Documentation updated in SKILL.md for clarity and better prompt examples.\n- No changes to code or functionality; content improvements only.\n\nv1.0.1 | 2026-04-08T05:52:26.429Z | auto\n\n**Major update to diagram-cog: clearer positioning, improved examples, and expanded documentation.**\n\n- Rewrote description and intro to emphasize \"describe it in words, get it as a diagram\" and interactive outputs — no traditional diagramming tools needed.\n- Added sections explaining why diagrams are hard, what sets CellCog apart (reasoning, interactive web apps, custom code generation), and how it differs from static AI image tools.\n- Expanded and reorganized example use cases and prompts for flowcharts, architecture diagrams, mind maps, org charts, and UML diagrams.\n- Clarified prerequisite setup, typical usage patterns, output types, and rendering stack (Mermaid, D3, custom SVG/HTML, Highcharts).\n- Documentation is now more user-focused, showing real-world prompts and highlighting the benefits for technical and non-technical audiences.\n\nv1.0.0 | 2026-04-06T05:07:07.596Z | auto\n\n- Initial release of diagram-cog.\n- Generate flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, network diagrams, and more from text descriptions.\n- Output diagrams as interactive HTML apps or print-ready PDFs.\n- Uses CellCog's internal tools: Mermaid.js, D3.js, custom SVG/HTML, PDF generation, and Highcharts.\n- Requires the cellcog skill and a CELLCOG_API_KEY.\n\nArchive index:\n\nArchive v1.0.10: 3 files, 7521 bytes\n\nFiles: skill-card.md (2278b), SKILL.md (13981b), _meta.json (145b)\n\nFile v1.0.10:SKILL.md\n\n---\nname: diagram-flowchart-cellcog\ndescription: \"AI diagram and flowchart generation powered by CellCog. Flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, network diagrams. Describe your system in plain English, get interactive diagrams or print-ready PDFs.\"\nmetadata:\n  openclaw:\n    emoji: \"🔀\"\n    os: [darwin, linux, windows]\n    requires:\n      bins: [python3]\n      env: [CELLCOG_API_KEY]\nauthor: CellCog\nhomepage: https://cellcog.ai\ndependencies: [cellcog]\n---\n# Diagram & Flowchart - Describe It in Words, Get It as a Diagram\n\nDescribe your system, process, or idea in plain English — CellCog produces professional, interactive diagrams you can share with a URL.\n\nNo Visio. No Lucidchart. No dragging boxes around for hours. Just describe what you need, and CellCog renders it as an interactive web page you can zoom, pan, and click — or a print-ready PDF for documentation.\n\n## How to Use\n\nFor your first CellCog task in a session, read the **cellcog** skill for the full SDK reference — file handling, chat modes, timeouts, and more.\n\n**OpenClaw (fire-and-forget):**\n```python\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    notify_session_key=\"agent:main:main\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\n```\n\n**All agents except OpenClaw (blocks until done):**\n```python\nfrom cellcog import CellCogClient\nclient = CellCogClient(agent_provider=\"openclaw|cursor|claude-code|codex|...\")\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\nprint(result[\"message\"])\n```\n\n\n---\n\n## Why Diagrams Are Hard\n\nCreating good diagrams manually is surprisingly painful:\n\n- **Layout is tedious**: Arranging boxes, arrows, and labels takes longer than the thinking itself\n- **Tools are complex**: Visio, Lucidchart, Draw.io all have learning curves\n- **Iteration is slow**: Changing one element cascades into repositioning everything\n- **Sharing is friction**: Export → attach → hope it renders on their device\n\nCellCog eliminates all of this. Describe your diagram in words, get a shareable interactive URL. Need to change something? Just ask.\n\n---\n\n## What Makes This Different\n\nOther AI diagram tools output a static image. CellCog does something fundamentally different.\n\nCellCog **reasons about your system, picks the right rendering approach, and deploys an interactive web application** you can share with a URL. Zoom into your microservices architecture. Click a node to see details. Pan across a sprawling org chart. Or export to a print-ready PDF for your board deck.\n\n| What You Ask For | What CellCog Actually Does |\n|-----------------|---------------------------|\n| \"Diagram my microservices\" | Reasons about the architecture → generates Mermaid/D3 code → deploys interactive web app → delivers shareable URL |\n| \"Flowchart for our hiring process\" | Analyzes the process → renders with proper decision logic → color-codes paths → interactive HTML with click states |\n| \"ER diagram for my database\" | Understands entity relationships → generates diagram with cardinality → exports as both interactive HTML and PDF |\n| \"Mind map for brainstorming\" | Explores the topic → creates hierarchical structure → deploys zoomable, expandable mind map |\n\nThe power comes from having a world-class coding agent, multiple rendering libraries (Mermaid.js, D3.js, custom SVG, Highcharts), and built-in app deployment — all orchestrated together. When standard tools fall short, the agent writes custom code.\n\n---\n\n## What Diagrams You Can Create\n\n### Flowcharts & Process Flows\n\nVisualize any process or decision tree:\n\n- **Business Processes**: \"Create a flowchart for our customer onboarding process — from signup to first value\"\n- **Decision Trees**: \"Build a decision tree for our support team to triage incoming tickets\"\n- **User Flows**: \"Create a user flow diagram for the checkout process in our e-commerce app\"\n- **Approval Workflows**: \"Diagram our expense approval workflow — who approves what at each dollar threshold\"\n- **Troubleshooting Guides**: \"Create a troubleshooting flowchart for common API integration errors\"\n\n**Example prompt:**\n> \"Create an interactive flowchart for our hiring process:\n> \n> Steps:\n> 1. Job posted → Applications received\n> 2. Resume screening (HR) → Pass/Fail\n> 3. Phone screen (Recruiter) → Pass/Fail\n> 4. Technical interview (Engineering) → Pass/Fail\n> 5. Culture interview (Team) → Pass/Fail\n> 6. Offer → Accept/Decline\n> 7. If decline → Back to step 2 with next candidate\n> \n> Color-code: Green for forward progress, red for rejection paths, yellow for decision points.\n> Include average time at each stage.\"\n\n### System Architecture\n\nTechnical diagrams for engineering teams:\n\n- **Microservices**: \"Diagram our microservices architecture showing all services, their communication patterns, and data stores\"\n- **Cloud Infrastructure**: \"Create an AWS architecture diagram for our production environment — VPC, ECS, RDS, ElastiCache, CloudFront\"\n- **Data Pipelines**: \"Diagram our data pipeline from raw ingestion through transformation to the analytics warehouse\"\n- **API Architecture**: \"Create an API gateway architecture showing routing, authentication, and rate limiting\"\n- **CI/CD Pipelines**: \"Diagram our deployment pipeline from git push to production\"\n\n**Example prompt:**\n> \"Create a system architecture diagram for a SaaS application:\n> \n> Frontend: React app on CloudFront/S3\n> API: FastAPI on ECS Fargate behind ALB\n> Auth: Firebase Authentication\n> Database: PostgreSQL on RDS (primary + read replica)\n> Cache: Redis on ElastiCache\n> Queue: SQS for async jobs\n> Workers: Celery on ECS\n> Storage: S3 for user uploads\n> Monitoring: CloudWatch + Datadog\n> \n> Show the data flow between components with arrows.\n> Group by VPC / public / external.\n> Interactive — I want to be able to zoom into each component.\"\n\n### Mind Maps & Concept Maps\n\nBrainstorm and organize ideas:\n\n- **Brainstorming**: \"Create a mind map exploring all possible revenue streams for our SaaS product\"\n- **Topic Exploration**: \"Build a concept map of machine learning — main branches, sub-topics, and relationships\"\n- **Content Planning**: \"Create a mind map for our Q2 content strategy — blog, social, video, email\"\n- **Strategy Mapping**: \"Map our go-to-market strategy showing channels, messaging, and target segments\"\n\n**Example prompt:**\n> \"Create an interactive mind map for 'AI in Healthcare':\n> \n> Central node: AI in Healthcare\n> \n> Main branches:\n> - Diagnostics (imaging, pathology, genomics)\n> - Drug Discovery (target identification, clinical trials, molecule design)\n> - Patient Care (chatbots, monitoring, personalized medicine)\n> - Operations (scheduling, billing, supply chain)\n> - Research (literature mining, clinical data analysis)\n> \n> Each branch should have 3-5 sub-topics with brief descriptions.\n> Color-code by maturity: green = in production, yellow = clinical trials, red = research stage.\"\n\n### Org Charts\n\nVisualize organizational structure:\n\n- **Company Hierarchy**: \"Create an org chart for a 50-person startup showing all departments and reporting lines\"\n- **Team Structure**: \"Diagram our engineering team structure — squads, tech leads, and cross-functional relationships\"\n- **Matrix Organization**: \"Create an org chart showing both functional reporting and project reporting lines\"\n\n### UML Diagrams\n\nSoftware engineering diagrams:\n\n- **Sequence Diagrams**: \"Create a sequence diagram showing the OAuth 2.0 authorization code flow\"\n- **Class Diagrams**: \"Diagram the class hierarchy for our e-commerce domain model — Product, Order, Customer, Payment\"\n- **State Diagrams**: \"Create a state diagram for an order lifecycle — placed, paid, shipped, delivered, returned\"\n- **Activity Diagrams**: \"Diagram the activity flow for our data processing pipeline\"\n\n**Example prompt:**\n> \"Create a sequence diagram for a payment processing flow:\n> \n> Actors: User, Frontend, API Server, Payment Service, Stripe, Database\n> \n> Flow:\n> 1. User clicks 'Pay' → Frontend sends payment request to API\n> 2. API creates payment intent with Stripe\n> 3. Stripe returns client secret\n> 4. API sends client secret to Frontend\n> 5. Frontend confirms payment with Stripe.js\n> 6. Stripe sends webhook to API\n> 7. API updates order status in Database\n> 8. API sends confirmation email to User\n> \n> Include error paths: payment declined, webhook timeout.\"\n\n### ER Diagrams\n\nDatabase design and data modeling:\n\n- **Database Schema**: \"Create an ER diagram for a social media platform — users, posts, comments, likes, follows\"\n- **Data Models**: \"Diagram the data model for our inventory management system\"\n- **Entity Relationships**: \"Create an ER diagram showing the relationships between customers, orders, products, and suppliers\"\n\n### Network Diagrams\n\nIT infrastructure visualization:\n\n- **Network Topology**: \"Create a network diagram showing our office network — firewalls, switches, VLANs, wireless APs\"\n- **Security Zones**: \"Diagram our network security zones — DMZ, internal, management, guest\"\n- **Cloud Networking**: \"Create a network diagram for our multi-VPC AWS setup with peering and transit gateway\"\n\n### Gantt Charts & Timelines\n\nProject planning and scheduling:\n\n- **Project Timelines**: \"Create a Gantt chart for our 6-month product launch — design, development, testing, marketing, launch\"\n- **Sprint Planning**: \"Diagram our next 3 sprints with epics, stories, and dependencies\"\n- **Roadmaps**: \"Create a product roadmap timeline for 2026 showing quarterly milestones\"\n\n### Swimlane Diagrams\n\nCross-functional process visualization:\n\n- **Cross-Team Workflows**: \"Create a swimlane diagram showing how a customer support ticket flows between Support, Engineering, and Product teams\"\n- **RACI Charts**: \"Diagram our incident response process with swimlanes for each role\"\n\n### User Journey Maps\n\nCustomer experience visualization:\n\n- **End-to-End Journeys**: \"Create a user journey map for a customer discovering, evaluating, purchasing, and onboarding to our product\"\n- **Touchpoint Mapping**: \"Map all customer touchpoints across email, web, app, and support\"\n\n---\n\n## Output Formats\n\n| Format | Features | Best For |\n|--------|----------|----------|\n| **Interactive HTML** | Zoom, pan, click, hover, responsive, shareable via URL | Presentations, team sharing, exploration |\n| **PDF** | Print-ready, static, professional | Documentation, email attachments, printing |\n\nCellCog defaults to interactive HTML — the whole point is diagrams you can explore, not static images. Request PDF explicitly when you need print-ready output.\n\n---\n\n## Choosing Mode & Tier\n\n| Scenario | Recommended |\n|----------|-------------|\n| Single diagrams and flowcharts | `chat_mode=\"agent\"` (defaults to the `\"flash\"` tier) |\n| Multi-diagram system documentation | `chat_mode=\"agent\", chat_tier=\"max\"` |\n\n**The flash tier is the default and handles most diagram work well** — fast and economical. **Upgrade to `chat_tier=\"max\"`** when quality disappoints or the work is genuinely complex: just re-run the same prompt with `chat_tier=\"max\"`.\n\nAgent Team (`chat_mode=\"team\"`) is reserved for deep research — don't use it for diagram work.\n\n---\n\n## Example Prompts\n\n**Quick flowchart:**\n> \"Create a flowchart for returning a product on our e-commerce site. Include: initiate return → reason selection → approval check → shipping label → refund processing → confirmation. Show the happy path and the rejection path.\"\n\n**Architecture diagram:**\n> \"Diagram our production infrastructure:\n> \n> Load Balancer → 3 API servers → PostgreSQL (primary + replica)\n> API servers also talk to Redis cache and S3 for file storage\n> Background workers pull from SQS queue\n> Everything monitored by Datadog\n> \n> Show it as a clean architecture diagram with arrows showing data flow direction.\"\n\n**Mind map:**\n> \"Create a mind map for planning a product launch:\n> \n> Center: Product Launch\n> Branches: Marketing, Engineering, Sales, Support, Legal\n> Each branch should have 4-6 specific tasks\n> Color-code by priority: red = critical path, yellow = important, green = nice to have\"\n\n**Database ER diagram:**\n> \"Create an ER diagram for a project management tool:\n> \n> Entities: User, Organization, Project, Task, Comment, Attachment, Label\n> \n> Key relationships:\n> - Users belong to Organizations (many-to-many)\n> - Projects belong to Organizations\n> - Tasks belong to Projects, assigned to Users\n> - Comments belong to Tasks, created by Users\n> - Tasks can have multiple Labels (many-to-many)\n> \n> Show primary keys, foreign keys, and cardinality.\"\n\n---\n\n## Tips for Better Diagrams\n\n1. **Describe the components and relationships**: \"A connects to B which talks to C\" is all CellCog needs. Don't worry about layout.\n\n2. **Specify the diagram type**: \"Flowchart\", \"sequence diagram\", \"ER diagram\" — naming the type helps CellCog choose the right rendering approach.\n\n3. **Include data flow direction**: For architecture diagrams, mention which way data flows. \"Frontend → API → Database\" is clearer than just listing components.\n\n4. **Request interactivity**: \"I want to zoom in\" or \"clickable components\" tells CellCog to build an interactive experience.\n\n5. **Color-coding helps**: \"Color-code by team\" or \"green for success paths, red for error paths\" makes diagrams immediately useful.\n\n6. **Think about audience**: \"For the engineering team\" vs. \"for the board presentation\" changes the level of technical detail.\n\n---\n\n## If CellCog is not installed\n\n**Claude Code, Cursor, Codex + 70 more agents:** `npx skills add cellcog/skills --skill cellcog`\n**OpenClaw:** `openclaw skills install @cellcog/cellcog`\n**CellCog plugin users:** run `/cellcog-setup` (or `/cellcog:cellcog-setup` depending on your tool)\n**Manual setup:** `pip install -U cellcog` and set `CELLCOG_API_KEY`. See the **cellcog** skill for SDK reference.\n\nFile v1.0.10:_meta.json\n\n{\n  \"ownerId\": \"kn7a96cj9q65e0bhmzahv790en80ffqm\",\n  \"slug\": \"diagram-flowchart-cellcog\",\n  \"version\": \"1.0.10\",\n  \"publishedAt\": 1787536912299\n}\n\nFile v1.0.10:skill-card.md\n\n## Description:\n\nFlowchart helps agents use CellCog to generate interactive diagrams and print-ready PDFs from plain-language descriptions, including flowcharts, system architecture diagrams, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, and network diagrams.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[cellcog](https://clawhub.ai/user/cellcog)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, architects, product teams, and technical writers use this skill to turn process, system, data, and planning descriptions into shareable diagrams. It is suited for flowcharts, architecture diagrams, mind maps, org charts, UML, ER diagrams, network diagrams, timelines, swimlanes, and user journey maps.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: User prompts and provided materials may be sent to CellCog and may be used to create a shareable hosted diagram output.\n\nMitigation: Do not include secrets, credentials, regulated data, or internal-only architecture details unless sharing them with CellCog and producing a shareable output is intended.\n\nRisk: The skill requires installing and using the CellCog dependency and API key.\n\nMitigation: Install only from a trusted CellCog source, prefer pinned versions where possible, and keep CELLCOG_API_KEY out of shared prompts, files, and logs.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/cellcog/skills/diagram-flowchart-cellcog)\n- [CellCog homepage](https://cellcog.ai)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Code, Shell commands, Configuration]\n\n**Output Format:** [Markdown guidance with Python snippets and setup commands; generated diagrams are delivered as interactive HTML or PDF.]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Requires the CellCog package, python3, and CELLCOG_API_KEY; diagram work may create a shareable hosted output.]\n\n## Skill Version(s):\n\n1.0.10 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.9: 3 files, 7454 bytes\n\nFiles: skill-card.md (2081b), SKILL.md (13964b), _meta.json (144b)\n\nFile v1.0.9:SKILL.md\n\n---\nname: diagram-flowchart-cellcog\ndescription: \"AI diagram and flowchart generation powered by CellCog. Flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, network diagrams. Describe your system in plain English, get interactive diagrams or print-ready PDFs.\"\nmetadata:\n  openclaw:\n    emoji: \"🔀\"\n    os: [darwin, linux, windows]\n    requires:\n      bins: [python3]\n      env: [CELLCOG_API_KEY]\nauthor: CellCog\nhomepage: https://cellcog.ai\ndependencies: [cellcog]\n---\n# Diagram & Flowchart - Describe It in Words, Get It as a Diagram\n\nDescribe your system, process, or idea in plain English — CellCog produces professional, interactive diagrams you can share with a URL.\n\nNo Visio. No Lucidchart. No dragging boxes around for hours. Just describe what you need, and CellCog renders it as an interactive web page you can zoom, pan, and click — or a print-ready PDF for documentation.\n\n## How to Use\n\nFor your first CellCog task in a session, read the **cellcog** skill for the full SDK reference — file handling, chat modes, timeouts, and more.\n\n**OpenClaw (fire-and-forget):**\n```python\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    notify_session_key=\"agent:main:main\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\n```\n\n**All agents except OpenClaw (blocks until done):**\n```python\nfrom cellcog import CellCogClient\nclient = CellCogClient(agent_provider=\"openclaw|cursor|claude-code|codex|...\")\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\nprint(result[\"message\"])\n```\n\n\n---\n\n## Why Diagrams Are Hard\n\nCreating good diagrams manually is surprisingly painful:\n\n- **Layout is tedious**: Arranging boxes, arrows, and labels takes longer than the thinking itself\n- **Tools are complex**: Visio, Lucidchart, Draw.io all have learning curves\n- **Iteration is slow**: Changing one element cascades into repositioning everything\n- **Sharing is friction**: Export → attach → hope it renders on their device\n\nCellCog eliminates all of this. Describe your diagram in words, get a shareable interactive URL. Need to change something? Just ask.\n\n---\n\n## What Makes This Different\n\nOther AI diagram tools output a static image. CellCog does something fundamentally different.\n\nCellCog **reasons about your system, picks the right rendering approach, and deploys an interactive web application** you can share with a URL. Zoom into your microservices architecture. Click a node to see details. Pan across a sprawling org chart. Or export to a print-ready PDF for your board deck.\n\n| What You Ask For | What CellCog Actually Does |\n|-----------------|---------------------------|\n| \"Diagram my microservices\" | Reasons about the architecture → generates Mermaid/D3 code → deploys interactive web app → delivers shareable URL |\n| \"Flowchart for our hiring process\" | Analyzes the process → renders with proper decision logic → color-codes paths → interactive HTML with click states |\n| \"ER diagram for my database\" | Understands entity relationships → generates diagram with cardinality → exports as both interactive HTML and PDF |\n| \"Mind map for brainstorming\" | Explores the topic → creates hierarchical structure → deploys zoomable, expandable mind map |\n\nThe power comes from having a world-class coding agent, multiple rendering libraries (Mermaid.js, D3.js, custom SVG, Highcharts), and built-in app deployment — all orchestrated together. When standard tools fall short, the agent writes custom code.\n\n---\n\n## What Diagrams You Can Create\n\n### Flowcharts & Process Flows\n\nVisualize any process or decision tree:\n\n- **Business Processes**: \"Create a flowchart for our customer onboarding process — from signup to first value\"\n- **Decision Trees**: \"Build a decision tree for our support team to triage incoming tickets\"\n- **User Flows**: \"Create a user flow diagram for the checkout process in our e-commerce app\"\n- **Approval Workflows**: \"Diagram our expense approval workflow — who approves what at each dollar threshold\"\n- **Troubleshooting Guides**: \"Create a troubleshooting flowchart for common API integration errors\"\n\n**Example prompt:**\n> \"Create an interactive flowchart for our hiring process:\n> \n> Steps:\n> 1. Job posted → Applications received\n> 2. Resume screening (HR) → Pass/Fail\n> 3. Phone screen (Recruiter) → Pass/Fail\n> 4. Technical interview (Engineering) → Pass/Fail\n> 5. Culture interview (Team) → Pass/Fail\n> 6. Offer → Accept/Decline\n> 7. If decline → Back to step 2 with next candidate\n> \n> Color-code: Green for forward progress, red for rejection paths, yellow for decision points.\n> Include average time at each stage.\"\n\n### System Architecture\n\nTechnical diagrams for engineering teams:\n\n- **Microservices**: \"Diagram our microservices architecture showing all services, their communication patterns, and data stores\"\n- **Cloud Infrastructure**: \"Create an AWS architecture diagram for our production environment — VPC, ECS, RDS, ElastiCache, CloudFront\"\n- **Data Pipelines**: \"Diagram our data pipeline from raw ingestion through transformation to the analytics warehouse\"\n- **API Architecture**: \"Create an API gateway architecture showing routing, authentication, and rate limiting\"\n- **CI/CD Pipelines**: \"Diagram our deployment pipeline from git push to production\"\n\n**Example prompt:**\n> \"Create a system architecture diagram for a SaaS application:\n> \n> Frontend: React app on CloudFront/S3\n> API: FastAPI on ECS Fargate behind ALB\n> Auth: Firebase Authentication\n> Database: PostgreSQL on RDS (primary + read replica)\n> Cache: Redis on ElastiCache\n> Queue: SQS for async jobs\n> Workers: Celery on ECS\n> Storage: S3 for user uploads\n> Monitoring: CloudWatch + Datadog\n> \n> Show the data flow between components with arrows.\n> Group by VPC / public / external.\n> Interactive — I want to be able to zoom into each component.\"\n\n### Mind Maps & Concept Maps\n\nBrainstorm and organize ideas:\n\n- **Brainstorming**: \"Create a mind map exploring all possible revenue streams for our SaaS product\"\n- **Topic Exploration**: \"Build a concept map of machine learning — main branches, sub-topics, and relationships\"\n- **Content Planning**: \"Create a mind map for our Q2 content strategy — blog, social, video, email\"\n- **Strategy Mapping**: \"Map our go-to-market strategy showing channels, messaging, and target segments\"\n\n**Example prompt:**\n> \"Create an interactive mind map for 'AI in Healthcare':\n> \n> Central node: AI in Healthcare\n> \n> Main branches:\n> - Diagnostics (imaging, pathology, genomics)\n> - Drug Discovery (target identification, clinical trials, molecule design)\n> - Patient Care (chatbots, monitoring, personalized medicine)\n> - Operations (scheduling, billing, supply chain)\n> - Research (literature mining, clinical data analysis)\n> \n> Each branch should have 3-5 sub-topics with brief descriptions.\n> Color-code by maturity: green = in production, yellow = clinical trials, red = research stage.\"\n\n### Org Charts\n\nVisualize organizational structure:\n\n- **Company Hierarchy**: \"Create an org chart for a 50-person startup showing all departments and reporting lines\"\n- **Team Structure**: \"Diagram our engineering team structure — squads, tech leads, and cross-functional relationships\"\n- **Matrix Organization**: \"Create an org chart showing both functional reporting and project reporting lines\"\n\n### UML Diagrams\n\nSoftware engineering diagrams:\n\n- **Sequence Diagrams**: \"Create a sequence diagram showing the OAuth 2.0 authorization code flow\"\n- **Class Diagrams**: \"Diagram the class hierarchy for our e-commerce domain model — Product, Order, Customer, Payment\"\n- **State Diagrams**: \"Create a state diagram for an order lifecycle — placed, paid, shipped, delivered, returned\"\n- **Activity Diagrams**: \"Diagram the activity flow for our data processing pipeline\"\n\n**Example prompt:**\n> \"Create a sequence diagram for a payment processing flow:\n> \n> Actors: User, Frontend, API Server, Payment Service, Stripe, Database\n> \n> Flow:\n> 1. User clicks 'Pay' → Frontend sends payment request to API\n> 2. API creates payment intent with Stripe\n> 3. Stripe returns client secret\n> 4. API sends client secret to Frontend\n> 5. Frontend confirms payment with Stripe.js\n> 6. Stripe sends webhook to API\n> 7. API updates order status in Database\n> 8. API sends confirmation email to User\n> \n> Include error paths: payment declined, webhook timeout.\"\n\n### ER Diagrams\n\nDatabase design and data modeling:\n\n- **Database Schema**: \"Create an ER diagram for a social media platform — users, posts, comments, likes, follows\"\n- **Data Models**: \"Diagram the data model for our inventory management system\"\n- **Entity Relationships**: \"Create an ER diagram showing the relationships between customers, orders, products, and suppliers\"\n\n### Network Diagrams\n\nIT infrastructure visualization:\n\n- **Network Topology**: \"Create a network diagram showing our office network — firewalls, switches, VLANs, wireless APs\"\n- **Security Zones**: \"Diagram our network security zones — DMZ, internal, management, guest\"\n- **Cloud Networking**: \"Create a network diagram for our multi-VPC AWS setup with peering and transit gateway\"\n\n### Gantt Charts & Timelines\n\nProject planning and scheduling:\n\n- **Project Timelines**: \"Create a Gantt chart for our 6-month product launch — design, development, testing, marketing, launch\"\n- **Sprint Planning**: \"Diagram our next 3 sprints with epics, stories, and dependencies\"\n- **Roadmaps**: \"Create a product roadmap timeline for 2026 showing quarterly milestones\"\n\n### Swimlane Diagrams\n\nCross-functional process visualization:\n\n- **Cross-Team Workflows**: \"Create a swimlane diagram showing how a customer support ticket flows between Support, Engineering, and Product teams\"\n- **RACI Charts**: \"Diagram our incident response process with swimlanes for each role\"\n\n### User Journey Maps\n\nCustomer experience visualization:\n\n- **End-to-End Journeys**: \"Create a user journey map for a customer discovering, evaluating, purchasing, and onboarding to our product\"\n- **Touchpoint Mapping**: \"Map all customer touchpoints across email, web, app, and support\"\n\n---\n\n## Output Formats\n\n| Format | Features | Best For |\n|--------|----------|----------|\n| **Interactive HTML** | Zoom, pan, click, hover, responsive, shareable via URL | Presentations, team sharing, exploration |\n| **PDF** | Print-ready, static, professional | Documentation, email attachments, printing |\n\nCellCog defaults to interactive HTML — the whole point is diagrams you can explore, not static images. Request PDF explicitly when you need print-ready output.\n\n---\n\n## Choosing Mode & Tier\n\n| Scenario | Recommended |\n|----------|-------------|\n| Single diagrams and flowcharts | `chat_mode=\"agent\"` (defaults to the `\"flash\"` tier) |\n| Multi-diagram system documentation | `chat_mode=\"agent\", chat_tier=\"max\"` |\n\n**The flash tier is the default and handles most diagram work well** — fast and economical. **Upgrade to `chat_tier=\"max\"`** when quality disappoints or the work is genuinely complex: just re-run the same prompt with `chat_tier=\"max\"`.\n\nAgent Team (`chat_mode=\"team\"`) is reserved for deep research — don't use it for diagram work.\n\n---\n\n## Example Prompts\n\n**Quick flowchart:**\n> \"Create a flowchart for returning a product on our e-commerce site. Include: initiate return → reason selection → approval check → shipping label → refund processing → confirmation. Show the happy path and the rejection path.\"\n\n**Architecture diagram:**\n> \"Diagram our production infrastructure:\n> \n> Load Balancer → 3 API servers → PostgreSQL (primary + replica)\n> API servers also talk to Redis cache and S3 for file storage\n> Background workers pull from SQS queue\n> Everything monitored by Datadog\n> \n> Show it as a clean architecture diagram with arrows showing data flow direction.\"\n\n**Mind map:**\n> \"Create a mind map for planning a product launch:\n> \n> Center: Product Launch\n> Branches: Marketing, Engineering, Sales, Support, Legal\n> Each branch should have 4-6 specific tasks\n> Color-code by priority: red = critical path, yellow = important, green = nice to have\"\n\n**Database ER diagram:**\n> \"Create an ER diagram for a project management tool:\n> \n> Entities: User, Organization, Project, Task, Comment, Attachment, Label\n> \n> Key relationships:\n> - Users belong to Organizations (many-to-many)\n> - Projects belong to Organizations\n> - Tasks belong to Projects, assigned to Users\n> - Comments belong to Tasks, created by Users\n> - Tasks can have multiple Labels (many-to-many)\n> \n> Show primary keys, foreign keys, and cardinality.\"\n\n---\n\n## Tips for Better Diagrams\n\n1. **Describe the components and relationships**: \"A connects to B which talks to C\" is all CellCog needs. Don't worry about layout.\n\n2. **Specify the diagram type**: \"Flowchart\", \"sequence diagram\", \"ER diagram\" — naming the type helps CellCog choose the right rendering approach.\n\n3. **Include data flow direction**: For architecture diagrams, mention which way data flows. \"Frontend → API → Database\" is clearer than just listing components.\n\n4. **Request interactivity**: \"I want to zoom in\" or \"clickable components\" tells CellCog to build an interactive experience.\n\n5. **Color-coding helps**: \"Color-code by team\" or \"green for success paths, red for error paths\" makes diagrams immediately useful.\n\n6. **Think about audience**: \"For the engineering team\" vs. \"for the board presentation\" changes the level of technical detail.\n\n---\n\n## If CellCog is not installed\n\n**Claude Code, Cursor, Codex + 70 more agents:** `npx skills add cellcog/skills --skill cellcog`\n**OpenClaw:** `clawhub install cellcog`\n**CellCog plugin users:** run `/cellcog-setup` (or `/cellcog:cellcog-setup` depending on your tool)\n**Manual setup:** `pip install -U cellcog` and set `CELLCOG_API_KEY`. See the **cellcog** skill for SDK reference.\n\nFile v1.0.9:_meta.json\n\n{\n  \"ownerId\": \"kn7a96cj9q65e0bhmzahv790en80ffqm\",\n  \"slug\": \"diagram-flowchart-cellcog\",\n  \"version\": \"1.0.9\",\n  \"publishedAt\": 1787535980884\n}\n\nFile v1.0.9:skill-card.md\n\n## Description:\n\nFlowchart is a CellCog skill that turns plain-language requests into interactive diagrams or print-ready PDFs for flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, and network diagrams.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[cellcog](https://clawhub.ai/user/cellcog)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, architects, product teams, and operations teams use this skill to turn process descriptions, system designs, data models, timelines, and organizational structures into interactive diagrams or PDF outputs.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: Prompts may include secrets, credentials, regulated data, or confidential internal architecture sent to an external service.\n\nMitigation: Use this skill only with data your organization approves for CellCog, and remove sensitive details from prompts before submission.\n\nRisk: Generated interactive URLs may be shareable external artifacts.\n\nMitigation: Review CellCog visibility and retention controls before sharing generated links or using them in internal documentation.\n\n## Reference(s):\n\n- [ClawHub Flowchart skill page](https://clawhub.ai/cellcog/skills/diagram-flowchart-cellcog)\n- [CellCog homepage](https://cellcog.ai)\n\n## Skill Output:\n\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance]\n\n**Output Format:** [Markdown guidance with Python examples; CellCog tasks return shareable interactive HTML URLs or PDF artifacts.]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Requires python3 and CELLCOG_API_KEY; server metadata lists darwin, linux, and windows support.]\n\n## Skill Version(s):\n\n1.0.9 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.\n\nArchive v1.0.8: 3 files, 7321 bytes\n\nFiles: skill-card.md (2008b), SKILL.md (13939b), _meta.json (144b)\n\nFile v1.0.8:SKILL.md\n\n---\nname: diagram-flowchart-cellcog\ndescription: \"AI diagram and flowchart generation powered by CellCog. Flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, network diagrams. Describe your system in plain English, get interactive diagrams or print-ready PDFs.\"\nmetadata:\n  openclaw:\n    emoji: \"🔀\"\n    os: [darwin, linux, windows]\n    requires:\n      bins: [python3]\n      env: [CELLCOG_API_KEY]\nauthor: CellCog\nhomepage: https://cellcog.ai\ndependencies: [cellcog]\n---\n# Diagram & Flowchart - Describe It in Words, Get It as a Diagram\n\nDescribe your system, process, or idea in plain English — CellCog produces professional, interactive diagrams you can share with a URL.\n\nNo Visio. No Lucidchart. No dragging boxes around for hours. Just describe what you need, and CellCog renders it as an interactive web page you can zoom, pan, and click — or a print-ready PDF for documentation.\n\n## How to Use\n\nFor your first CellCog task in a session, read the **cellcog** skill for the full SDK reference — file handling, chat modes, timeouts, and more.\n\n**OpenClaw (fire-and-forget):**\n```python\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    notify_session_key=\"agent:main:main\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\n```\n\n**All agents except OpenClaw (blocks until done):**\n```python\nfrom cellcog import CellCogClient\nclient = CellCogClient(agent_provider=\"openclaw|cursor|claude-code|codex|...\")\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\nprint(result[\"message\"])\n```\n\n\n---\n\n## Why Diagrams Are Hard\n\nCreating good diagrams manually is surprisingly painful:\n\n- **Layout is tedious**: Arranging boxes, arrows, and labels takes longer than the thinking itself\n- **Tools are complex**: Visio, Lucidchart, Draw.io all have learning curves\n- **Iteration is slow**: Changing one element cascades into repositioning everything\n- **Sharing is friction**: Export → attach → hope it renders on their device\n\nCellCog eliminates all of this. Describe your diagram in words, get a shareable interactive URL. Need to change something? Just ask.\n\n---\n\n## What Makes This Different\n\nOther AI diagram tools output a static image. CellCog does something fundamentally different.\n\nCellCog **reasons about your system, picks the right rendering approach, and deploys an interactive web application** you can share with a URL. Zoom into your microservices architecture. Click a node to see details. Pan across a sprawling org chart. Or export to a print-ready PDF for your board deck.\n\n| What You Ask For | What CellCog Actually Does |\n|-----------------|---------------------------|\n| \"Diagram my microservices\" | Reasons about the architecture → generates Mermaid/D3 code → deploys interactive web app → delivers shareable URL |\n| \"Flowchart for our hiring process\" | Analyzes the process → renders with proper decision logic → color-codes paths → interactive HTML with click states |\n| \"ER diagram for my database\" | Understands entity relationships → generates diagram with cardinality → exports as both interactive HTML and PDF |\n| \"Mind map for brainstorming\" | Explores the topic → creates hierarchical structure → deploys zoomable, expandable mind map |\n\nThe power comes from having a world-class coding agent, multiple rendering libraries (Mermaid.js, D3.js, custom SVG, Highcharts), and built-in app deployment — all orchestrated together. When standard tools fall short, the agent writes custom code.\n\n---\n\n## What Diagrams You Can Create\n\n### Flowcharts & Process Flows\n\nVisualize any process or decision tree:\n\n- **Business Processes**: \"Create a flowchart for our customer onboarding process — from signup to first value\"\n- **Decision Trees**: \"Build a decision tree for our support team to triage incoming tickets\"\n- **User Flows**: \"Create a user flow diagram for the checkout process in our e-commerce app\"\n- **Approval Workflows**: \"Diagram our expense approval workflow — who approves what at each dollar threshold\"\n- **Troubleshooting Guides**: \"Create a troubleshooting flowchart for common API integration errors\"\n\n**Example prompt:**\n> \"Create an interactive flowchart for our hiring process:\n> \n> Steps:\n> 1. Job posted → Applications received\n> 2. Resume screening (HR) → Pass/Fail\n> 3. Phone screen (Recruiter) → Pass/Fail\n> 4. Technical interview (Engineering) → Pass/Fail\n> 5. Culture interview (Team) → Pass/Fail\n> 6. Offer → Accept/Decline\n> 7. If decline → Back to step 2 with next candidate\n> \n> Color-code: Green for forward progress, red for rejection paths, yellow for decision points.\n> Include average time at each stage.\"\n\n### System Architecture\n\nTechnical diagrams for engineering teams:\n\n- **Microservices**: \"Diagram our microservices architecture showing all services, their communication patterns, and data stores\"\n- **Cloud Infrastructure**: \"Create an AWS architecture diagram for our production environment — VPC, ECS, RDS, ElastiCache, CloudFront\"\n- **Data Pipelines**: \"Diagram our data pipeline from raw ingestion through transformation to the analytics warehouse\"\n- **API Architecture**: \"Create an API gateway architecture showing routing, authentication, and rate limiting\"\n- **CI/CD Pipelines**: \"Diagram our deployment pipeline from git push to production\"\n\n**Example prompt:**\n> \"Create a system architecture diagram for a SaaS application:\n> \n> Frontend: React app on CloudFront/S3\n> API: FastAPI on ECS Fargate behind ALB\n> Auth: Firebase Authentication\n> Database: PostgreSQL on RDS (primary + read replica)\n> Cache: Redis on ElastiCache\n> Queue: SQS for async jobs\n> Workers: Celery on ECS\n> Storage: S3 for user uploads\n> Monitoring: CloudWatch + Datadog\n> \n> Show the data flow between components with arrows.\n> Group by VPC / public / external.\n> Interactive — I want to be able to zoom into each component.\"\n\n### Mind Maps & Concept Maps\n\nBrainstorm and organize ideas:\n\n- **Brainstorming**: \"Create a mind map exploring all possible revenue streams for our SaaS product\"\n- **Topic Exploration**: \"Build a concept map of machine learning — main branches, sub-topics, and relationships\"\n- **Content Planning**: \"Create a mind map for our Q2 content strategy — blog, social, video, email\"\n- **Strategy Mapping**: \"Map our go-to-market strategy showing channels, messaging, and target segments\"\n\n**Example prompt:**\n> \"Create an interactive mind map for 'AI in Healthcare':\n> \n> Central node: AI in Healthcare\n> \n> Main branches:\n> - Diagnostics (imaging, pathology, genomics)\n> - Drug Discovery (target identification, clinical trials, molecule design)\n> - Patient Care (chatbots, monitoring, personalized medicine)\n> - Operations (scheduling, billing, supply chain)\n> - Research (literature mining, clinical data analysis)\n> \n> Each branch should have 3-5 sub-topics with brief descriptions.\n> Color-code by maturity: green = in production, yellow = clinical trials, red = research stage.\"\n\n### Org Charts\n\nVisualize organizational structure:\n\n- **Company Hierarchy**: \"Create an org chart for a 50-person startup showing all departments and reporting lines\"\n- **Team Structure**: \"Diagram our engineering team structure — squads, tech leads, and cross-functional relationships\"\n- **Matrix Organization**: \"Create an org chart showing both functional reporting and project reporting lines\"\n\n### UML Diagrams\n\nSoftware engineering diagrams:\n\n- **Sequence Diagrams**: \"Create a sequence diagram showing the OAuth 2.0 authorization code flow\"\n- **Class Diagrams**: \"Diagram the class hierarchy for our e-commerce domain model — Product, Order, Customer, Payment\"\n- **State Diagrams**: \"Create a state diagram for an order lifecycle — placed, paid, shipped, delivered, returned\"\n- **Activity Diagrams**: \"Diagram the activity flow for our data processing pipeline\"\n\n**Example prompt:**\n> \"Create a sequence diagram for a payment processing flow:\n> \n> Actors: User, Frontend, API Server, Payment Service, Stripe, Database\n> \n> Flow:\n> 1. User clicks 'Pay' → Frontend sends payment request to API\n> 2. API creates payment intent with Stripe\n> 3. Stripe returns client secret\n> 4. API sends client secret to Frontend\n> 5. Frontend confirms payment with Stripe.js\n> 6. Stripe sends webhook to API\n> 7. API updates order status in Database\n> 8. API sends confirmation email to User\n> \n> Include error paths: payment declined, webhook timeout.\"\n\n### ER Diagrams\n\nDatabase design and data modeling:\n\n- **Database Schema**: \"Create an ER diagram for a social media platform — users, posts, comments, likes, follows\"\n- **Data Models**: \"Diagram the data model for our inventory management system\"\n- **Entity Relationships**: \"Create an ER diagram showing the relationships between customers, orders, products, and suppliers\"\n\n### Network Diagrams\n\nIT infrastructure visualization:\n\n- **Network Topology**: \"Create a network diagram showing our office network — firewalls, switches, VLANs, wireless APs\"\n- **Security Zones**: \"Diagram our network security zones — DMZ, internal, management, guest\"\n- **Cloud Networking**: \"Create a network diagram for our multi-VPC AWS setup with peering and transit gateway\"\n\n### Gantt Charts & Timelines\n\nProject planning and scheduling:\n\n- **Project Timelines**: \"Create a Gantt chart for our 6-month product launch — design, development, testing, marketing, launch\"\n- **Sprint Planning**: \"Diagram our next 3 sprints with epics, stories, and dependencies\"\n- **Roadmaps**: \"Create a product roadmap timeline for 2026 showing quarterly milestones\"\n\n### Swimlane Diagrams\n\nCross-functional process visualization:\n\n- **Cross-Team Workflows**: \"Create a swimlane diagram showing how a customer support ticket flows between Support, Engineering, and Product teams\"\n- **RACI Charts**: \"Diagram our incident response process with swimlanes for each role\"\n\n### User Journey Maps\n\nCustomer experience visualization:\n\n- **End-to-End Journeys**: \"Create a user journey map for a customer discovering, evaluating, purchasing, and onboarding to our product\"\n- **Touchpoint Mapping**: \"Map all customer touchpoints across email, web, app, and support\"\n\n---\n\n## Output Formats\n\n| Format | Features | Best For |\n|--------|----------|----------|\n| **Interactive HTML** | Zoom, pan, click, hover, responsive, shareable via URL | Presentations, team sharing, exploration |\n| **PDF** | Print-ready, static, professional | Documentation, email attachments, printing |\n\nCellCog defaults to interactive HTML — the whole point is diagrams you can explore, not static images. Request PDF explicitly when you need print-ready output.\n\n---\n\n## Chat Mode for Diagrams\n\n| Scenario | Recommended Mode |\n|----------|------------------|\n| Individual diagrams — flowcharts, org charts, ER diagrams, mind maps | `\"agent\"` |\n| Complex multi-diagram documentation, full system design docs with multiple views | `\"agent team\"` |\n\n**Use `\"agent\"` for most diagrams.** Individual flowcharts, architecture diagrams, and org charts execute well in agent mode.\n\n**Use `\"agent team\"` for comprehensive documentation** — when you need multiple interconnected diagrams that form a complete system design document.\n\n---\n\n## Example Prompts\n\n**Quick flowchart:**\n> \"Create a flowchart for returning a product on our e-commerce site. Include: initiate return → reason selection → approval check → shipping label → refund processing → confirmation. Show the happy path and the rejection path.\"\n\n**Architecture diagram:**\n> \"Diagram our production infrastructure:\n> \n> Load Balancer → 3 API servers → PostgreSQL (primary + replica)\n> API servers also talk to Redis cache and S3 for file storage\n> Background workers pull from SQS queue\n> Everything monitored by Datadog\n> \n> Show it as a clean architecture diagram with arrows showing data flow direction.\"\n\n**Mind map:**\n> \"Create a mind map for planning a product launch:\n> \n> Center: Product Launch\n> Branches: Marketing, Engineering, Sales, Support, Legal\n> Each branch should have 4-6 specific tasks\n> Color-code by priority: red = critical path, yellow = important, green = nice to have\"\n\n**Database ER diagram:**\n> \"Create an ER diagram for a project management tool:\n> \n> Entities: User, Organization, Project, Task, Comment, Attachment, Label\n> \n> Key relationships:\n> - Users belong to Organizations (many-to-many)\n> - Projects belong to Organizations\n> - Tasks belong to Projects, assigned to Users\n> - Comments belong to Tasks, created by Users\n> - Tasks can have multiple Labels (many-to-many)\n> \n> Show primary keys, foreign keys, and cardinality.\"\n\n---\n\n## Tips for Better Diagrams\n\n1. **Describe the components and relationships**: \"A connects to B which talks to C\" is all CellCog needs. Don't worry about layout.\n\n2. **Specify the diagram type**: \"Flowchart\", \"sequence diagram\", \"ER diagram\" — naming the type helps CellCog choose the right rendering approach.\n\n3. **Include data flow direction**: For architecture diagrams, mention which way data flows. \"Frontend → API → Database\" is clearer than just listing components.\n\n4. **Request interactivity**: \"I want to zoom in\" or \"clickable components\" tells CellCog to build an interactive experience.\n\n5. **Color-coding helps**: \"Color-code by team\" or \"green for success paths, red for error paths\" makes diagrams immediately useful.\n\n6. **Think about audience**: \"For the engineering team\" vs. \"for the board presentation\" changes the level of technical detail.\n\n---\n\n## If CellCog is not installed\n\n**Claude Code, Cursor, Codex + 70 more agents:** `npx skills add cellcog/skills --skill cellcog`\n**OpenClaw:** `clawhub install cellcog`\n**CellCog plugin users:** run `/cellcog-setup` (or `/cellcog:cellcog-setup` depending on your tool)\n**Manual setup:** `pip install -U cellcog` and set `CELLCOG_API_KEY`. See the **cellcog** skill for SDK reference.\n\nFile v1.0.8:_meta.json\n\n{\n  \"ownerId\": \"kn7a96cj9q65e0bhmzahv790en80ffqm\",\n  \"slug\": \"diagram-flowchart-cellcog\",\n  \"version\": \"1.0.8\",\n  \"publishedAt\": 1785737194349\n}\n\nFile v1.0.8:skill-card.md\n\n## Description: <br>\nFlowchart helps agents generate interactive diagrams and print-ready PDFs from plain-English descriptions using CellCog. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[cellcog](https://clawhub.ai/user/cellcog) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers, operators, and business teams use this skill to turn process, architecture, data model, roadmap, and organization descriptions into shareable diagrams or PDFs. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Diagram prompts and related content are sent to CellCog. <br>\nMitigation: Avoid including secrets, credentials, regulated data, or sensitive internal architecture unless organizational policy approves that use. <br>\nRisk: Generated diagrams may be shareable hosted outputs. <br>\nMitigation: Review generated diagrams before sharing and limit prompts or outputs that reveal sensitive architecture or business processes. <br>\n\n\n## Reference(s): <br>\n- [Flowchart skill listing](https://clawhub.ai/cellcog/skills/diagram-flowchart-cellcog) <br>\n- [CellCog homepage](https://cellcog.ai) <br>\n- [CellCog publisher profile](https://clawhub.ai/user/cellcog) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [Guidance, Code, API Calls, Configuration instructions] <br>\n**Output Format:** [Markdown guidance with Python code examples and hosted diagram output links] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Requires CELLCOG_API_KEY; outputs may include interactive HTML URLs or PDF artifacts created by CellCog.] <br>\n\n## Skill Version(s): <br>\n1.0.8 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.7: 3 files, 7405 bytes\n\nFiles: skill-card.md (2280b), SKILL.md (13864b), _meta.json (144b)\n\nFile v1.0.7:SKILL.md\n\n---\nname: diagram-flowchart-cellcog\ndescription: \"AI diagram and flowchart generation powered by CellCog. Flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, network diagrams. Describe your system in plain English, get interactive diagrams or print-ready PDFs.\"\nmetadata:\n  openclaw:\n    emoji: \"🔀\"\n    os: [darwin, linux, windows]\n    requires:\n      bins: [python3]\n      env: [CELLCOG_API_KEY]\nauthor: CellCog\nhomepage: https://cellcog.ai\ndependencies: [cellcog]\n---\n# Diagram & Flowchart - Describe It in Words, Get It as a Diagram\n\nDescribe your system, process, or idea in plain English — CellCog produces professional, interactive diagrams you can share with a URL.\n\nNo Visio. No Lucidchart. No dragging boxes around for hours. Just describe what you need, and CellCog renders it as an interactive web page you can zoom, pan, and click — or a print-ready PDF for documentation.\n\n## How to Use\n\nFor your first CellCog task in a session, read the **cellcog** skill for the full SDK reference — file handling, chat modes, timeouts, and more.\n\n**OpenClaw (fire-and-forget):**\n```python\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    notify_session_key=\"agent:main:main\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\n```\n\n**All agents except OpenClaw (blocks until done):**\n```python\nfrom cellcog import CellCogClient\nclient = CellCogClient(agent_provider=\"openclaw|cursor|claude-code|codex|...\")\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\nprint(result[\"message\"])\n```\n\n\n---\n\n## Why Diagrams Are Hard\n\nCreating good diagrams manually is surprisingly painful:\n\n- **Layout is tedious**: Arranging boxes, arrows, and labels takes longer than the thinking itself\n- **Tools are complex**: Visio, Lucidchart, Draw.io all have learning curves\n- **Iteration is slow**: Changing one element cascades into repositioning everything\n- **Sharing is friction**: Export → attach → hope it renders on their device\n\nCellCog eliminates all of this. Describe your diagram in words, get a shareable interactive URL. Need to change something? Just ask.\n\n---\n\n## What Makes This Different\n\nOther AI diagram tools output a static image. CellCog does something fundamentally different.\n\nCellCog **reasons about your system, picks the right rendering approach, and deploys an interactive web application** you can share with a URL. Zoom into your microservices architecture. Click a node to see details. Pan across a sprawling org chart. Or export to a print-ready PDF for your board deck.\n\n| What You Ask For | What CellCog Actually Does |\n|-----------------|---------------------------|\n| \"Diagram my microservices\" | Reasons about the architecture → generates Mermaid/D3 code → deploys interactive web app → delivers shareable URL |\n| \"Flowchart for our hiring process\" | Analyzes the process → renders with proper decision logic → color-codes paths → interactive HTML with click states |\n| \"ER diagram for my database\" | Understands entity relationships → generates diagram with cardinality → exports as both interactive HTML and PDF |\n| \"Mind map for brainstorming\" | Explores the topic → creates hierarchical structure → deploys zoomable, expandable mind map |\n\nThe power comes from having a world-class coding agent, multiple rendering libraries (Mermaid.js, D3.js, custom SVG, Highcharts), and built-in app deployment — all orchestrated together. When standard tools fall short, the agent writes custom code.\n\n---\n\n## What Diagrams You Can Create\n\n### Flowcharts & Process Flows\n\nVisualize any process or decision tree:\n\n- **Business Processes**: \"Create a flowchart for our customer onboarding process — from signup to first value\"\n- **Decision Trees**: \"Build a decision tree for our support team to triage incoming tickets\"\n- **User Flows**: \"Create a user flow diagram for the checkout process in our e-commerce app\"\n- **Approval Workflows**: \"Diagram our expense approval workflow — who approves what at each dollar threshold\"\n- **Troubleshooting Guides**: \"Create a troubleshooting flowchart for common API integration errors\"\n\n**Example prompt:**\n> \"Create an interactive flowchart for our hiring process:\n> \n> Steps:\n> 1. Job posted → Applications received\n> 2. Resume screening (HR) → Pass/Fail\n> 3. Phone screen (Recruiter) → Pass/Fail\n> 4. Technical interview (Engineering) → Pass/Fail\n> 5. Culture interview (Team) → Pass/Fail\n> 6. Offer → Accept/Decline\n> 7. If decline → Back to step 2 with next candidate\n> \n> Color-code: Green for forward progress, red for rejection paths, yellow for decision points.\n> Include average time at each stage.\"\n\n### System Architecture\n\nTechnical diagrams for engineering teams:\n\n- **Microservices**: \"Diagram our microservices architecture showing all services, their communication patterns, and data stores\"\n- **Cloud Infrastructure**: \"Create an AWS architecture diagram for our production environment — VPC, ECS, RDS, ElastiCache, CloudFront\"\n- **Data Pipelines**: \"Diagram our data pipeline from raw ingestion through transformation to the analytics warehouse\"\n- **API Architecture**: \"Create an API gateway architecture showing routing, authentication, and rate limiting\"\n- **CI/CD Pipelines**: \"Diagram our deployment pipeline from git push to production\"\n\n**Example prompt:**\n> \"Create a system architecture diagram for a SaaS application:\n> \n> Frontend: React app on CloudFront/S3\n> API: FastAPI on ECS Fargate behind ALB\n> Auth: Firebase Authentication\n> Database: PostgreSQL on RDS (primary + read replica)\n> Cache: Redis on ElastiCache\n> Queue: SQS for async jobs\n> Workers: Celery on ECS\n> Storage: S3 for user uploads\n> Monitoring: CloudWatch + Datadog\n> \n> Show the data flow between components with arrows.\n> Group by VPC / public / external.\n> Interactive — I want to be able to zoom into each component.\"\n\n### Mind Maps & Concept Maps\n\nBrainstorm and organize ideas:\n\n- **Brainstorming**: \"Create a mind map exploring all possible revenue streams for our SaaS product\"\n- **Topic Exploration**: \"Build a concept map of machine learning — main branches, sub-topics, and relationships\"\n- **Content Planning**: \"Create a mind map for our Q2 content strategy — blog, social, video, email\"\n- **Strategy Mapping**: \"Map our go-to-market strategy showing channels, messaging, and target segments\"\n\n**Example prompt:**\n> \"Create an interactive mind map for 'AI in Healthcare':\n> \n> Central node: AI in Healthcare\n> \n> Main branches:\n> - Diagnostics (imaging, pathology, genomics)\n> - Drug Discovery (target identification, clinical trials, molecule design)\n> - Patient Care (chatbots, monitoring, personalized medicine)\n> - Operations (scheduling, billing, supply chain)\n> - Research (literature mining, clinical data analysis)\n> \n> Each branch should have 3-5 sub-topics with brief descriptions.\n> Color-code by maturity: green = in production, yellow = clinical trials, red = research stage.\"\n\n### Org Charts\n\nVisualize organizational structure:\n\n- **Company Hierarchy**: \"Create an org chart for a 50-person startup showing all departments and reporting lines\"\n- **Team Structure**: \"Diagram our engineering team structure — squads, tech leads, and cross-functional relationships\"\n- **Matrix Organization**: \"Create an org chart showing both functional reporting and project reporting lines\"\n\n### UML Diagrams\n\nSoftware engineering diagrams:\n\n- **Sequence Diagrams**: \"Create a sequence diagram showing the OAuth 2.0 authorization code flow\"\n- **Class Diagrams**: \"Diagram the class hierarchy for our e-commerce domain model — Product, Order, Customer, Payment\"\n- **State Diagrams**: \"Create a state diagram for an order lifecycle — placed, paid, shipped, delivered, returned\"\n- **Activity Diagrams**: \"Diagram the activity flow for our data processing pipeline\"\n\n**Example prompt:**\n> \"Create a sequence diagram for a payment processing flow:\n> \n> Actors: User, Frontend, API Server, Payment Service, Stripe, Database\n> \n> Flow:\n> 1. User clicks 'Pay' → Frontend sends payment request to API\n> 2. API creates payment intent with Stripe\n> 3. Stripe returns client secret\n> 4. API sends client secret to Frontend\n> 5. Frontend confirms payment with Stripe.js\n> 6. Stripe sends webhook to API\n> 7. API updates order status in Database\n> 8. API sends confirmation email to User\n> \n> Include error paths: payment declined, webhook timeout.\"\n\n### ER Diagrams\n\nDatabase design and data modeling:\n\n- **Database Schema**: \"Create an ER diagram for a social media platform — users, posts, comments, likes, follows\"\n- **Data Models**: \"Diagram the data model for our inventory management system\"\n- **Entity Relationships**: \"Create an ER diagram showing the relationships between customers, orders, products, and suppliers\"\n\n### Network Diagrams\n\nIT infrastructure visualization:\n\n- **Network Topology**: \"Create a network diagram showing our office network — firewalls, switches, VLANs, wireless APs\"\n- **Security Zones**: \"Diagram our network security zones — DMZ, internal, management, guest\"\n- **Cloud Networking**: \"Create a network diagram for our multi-VPC AWS setup with peering and transit gateway\"\n\n### Gantt Charts & Timelines\n\nProject planning and scheduling:\n\n- **Project Timelines**: \"Create a Gantt chart for our 6-month product launch — design, development, testing, marketing, launch\"\n- **Sprint Planning**: \"Diagram our next 3 sprints with epics, stories, and dependencies\"\n- **Roadmaps**: \"Create a product roadmap timeline for 2026 showing quarterly milestones\"\n\n### Swimlane Diagrams\n\nCross-functional process visualization:\n\n- **Cross-Team Workflows**: \"Create a swimlane diagram showing how a customer support ticket flows between Support, Engineering, and Product teams\"\n- **RACI Charts**: \"Diagram our incident response process with swimlanes for each role\"\n\n### User Journey Maps\n\nCustomer experience visualization:\n\n- **End-to-End Journeys**: \"Create a user journey map for a customer discovering, evaluating, purchasing, and onboarding to our product\"\n- **Touchpoint Mapping**: \"Map all customer touchpoints across email, web, app, and support\"\n\n---\n\n## Output Formats\n\n| Format | Features | Best For |\n|--------|----------|----------|\n| **Interactive HTML** | Zoom, pan, click, hover, responsive, shareable via URL | Presentations, team sharing, exploration |\n| **PDF** | Print-ready, static, professional | Documentation, email attachments, printing |\n\nCellCog defaults to interactive HTML — the whole point is diagrams you can explore, not static images. Request PDF explicitly when you need print-ready output.\n\n---\n\n## Chat Mode for Diagrams\n\n| Scenario | Recommended Mode |\n|----------|------------------|\n| Individual diagrams — flowcharts, org charts, ER diagrams, mind maps | `\"agent\"` |\n| Complex multi-diagram documentation, full system design docs with multiple views | `\"agent team\"` |\n\n**Use `\"agent\"` for most diagrams.** Individual flowcharts, architecture diagrams, and org charts execute well in agent mode.\n\n**Use `\"agent team\"` for comprehensive documentation** — when you need multiple interconnected diagrams that form a complete system design document.\n\n---\n\n## Example Prompts\n\n**Quick flowchart:**\n> \"Create a flowchart for returning a product on our e-commerce site. Include: initiate return → reason selection → approval check → shipping label → refund processing → confirmation. Show the happy path and the rejection path.\"\n\n**Architecture diagram:**\n> \"Diagram our production infrastructure:\n> \n> Load Balancer → 3 API servers → PostgreSQL (primary + replica)\n> API servers also talk to Redis cache and S3 for file storage\n> Background workers pull from SQS queue\n> Everything monitored by Datadog\n> \n> Show it as a clean architecture diagram with arrows showing data flow direction.\"\n\n**Mind map:**\n> \"Create a mind map for planning a product launch:\n> \n> Center: Product Launch\n> Branches: Marketing, Engineering, Sales, Support, Legal\n> Each branch should have 4-6 specific tasks\n> Color-code by priority: red = critical path, yellow = important, green = nice to have\"\n\n**Database ER diagram:**\n> \"Create an ER diagram for a project management tool:\n> \n> Entities: User, Organization, Project, Task, Comment, Attachment, Label\n> \n> Key relationships:\n> - Users belong to Organizations (many-to-many)\n> - Projects belong to Organizations\n> - Tasks belong to Projects, assigned to Users\n> - Comments belong to Tasks, created by Users\n> - Tasks can have multiple Labels (many-to-many)\n> \n> Show primary keys, foreign keys, and cardinality.\"\n\n---\n\n## Tips for Better Diagrams\n\n1. **Describe the components and relationships**: \"A connects to B which talks to C\" is all CellCog needs. Don't worry about layout.\n\n2. **Specify the diagram type**: \"Flowchart\", \"sequence diagram\", \"ER diagram\" — naming the type helps CellCog choose the right rendering approach.\n\n3. **Include data flow direction**: For architecture diagrams, mention which way data flows. \"Frontend → API → Database\" is clearer than just listing components.\n\n4. **Request interactivity**: \"I want to zoom in\" or \"clickable components\" tells CellCog to build an interactive experience.\n\n5. **Color-coding helps**: \"Color-code by team\" or \"green for success paths, red for error paths\" makes diagrams immediately useful.\n\n6. **Think about audience**: \"For the engineering team\" vs. \"for the board presentation\" changes the level of technical detail.\n\n---\n\n## If CellCog is not installed\n\nRun `/cellcog-setup` (or `/cellcog:cellcog-setup` depending on your tool) to install and authenticate.\n**OpenClaw users:** Run `clawhub install cellcog` instead.\n**Manual setup:** `pip install -U cellcog` and set `CELLCOG_API_KEY`. See the **cellcog** skill for SDK reference.\n\nFile v1.0.7:_meta.json\n\n{\n  \"ownerId\": \"kn7a96cj9q65e0bhmzahv790en80ffqm\",\n  \"slug\": \"diagram-flowchart-cellcog\",\n  \"version\": \"1.0.7\",\n  \"publishedAt\": 1785708210282\n}\n\nFile v1.0.7:skill-card.md\n\n## Description: <br>\nFlowchart helps agents generate CellCog-powered flowcharts and diagrams from plain-English prompts, including architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, and network diagrams. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[cellcog](https://clawhub.ai/user/cellcog) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers, engineers, and business users use this skill to turn process descriptions, system designs, data models, timelines, and organizational structures into interactive diagrams or print-ready PDFs. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Diagram prompts, included files, or system details may be processed by CellCog and may produce hosted or shareable outputs. <br>\nMitigation: Avoid submitting secrets, credentials, regulated data, or sensitive internal architecture unless the use has been approved by the organization. <br>\nRisk: Generated diagrams may encode incorrect architecture, process, or data-model assumptions. <br>\nMitigation: Review generated diagrams before sharing, publishing, or using them as implementation or compliance documentation. <br>\n\n\n## Reference(s): <br>\n- [ClawHub Flowchart skill page](https://clawhub.ai/cellcog/skills/diagram-flowchart-cellcog) <br>\n- [CellCog homepage](https://cellcog.ai) <br>\n- [CellCog publisher profile](https://clawhub.ai/user/cellcog) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance] <br>\n**Output Format:** [Markdown guidance with Python examples and links to hosted interactive HTML or PDF diagram outputs] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Requires python3, the cellcog dependency, and CELLCOG_API_KEY; prompts and supplied context may be sent to CellCog.] <br>\n\n## Skill Version(s): <br>\n1.0.7 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.6: 3 files, 7388 bytes\n\nFiles: skill-card.md (2255b), SKILL.md (13864b), _meta.json (144b)\n\nFile v1.0.6:SKILL.md\n\n---\nname: diagram-flowchart-cellcog\ndescription: \"AI diagram and flowchart generation powered by CellCog. Flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, network diagrams. Describe your system in plain English, get interactive diagrams or print-ready PDFs.\"\nmetadata:\n  openclaw:\n    emoji: \"🔀\"\n    os: [darwin, linux, windows]\n    requires:\n      bins: [python3]\n      env: [CELLCOG_API_KEY]\nauthor: CellCog\nhomepage: https://cellcog.ai\ndependencies: [cellcog]\n---\n# Diagram & Flowchart - Describe It in Words, Get It as a Diagram\n\nDescribe your system, process, or idea in plain English — CellCog produces professional, interactive diagrams you can share with a URL.\n\nNo Visio. No Lucidchart. No dragging boxes around for hours. Just describe what you need, and CellCog renders it as an interactive web page you can zoom, pan, and click — or a print-ready PDF for documentation.\n\n## How to Use\n\nFor your first CellCog task in a session, read the **cellcog** skill for the full SDK reference — file handling, chat modes, timeouts, and more.\n\n**OpenClaw (fire-and-forget):**\n```python\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    notify_session_key=\"agent:main:main\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\n```\n\n**All agents except OpenClaw (blocks until done):**\n```python\nfrom cellcog import CellCogClient\nclient = CellCogClient(agent_provider=\"openclaw|cursor|claude-code|codex|...\")\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\nprint(result[\"message\"])\n```\n\n\n---\n\n## Why Diagrams Are Hard\n\nCreating good diagrams manually is surprisingly painful:\n\n- **Layout is tedious**: Arranging boxes, arrows, and labels takes longer than the thinking itself\n- **Tools are complex**: Visio, Lucidchart, Draw.io all have learning curves\n- **Iteration is slow**: Changing one element cascades into repositioning everything\n- **Sharing is friction**: Export → attach → hope it renders on their device\n\nCellCog eliminates all of this. Describe your diagram in words, get a shareable interactive URL. Need to change something? Just ask.\n\n---\n\n## What Makes This Different\n\nOther AI diagram tools output a static image. CellCog does something fundamentally different.\n\nCellCog **reasons about your system, picks the right rendering approach, and deploys an interactive web application** you can share with a URL. Zoom into your microservices architecture. Click a node to see details. Pan across a sprawling org chart. Or export to a print-ready PDF for your board deck.\n\n| What You Ask For | What CellCog Actually Does |\n|-----------------|---------------------------|\n| \"Diagram my microservices\" | Reasons about the architecture → generates Mermaid/D3 code → deploys interactive web app → delivers shareable URL |\n| \"Flowchart for our hiring process\" | Analyzes the process → renders with proper decision logic → color-codes paths → interactive HTML with click states |\n| \"ER diagram for my database\" | Understands entity relationships → generates diagram with cardinality → exports as both interactive HTML and PDF |\n| \"Mind map for brainstorming\" | Explores the topic → creates hierarchical structure → deploys zoomable, expandable mind map |\n\nThe power comes from having a world-class coding agent, multiple rendering libraries (Mermaid.js, D3.js, custom SVG, Highcharts), and built-in app deployment — all orchestrated together. When standard tools fall short, the agent writes custom code.\n\n---\n\n## What Diagrams You Can Create\n\n### Flowcharts & Process Flows\n\nVisualize any process or decision tree:\n\n- **Business Processes**: \"Create a flowchart for our customer onboarding process — from signup to first value\"\n- **Decision Trees**: \"Build a decision tree for our support team to triage incoming tickets\"\n- **User Flows**: \"Create a user flow diagram for the checkout process in our e-commerce app\"\n- **Approval Workflows**: \"Diagram our expense approval workflow — who approves what at each dollar threshold\"\n- **Troubleshooting Guides**: \"Create a troubleshooting flowchart for common API integration errors\"\n\n**Example prompt:**\n> \"Create an interactive flowchart for our hiring process:\n> \n> Steps:\n> 1. Job posted → Applications received\n> 2. Resume screening (HR) → Pass/Fail\n> 3. Phone screen (Recruiter) → Pass/Fail\n> 4. Technical interview (Engineering) → Pass/Fail\n> 5. Culture interview (Team) → Pass/Fail\n> 6. Offer → Accept/Decline\n> 7. If decline → Back to step 2 with next candidate\n> \n> Color-code: Green for forward progress, red for rejection paths, yellow for decision points.\n> Include average time at each stage.\"\n\n### System Architecture\n\nTechnical diagrams for engineering teams:\n\n- **Microservices**: \"Diagram our microservices architecture showing all services, their communication patterns, and data stores\"\n- **Cloud Infrastructure**: \"Create an AWS architecture diagram for our production environment — VPC, ECS, RDS, ElastiCache, CloudFront\"\n- **Data Pipelines**: \"Diagram our data pipeline from raw ingestion through transformation to the analytics warehouse\"\n- **API Architecture**: \"Create an API gateway architecture showing routing, authentication, and rate limiting\"\n- **CI/CD Pipelines**: \"Diagram our deployment pipeline from git push to production\"\n\n**Example prompt:**\n> \"Create a system architecture diagram for a SaaS application:\n> \n> Frontend: React app on CloudFront/S3\n> API: FastAPI on ECS Fargate behind ALB\n> Auth: Firebase Authentication\n> Database: PostgreSQL on RDS (primary + read replica)\n> Cache: Redis on ElastiCache\n> Queue: SQS for async jobs\n> Workers: Celery on ECS\n> Storage: S3 for user uploads\n> Monitoring: CloudWatch + Datadog\n> \n> Show the data flow between components with arrows.\n> Group by VPC / public / external.\n> Interactive — I want to be able to zoom into each component.\"\n\n### Mind Maps & Concept Maps\n\nBrainstorm and organize ideas:\n\n- **Brainstorming**: \"Create a mind map exploring all possible revenue streams for our SaaS product\"\n- **Topic Exploration**: \"Build a concept map of machine learning — main branches, sub-topics, and relationships\"\n- **Content Planning**: \"Create a mind map for our Q2 content strategy — blog, social, video, email\"\n- **Strategy Mapping**: \"Map our go-to-market strategy showing channels, messaging, and target segments\"\n\n**Example prompt:**\n> \"Create an interactive mind map for 'AI in Healthcare':\n> \n> Central node: AI in Healthcare\n> \n> Main branches:\n> - Diagnostics (imaging, pathology, genomics)\n> - Drug Discovery (target identification, clinical trials, molecule design)\n> - Patient Care (chatbots, monitoring, personalized medicine)\n> - Operations (scheduling, billing, supply chain)\n> - Research (literature mining, clinical data analysis)\n> \n> Each branch should have 3-5 sub-topics with brief descriptions.\n> Color-code by maturity: green = in production, yellow = clinical trials, red = research stage.\"\n\n### Org Charts\n\nVisualize organizational structure:\n\n- **Company Hierarchy**: \"Create an org chart for a 50-person startup showing all departments and reporting lines\"\n- **Team Structure**: \"Diagram our engineering team structure — squads, tech leads, and cross-functional relationships\"\n- **Matrix Organization**: \"Create an org chart showing both functional reporting and project reporting lines\"\n\n### UML Diagrams\n\nSoftware engineering diagrams:\n\n- **Sequence Diagrams**: \"Create a sequence diagram showing the OAuth 2.0 authorization code flow\"\n- **Class Diagrams**: \"Diagram the class hierarchy for our e-commerce domain model — Product, Order, Customer, Payment\"\n- **State Diagrams**: \"Create a state diagram for an order lifecycle — placed, paid, shipped, delivered, returned\"\n- **Activity Diagrams**: \"Diagram the activity flow for our data processing pipeline\"\n\n**Example prompt:**\n> \"Create a sequence diagram for a payment processing flow:\n> \n> Actors: User, Frontend, API Server, Payment Service, Stripe, Database\n> \n> Flow:\n> 1. User clicks 'Pay' → Frontend sends payment request to API\n> 2. API creates payment intent with Stripe\n> 3. Stripe returns client secret\n> 4. API sends client secret to Frontend\n> 5. Frontend confirms payment with Stripe.js\n> 6. Stripe sends webhook to API\n> 7. API updates order status in Database\n> 8. API sends confirmation email to User\n> \n> Include error paths: payment declined, webhook timeout.\"\n\n### ER Diagrams\n\nDatabase design and data modeling:\n\n- **Database Schema**: \"Create an ER diagram for a social media platform — users, posts, comments, likes, follows\"\n- **Data Models**: \"Diagram the data model for our inventory management system\"\n- **Entity Relationships**: \"Create an ER diagram showing the relationships between customers, orders, products, and suppliers\"\n\n### Network Diagrams\n\nIT infrastructure visualization:\n\n- **Network Topology**: \"Create a network diagram showing our office network — firewalls, switches, VLANs, wireless APs\"\n- **Security Zones**: \"Diagram our network security zones — DMZ, internal, management, guest\"\n- **Cloud Networking**: \"Create a network diagram for our multi-VPC AWS setup with peering and transit gateway\"\n\n### Gantt Charts & Timelines\n\nProject planning and scheduling:\n\n- **Project Timelines**: \"Create a Gantt chart for our 6-month product launch — design, development, testing, marketing, launch\"\n- **Sprint Planning**: \"Diagram our next 3 sprints with epics, stories, and dependencies\"\n- **Roadmaps**: \"Create a product roadmap timeline for 2026 showing quarterly milestones\"\n\n### Swimlane Diagrams\n\nCross-functional process visualization:\n\n- **Cross-Team Workflows**: \"Create a swimlane diagram showing how a customer support ticket flows between Support, Engineering, and Product teams\"\n- **RACI Charts**: \"Diagram our incident response process with swimlanes for each role\"\n\n### User Journey Maps\n\nCustomer experience visualization:\n\n- **End-to-End Journeys**: \"Create a user journey map for a customer discovering, evaluating, purchasing, and onboarding to our product\"\n- **Touchpoint Mapping**: \"Map all customer touchpoints across email, web, app, and support\"\n\n---\n\n## Output Formats\n\n| Format | Features | Best For |\n|--------|----------|----------|\n| **Interactive HTML** | Zoom, pan, click, hover, responsive, shareable via URL | Presentations, team sharing, exploration |\n| **PDF** | Print-ready, static, professional | Documentation, email attachments, printing |\n\nCellCog defaults to interactive HTML — the whole point is diagrams you can explore, not static images. Request PDF explicitly when you need print-ready output.\n\n---\n\n## Chat Mode for Diagrams\n\n| Scenario | Recommended Mode |\n|----------|------------------|\n| Individual diagrams — flowcharts, org charts, ER diagrams, mind maps | `\"agent\"` |\n| Complex multi-diagram documentation, full system design docs with multiple views | `\"agent team\"` |\n\n**Use `\"agent\"` for most diagrams.** Individual flowcharts, architecture diagrams, and org charts execute well in agent mode.\n\n**Use `\"agent team\"` for comprehensive documentation** — when you need multiple interconnected diagrams that form a complete system design document.\n\n---\n\n## Example Prompts\n\n**Quick flowchart:**\n> \"Create a flowchart for returning a product on our e-commerce site. Include: initiate return → reason selection → approval check → shipping label → refund processing → confirmation. Show the happy path and the rejection path.\"\n\n**Architecture diagram:**\n> \"Diagram our production infrastructure:\n> \n> Load Balancer → 3 API servers → PostgreSQL (primary + replica)\n> API servers also talk to Redis cache and S3 for file storage\n> Background workers pull from SQS queue\n> Everything monitored by Datadog\n> \n> Show it as a clean architecture diagram with arrows showing data flow direction.\"\n\n**Mind map:**\n> \"Create a mind map for planning a product launch:\n> \n> Center: Product Launch\n> Branches: Marketing, Engineering, Sales, Support, Legal\n> Each branch should have 4-6 specific tasks\n> Color-code by priority: red = critical path, yellow = important, green = nice to have\"\n\n**Database ER diagram:**\n> \"Create an ER diagram for a project management tool:\n> \n> Entities: User, Organization, Project, Task, Comment, Attachment, Label\n> \n> Key relationships:\n> - Users belong to Organizations (many-to-many)\n> - Projects belong to Organizations\n> - Tasks belong to Projects, assigned to Users\n> - Comments belong to Tasks, created by Users\n> - Tasks can have multiple Labels (many-to-many)\n> \n> Show primary keys, foreign keys, and cardinality.\"\n\n---\n\n## Tips for Better Diagrams\n\n1. **Describe the components and relationships**: \"A connects to B which talks to C\" is all CellCog needs. Don't worry about layout.\n\n2. **Specify the diagram type**: \"Flowchart\", \"sequence diagram\", \"ER diagram\" — naming the type helps CellCog choose the right rendering approach.\n\n3. **Include data flow direction**: For architecture diagrams, mention which way data flows. \"Frontend → API → Database\" is clearer than just listing components.\n\n4. **Request interactivity**: \"I want to zoom in\" or \"clickable components\" tells CellCog to build an interactive experience.\n\n5. **Color-coding helps**: \"Color-code by team\" or \"green for success paths, red for error paths\" makes diagrams immediately useful.\n\n6. **Think about audience**: \"For the engineering team\" vs. \"for the board presentation\" changes the level of technical detail.\n\n---\n\n## If CellCog is not installed\n\nRun `/cellcog-setup` (or `/cellcog:cellcog-setup` depending on your tool) to install and authenticate.\n**OpenClaw users:** Run `clawhub install cellcog` instead.\n**Manual setup:** `pip install -U cellcog` and set `CELLCOG_API_KEY`. See the **cellcog** skill for SDK reference.\n\nFile v1.0.6:_meta.json\n\n{\n  \"ownerId\": \"kn7a96cj9q65e0bhmzahv790en80ffqm\",\n  \"slug\": \"diagram-flowchart-cellcog\",\n  \"version\": \"1.0.6\",\n  \"publishedAt\": 1784259655189\n}\n\nFile v1.0.6:skill-card.md\n\n## Description: <br>\nGenerates interactive diagrams and flowcharts from plain-language prompts using CellCog, including system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, network diagrams, and print-ready PDFs. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[nitishgargiitd](https://clawhub.ai/user/nitishgargiitd) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers, product teams, and business users use this skill to turn plain-language descriptions of systems, processes, data models, timelines, and journeys into interactive diagrams or PDFs. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Diagram prompts and shareable diagram URLs may expose sensitive architecture, network, regulated personal data, or credentials. <br>\nMitigation: Do not submit secrets, credentials, regulated personal data, or internal-only architecture or network details unless CellCog privacy and sharing controls are verified for the use case. <br>\nRisk: The skill requires a CellCog API key for operation. <br>\nMitigation: Store CELLCOG_API_KEY as an environment variable or secret and avoid placing API keys in prompts, diagrams, source files, or generated outputs. <br>\n\n\n## Reference(s): <br>\n- [CellCog](https://cellcog.ai) <br>\n- [ClawHub skill page](https://clawhub.ai/nitishgargiitd/skills/diagram-flowchart-cellcog) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [text, markdown, code, shell commands, configuration, guidance, URLs, PDF] <br>\n**Output Format:** [Markdown guidance with Python snippets; CellCog responses may include shareable interactive HTML URLs or PDF outputs.] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Requires python3, the cellcog package, and CELLCOG_API_KEY; prompts are sent to CellCog.] <br>\n\n## Skill Version(s): <br>\n1.0.6 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.5: 3 files, 7422 bytes\n\nFiles: skill-card.md (2348b), SKILL.md (13828b), _meta.json (144b)\n\nFile v1.0.5:SKILL.md\n\n---\nname: diagram-cog\ndescription: \"AI diagram generation powered by CellCog. Flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, network diagrams. Describe your system in plain English, get interactive diagrams or print-ready PDFs.\"\nmetadata:\n  openclaw:\n    emoji: \"🔀\"\n    os: [darwin, linux, windows]\n    requires:\n      bins: [python3]\n      env: [CELLCOG_API_KEY]\nauthor: CellCog\nhomepage: https://cellcog.ai\ndependencies: [cellcog]\n---\n# Diagram Cog - Describe It in Words, Get It as a Diagram\n\nDescribe your system, process, or idea in plain English — CellCog produces professional, interactive diagrams you can share with a URL.\n\nNo Visio. No Lucidchart. No dragging boxes around for hours. Just describe what you need, and CellCog renders it as an interactive web page you can zoom, pan, and click — or a print-ready PDF for documentation.\n\n## How to Use\n\nFor your first CellCog task in a session, read the **cellcog** skill for the full SDK reference — file handling, chat modes, timeouts, and more.\n\n**OpenClaw (fire-and-forget):**\n```python\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    notify_session_key=\"agent:main:main\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\n```\n\n**All agents except OpenClaw (blocks until done):**\n```python\nfrom cellcog import CellCogClient\nclient = CellCogClient(agent_provider=\"openclaw|cursor|claude-code|codex|...\")\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\nprint(result[\"message\"])\n```\n\n\n---\n\n## Why Diagrams Are Hard\n\nCreating good diagrams manually is surprisingly painful:\n\n- **Layout is tedious**: Arranging boxes, arrows, and labels takes longer than the thinking itself\n- **Tools are complex**: Visio, Lucidchart, Draw.io all have learning curves\n- **Iteration is slow**: Changing one element cascades into repositioning everything\n- **Sharing is friction**: Export → attach → hope it renders on their device\n\nCellCog eliminates all of this. Describe your diagram in words, get a shareable interactive URL. Need to change something? Just ask.\n\n---\n\n## What Makes This Different\n\nOther AI diagram tools output a static image. CellCog does something fundamentally different.\n\nCellCog **reasons about your system, picks the right rendering approach, and deploys an interactive web application** you can share with a URL. Zoom into your microservices architecture. Click a node to see details. Pan across a sprawling org chart. Or export to a print-ready PDF for your board deck.\n\n| What You Ask For | What CellCog Actually Does |\n|-----------------|---------------------------|\n| \"Diagram my microservices\" | Reasons about the architecture → generates Mermaid/D3 code → deploys interactive web app → delivers shareable URL |\n| \"Flowchart for our hiring process\" | Analyzes the process → renders with proper decision logic → color-codes paths → interactive HTML with click states |\n| \"ER diagram for my database\" | Understands entity relationships → generates diagram with cardinality → exports as both interactive HTML and PDF |\n| \"Mind map for brainstorming\" | Explores the topic → creates hierarchical structure → deploys zoomable, expandable mind map |\n\nThe power comes from having a world-class coding agent, multiple rendering libraries (Mermaid.js, D3.js, custom SVG, Highcharts), and built-in app deployment — all orchestrated together. When standard tools fall short, the agent writes custom code.\n\n---\n\n## What Diagrams You Can Create\n\n### Flowcharts & Process Flows\n\nVisualize any process or decision tree:\n\n- **Business Processes**: \"Create a flowchart for our customer onboarding process — from signup to first value\"\n- **Decision Trees**: \"Build a decision tree for our support team to triage incoming tickets\"\n- **User Flows**: \"Create a user flow diagram for the checkout process in our e-commerce app\"\n- **Approval Workflows**: \"Diagram our expense approval workflow — who approves what at each dollar threshold\"\n- **Troubleshooting Guides**: \"Create a troubleshooting flowchart for common API integration errors\"\n\n**Example prompt:**\n> \"Create an interactive flowchart for our hiring process:\n> \n> Steps:\n> 1. Job posted → Applications received\n> 2. Resume screening (HR) → Pass/Fail\n> 3. Phone screen (Recruiter) → Pass/Fail\n> 4. Technical interview (Engineering) → Pass/Fail\n> 5. Culture interview (Team) → Pass/Fail\n> 6. Offer → Accept/Decline\n> 7. If decline → Back to step 2 with next candidate\n> \n> Color-code: Green for forward progress, red for rejection paths, yellow for decision points.\n> Include average time at each stage.\"\n\n### System Architecture\n\nTechnical diagrams for engineering teams:\n\n- **Microservices**: \"Diagram our microservices architecture showing all services, their communication patterns, and data stores\"\n- **Cloud Infrastructure**: \"Create an AWS architecture diagram for our production environment — VPC, ECS, RDS, ElastiCache, CloudFront\"\n- **Data Pipelines**: \"Diagram our data pipeline from raw ingestion through transformation to the analytics warehouse\"\n- **API Architecture**: \"Create an API gateway architecture showing routing, authentication, and rate limiting\"\n- **CI/CD Pipelines**: \"Diagram our deployment pipeline from git push to production\"\n\n**Example prompt:**\n> \"Create a system architecture diagram for a SaaS application:\n> \n> Frontend: React app on CloudFront/S3\n> API: FastAPI on ECS Fargate behind ALB\n> Auth: Firebase Authentication\n> Database: PostgreSQL on RDS (primary + read replica)\n> Cache: Redis on ElastiCache\n> Queue: SQS for async jobs\n> Workers: Celery on ECS\n> Storage: S3 for user uploads\n> Monitoring: CloudWatch + Datadog\n> \n> Show the data flow between components with arrows.\n> Group by VPC / public / external.\n> Interactive — I want to be able to zoom into each component.\"\n\n### Mind Maps & Concept Maps\n\nBrainstorm and organize ideas:\n\n- **Brainstorming**: \"Create a mind map exploring all possible revenue streams for our SaaS product\"\n- **Topic Exploration**: \"Build a concept map of machine learning — main branches, sub-topics, and relationships\"\n- **Content Planning**: \"Create a mind map for our Q2 content strategy — blog, social, video, email\"\n- **Strategy Mapping**: \"Map our go-to-market strategy showing channels, messaging, and target segments\"\n\n**Example prompt:**\n> \"Create an interactive mind map for 'AI in Healthcare':\n> \n> Central node: AI in Healthcare\n> \n> Main branches:\n> - Diagnostics (imaging, pathology, genomics)\n> - Drug Discovery (target identification, clinical trials, molecule design)\n> - Patient Care (chatbots, monitoring, personalized medicine)\n> - Operations (scheduling, billing, supply chain)\n> - Research (literature mining, clinical data analysis)\n> \n> Each branch should have 3-5 sub-topics with brief descriptions.\n> Color-code by maturity: green = in production, yellow = clinical trials, red = research stage.\"\n\n### Org Charts\n\nVisualize organizational structure:\n\n- **Company Hierarchy**: \"Create an org chart for a 50-person startup showing all departments and reporting lines\"\n- **Team Structure**: \"Diagram our engineering team structure — squads, tech leads, and cross-functional relationships\"\n- **Matrix Organization**: \"Create an org chart showing both functional reporting and project reporting lines\"\n\n### UML Diagrams\n\nSoftware engineering diagrams:\n\n- **Sequence Diagrams**: \"Create a sequence diagram showing the OAuth 2.0 authorization code flow\"\n- **Class Diagrams**: \"Diagram the class hierarchy for our e-commerce domain model — Product, Order, Customer, Payment\"\n- **State Diagrams**: \"Create a state diagram for an order lifecycle — placed, paid, shipped, delivered, returned\"\n- **Activity Diagrams**: \"Diagram the activity flow for our data processing pipeline\"\n\n**Example prompt:**\n> \"Create a sequence diagram for a payment processing flow:\n> \n> Actors: User, Frontend, API Server, Payment Service, Stripe, Database\n> \n> Flow:\n> 1. User clicks 'Pay' → Frontend sends payment request to API\n> 2. API creates payment intent with Stripe\n> 3. Stripe returns client secret\n> 4. API sends client secret to Frontend\n> 5. Frontend confirms payment with Stripe.js\n> 6. Stripe sends webhook to API\n> 7. API updates order status in Database\n> 8. API sends confirmation email to User\n> \n> Include error paths: payment declined, webhook timeout.\"\n\n### ER Diagrams\n\nDatabase design and data modeling:\n\n- **Database Schema**: \"Create an ER diagram for a social media platform — users, posts, comments, likes, follows\"\n- **Data Models**: \"Diagram the data model for our inventory management system\"\n- **Entity Relationships**: \"Create an ER diagram showing the relationships between customers, orders, products, and suppliers\"\n\n### Network Diagrams\n\nIT infrastructure visualization:\n\n- **Network Topology**: \"Create a network diagram showing our office network — firewalls, switches, VLANs, wireless APs\"\n- **Security Zones**: \"Diagram our network security zones — DMZ, internal, management, guest\"\n- **Cloud Networking**: \"Create a network diagram for our multi-VPC AWS setup with peering and transit gateway\"\n\n### Gantt Charts & Timelines\n\nProject planning and scheduling:\n\n- **Project Timelines**: \"Create a Gantt chart for our 6-month product launch — design, development, testing, marketing, launch\"\n- **Sprint Planning**: \"Diagram our next 3 sprints with epics, stories, and dependencies\"\n- **Roadmaps**: \"Create a product roadmap timeline for 2026 showing quarterly milestones\"\n\n### Swimlane Diagrams\n\nCross-functional process visualization:\n\n- **Cross-Team Workflows**: \"Create a swimlane diagram showing how a customer support ticket flows between Support, Engineering, and Product teams\"\n- **RACI Charts**: \"Diagram our incident response process with swimlanes for each role\"\n\n### User Journey Maps\n\nCustomer experience visualization:\n\n- **End-to-End Journeys**: \"Create a user journey map for a customer discovering, evaluating, purchasing, and onboarding to our product\"\n- **Touchpoint Mapping**: \"Map all customer touchpoints across email, web, app, and support\"\n\n---\n\n## Output Formats\n\n| Format | Features | Best For |\n|--------|----------|----------|\n| **Interactive HTML** | Zoom, pan, click, hover, responsive, shareable via URL | Presentations, team sharing, exploration |\n| **PDF** | Print-ready, static, professional | Documentation, email attachments, printing |\n\nCellCog defaults to interactive HTML — the whole point is diagrams you can explore, not static images. Request PDF explicitly when you need print-ready output.\n\n---\n\n## Chat Mode for Diagrams\n\n| Scenario | Recommended Mode |\n|----------|------------------|\n| Individual diagrams — flowcharts, org charts, ER diagrams, mind maps | `\"agent\"` |\n| Complex multi-diagram documentation, full system design docs with multiple views | `\"agent team\"` |\n\n**Use `\"agent\"` for most diagrams.** Individual flowcharts, architecture diagrams, and org charts execute well in agent mode.\n\n**Use `\"agent team\"` for comprehensive documentation** — when you need multiple interconnected diagrams that form a complete system design document.\n\n---\n\n## Example Prompts\n\n**Quick flowchart:**\n> \"Create a flowchart for returning a product on our e-commerce site. Include: initiate return → reason selection → approval check → shipping label → refund processing → confirmation. Show the happy path and the rejection path.\"\n\n**Architecture diagram:**\n> \"Diagram our production infrastructure:\n> \n> Load Balancer → 3 API servers → PostgreSQL (primary + replica)\n> API servers also talk to Redis cache and S3 for file storage\n> Background workers pull from SQS queue\n> Everything monitored by Datadog\n> \n> Show it as a clean architecture diagram with arrows showing data flow direction.\"\n\n**Mind map:**\n> \"Create a mind map for planning a product launch:\n> \n> Center: Product Launch\n> Branches: Marketing, Engineering, Sales, Support, Legal\n> Each branch should have 4-6 specific tasks\n> Color-code by priority: red = critical path, yellow = important, green = nice to have\"\n\n**Database ER diagram:**\n> \"Create an ER diagram for a project management tool:\n> \n> Entities: User, Organization, Project, Task, Comment, Attachment, Label\n> \n> Key relationships:\n> - Users belong to Organizations (many-to-many)\n> - Projects belong to Organizations\n> - Tasks belong to Projects, assigned to Users\n> - Comments belong to Tasks, created by Users\n> - Tasks can have multiple Labels (many-to-many)\n> \n> Show primary keys, foreign keys, and cardinality.\"\n\n---\n\n## Tips for Better Diagrams\n\n1. **Describe the components and relationships**: \"A connects to B which talks to C\" is all CellCog needs. Don't worry about layout.\n\n2. **Specify the diagram type**: \"Flowchart\", \"sequence diagram\", \"ER diagram\" — naming the type helps CellCog choose the right rendering approach.\n\n3. **Include data flow direction**: For architecture diagrams, mention which way data flows. \"Frontend → API → Database\" is clearer than just listing components.\n\n4. **Request interactivity**: \"I want to zoom in\" or \"clickable components\" tells CellCog to build an interactive experience.\n\n5. **Color-coding helps**: \"Color-code by team\" or \"green for success paths, red for error paths\" makes diagrams immediately useful.\n\n6. **Think about audience**: \"For the engineering team\" vs. \"for the board presentation\" changes the level of technical detail.\n\n---\n\n## If CellCog is not installed\n\nRun `/cellcog-setup` (or `/cellcog:cellcog-setup` depending on your tool) to install and authenticate.\n**OpenClaw users:** Run `clawhub install cellcog` instead.\n**Manual setup:** `pip install -U cellcog` and set `CELLCOG_API_KEY`. See the **cellcog** skill for SDK reference.\n\nFile v1.0.5:_meta.json\n\n{\n  \"ownerId\": \"kn7a96cj9q65e0bhmzahv790en80ffqm\",\n  \"slug\": \"diagram-flowchart-cellcog\",\n  \"version\": \"1.0.5\",\n  \"publishedAt\": 1776187930612\n}\n\nFile v1.0.5:skill-card.md\n\n## Description: <br>\nDiagram Cog uses CellCog to generate flowcharts, architecture diagrams, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, and network diagrams from plain-English prompts. <br>\n\nThis skill is ready for commercial/non-commercial use. <br>\n\n## Publisher: <br>\n[nitishgargiitd](https://clawhub.ai/user/nitishgargiitd) <br>\n\n### License/Terms of Use: <br>\nMIT-0 <br>\n\n\n## Use Case: <br>\nDevelopers, engineers, product teams, and business users use this skill to turn plain-English descriptions of systems, processes, data models, organizations, timelines, and user journeys into interactive diagrams or print-ready PDFs through CellCog. <br>\n\n### Deployment Geography for Use: <br>\nGlobal <br>\n\n## Known Risks and Mitigations: <br>\nRisk: Diagram prompts and generated diagram content are sent to CellCog and may include sensitive architecture, customer, or business information. <br>\nMitigation: Do not include secrets, credentials, regulated data, confidential internal architecture, or customer data unless the organization has approved CellCog for that use. <br>\nRisk: Generated diagrams may be shared through interactive URLs or PDFs with privacy implications. <br>\nMitigation: Review sharing settings and treat generated URLs and exported files according to the organization's data-handling requirements. <br>\n\n\n## Reference(s): <br>\n- [Diagram Cog on ClawHub](https://clawhub.ai/nitishgargiitd/diagram-cog) <br>\n- [CellCog Homepage](https://cellcog.ai) <br>\n\n\n## Skill Output: <br>\n**Output Type(s):** [guidance, code, shell commands, configuration, markdown] <br>\n**Output Format:** [Markdown guidance with Python SDK examples and setup commands; generated diagram work is returned through CellCog as interactive HTML URLs or PDFs.] <br>\n**Output Parameters:** [1D] <br>\n**Other Properties Related to Output:** [Requires python3, the cellcog dependency, and CELLCOG_API_KEY; supports OpenClaw fire-and-forget usage and blocking usage for other agents.] <br>\n\n## Skill Version(s): <br>\n1.0.5 (source: server release evidence) <br>\n\n## Ethical Considerations: <br>\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment. <br>\n\nArchive v1.0.4: 2 files, 6211 bytes\n\nFiles: SKILL.md (13891b), _meta.json (144b)\n\nFile v1.0.4:SKILL.md\n\n---\nname: diagram-cog\ndescription: \"AI diagram generator — flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, network diagrams. Describe your system in plain English, get interactive zoomable diagrams or print-ready PDFs. No Visio, no Lucidchart. Powered by CellCog's frontier coding agent and app deployment infrastructure.\"\nmetadata:\n  openclaw:\n    emoji: \"🔀\"\n    os: [darwin, linux, windows]\n    requires:\n      bins: [python3]\n      env: [CELLCOG_API_KEY]\nauthor: CellCog\nhomepage: https://cellcog.ai\ndependencies: [cellcog]\n---\n# Diagram Cog - Describe It in Words, Get It as a Diagram\n\nDescribe your system, process, or idea in plain English — CellCog produces professional, interactive diagrams you can share with a URL.\n\nNo Visio. No Lucidchart. No dragging boxes around for hours. Just describe what you need, and CellCog renders it as an interactive web page you can zoom, pan, and click — or a print-ready PDF for documentation.\n\n## How to Use\n\nFor your first CellCog task in a session, read the **cellcog** skill for the full SDK reference — file handling, chat modes, timeouts, and more.\n\n**OpenClaw (fire-and-forget):**\n```python\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    notify_session_key=\"agent:main:main\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\n```\n\n**Cursor / Claude Code / Other agents (blocks until done):**\n```python\nfrom cellcog import CellCogClient\nclient = CellCogClient(agent_provider=\"openclaw|cursor|claude-code|codex|...\")\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\nprint(result[\"message\"])\n```\n\n\n---\n\n## Why Diagrams Are Hard\n\nCreating good diagrams manually is surprisingly painful:\n\n- **Layout is tedious**: Arranging boxes, arrows, and labels takes longer than the thinking itself\n- **Tools are complex**: Visio, Lucidchart, Draw.io all have learning curves\n- **Iteration is slow**: Changing one element cascades into repositioning everything\n- **Sharing is friction**: Export → attach → hope it renders on their device\n\nCellCog eliminates all of this. Describe your diagram in words, get a shareable interactive URL. Need to change something? Just ask.\n\n---\n\n## What Makes This Different\n\nOther AI diagram tools output a static image. CellCog does something fundamentally different.\n\nCellCog **reasons about your system, picks the right rendering approach, and deploys an interactive web application** you can share with a URL. Zoom into your microservices architecture. Click a node to see details. Pan across a sprawling org chart. Or export to a print-ready PDF for your board deck.\n\n| What You Ask For | What CellCog Actually Does |\n|-----------------|---------------------------|\n| \"Diagram my microservices\" | Reasons about the architecture → generates Mermaid/D3 code → deploys interactive web app → delivers shareable URL |\n| \"Flowchart for our hiring process\" | Analyzes the process → renders with proper decision logic → color-codes paths → interactive HTML with click states |\n| \"ER diagram for my database\" | Understands entity relationships → generates diagram with cardinality → exports as both interactive HTML and PDF |\n| \"Mind map for brainstorming\" | Explores the topic → creates hierarchical structure → deploys zoomable, expandable mind map |\n\nThe power comes from having a world-class coding agent, multiple rendering libraries (Mermaid.js, D3.js, custom SVG, Highcharts), and built-in app deployment — all orchestrated together. When standard tools fall short, the agent writes custom code.\n\n---\n\n## What Diagrams You Can Create\n\n### Flowcharts & Process Flows\n\nVisualize any process or decision tree:\n\n- **Business Processes**: \"Create a flowchart for our customer onboarding process — from signup to first value\"\n- **Decision Trees**: \"Build a decision tree for our support team to triage incoming tickets\"\n- **User Flows**: \"Create a user flow diagram for the checkout process in our e-commerce app\"\n- **Approval Workflows**: \"Diagram our expense approval workflow — who approves what at each dollar threshold\"\n- **Troubleshooting Guides**: \"Create a troubleshooting flowchart for common API integration errors\"\n\n**Example prompt:**\n> \"Create an interactive flowchart for our hiring process:\n> \n> Steps:\n> 1. Job posted → Applications received\n> 2. Resume screening (HR) → Pass/Fail\n> 3. Phone screen (Recruiter) → Pass/Fail\n> 4. Technical interview (Engineering) → Pass/Fail\n> 5. Culture interview (Team) → Pass/Fail\n> 6. Offer → Accept/Decline\n> 7. If decline → Back to step 2 with next candidate\n> \n> Color-code: Green for forward progress, red for rejection paths, yellow for decision points.\n> Include average time at each stage.\"\n\n### System Architecture\n\nTechnical diagrams for engineering teams:\n\n- **Microservices**: \"Diagram our microservices architecture showing all services, their communication patterns, and data stores\"\n- **Cloud Infrastructure**: \"Create an AWS architecture diagram for our production environment — VPC, ECS, RDS, ElastiCache, CloudFront\"\n- **Data Pipelines**: \"Diagram our data pipeline from raw ingestion through transformation to the analytics warehouse\"\n- **API Architecture**: \"Create an API gateway architecture showing routing, authentication, and rate limiting\"\n- **CI/CD Pipelines**: \"Diagram our deployment pipeline from git push to production\"\n\n**Example prompt:**\n> \"Create a system architecture diagram for a SaaS application:\n> \n> Frontend: React app on CloudFront/S3\n> API: FastAPI on ECS Fargate behind ALB\n> Auth: Firebase Authentication\n> Database: PostgreSQL on RDS (primary + read replica)\n> Cache: Redis on ElastiCache\n> Queue: SQS for async jobs\n> Workers: Celery on ECS\n> Storage: S3 for user uploads\n> Monitoring: CloudWatch + Datadog\n> \n> Show the data flow between components with arrows.\n> Group by VPC / public / external.\n> Interactive — I want to be able to zoom into each component.\"\n\n### Mind Maps & Concept Maps\n\nBrainstorm and organize ideas:\n\n- **Brainstorming**: \"Create a mind map exploring all possible revenue streams for our SaaS product\"\n- **Topic Exploration**: \"Build a concept map of machine learning — main branches, sub-topics, and relationships\"\n- **Content Planning**: \"Create a mind map for our Q2 content strategy — blog, social, video, email\"\n- **Strategy Mapping**: \"Map our go-to-market strategy showing channels, messaging, and target segments\"\n\n**Example prompt:**\n> \"Create an interactive mind map for 'AI in Healthcare':\n> \n> Central node: AI in Healthcare\n> \n> Main branches:\n> - Diagnostics (imaging, pathology, genomics)\n> - Drug Discovery (target identification, clinical trials, molecule design)\n> - Patient Care (chatbots, monitoring, personalized medicine)\n> - Operations (scheduling, billing, supply chain)\n> - Research (literature mining, clinical data analysis)\n> \n> Each branch should have 3-5 sub-topics with brief descriptions.\n> Color-code by maturity: green = in production, yellow = clinical trials, red = research stage.\"\n\n### Org Charts\n\nVisualize organizational structure:\n\n- **Company Hierarchy**: \"Create an org chart for a 50-person startup showing all departments and reporting lines\"\n- **Team Structure**: \"Diagram our engineering team structure — squads, tech leads, and cross-functional relationships\"\n- **Matrix Organization**: \"Create an org chart showing both functional reporting and project reporting lines\"\n\n### UML Diagrams\n\nSoftware engineering diagrams:\n\n- **Sequence Diagrams**: \"Create a sequence diagram showing the OAuth 2.0 authorization code flow\"\n- **Class Diagrams**: \"Diagram the class hierarchy for our e-commerce domain model — Product, Order, Customer, Payment\"\n- **State Diagrams**: \"Create a state diagram for an order lifecycle — placed, paid, shipped, delivered, returned\"\n- **Activity Diagrams**: \"Diagram the activity flow for our data processing pipeline\"\n\n**Example prompt:**\n> \"Create a sequence diagram for a payment processing flow:\n> \n> Actors: User, Frontend, API Server, Payment Service, Stripe, Database\n> \n> Flow:\n> 1. User clicks 'Pay' → Frontend sends payment request to API\n> 2. API creates payment intent with Stripe\n> 3. Stripe returns client secret\n> 4. API sends client secret to Frontend\n> 5. Frontend confirms payment with Stripe.js\n> 6. Stripe sends webhook to API\n> 7. API updates order status in Database\n> 8. API sends confirmation email to User\n> \n> Include error paths: payment declined, webhook timeout.\"\n\n### ER Diagrams\n\nDatabase design and data modeling:\n\n- **Database Schema**: \"Create an ER diagram for a social media platform — users, posts, comments, likes, follows\"\n- **Data Models**: \"Diagram the data model for our inventory management system\"\n- **Entity Relationships**: \"Create an ER diagram showing the relationships between customers, orders, products, and suppliers\"\n\n### Network Diagrams\n\nIT infrastructure visualization:\n\n- **Network Topology**: \"Create a network diagram showing our office network — firewalls, switches, VLANs, wireless APs\"\n- **Security Zones**: \"Diagram our network security zones — DMZ, internal, management, guest\"\n- **Cloud Networking**: \"Create a network diagram for our multi-VPC AWS setup with peering and transit gateway\"\n\n### Gantt Charts & Timelines\n\nProject planning and scheduling:\n\n- **Project Timelines**: \"Create a Gantt chart for our 6-month product launch — design, development, testing, marketing, launch\"\n- **Sprint Planning**: \"Diagram our next 3 sprints with epics, stories, and dependencies\"\n- **Roadmaps**: \"Create a product roadmap timeline for 2026 showing quarterly milestones\"\n\n### Swimlane Diagrams\n\nCross-functional process visualization:\n\n- **Cross-Team Workflows**: \"Create a swimlane diagram showing how a customer support ticket flows between Support, Engineering, and Product teams\"\n- **RACI Charts**: \"Diagram our incident response process with swimlanes for each role\"\n\n### User Journey Maps\n\nCustomer experience visualization:\n\n- **End-to-End Journeys**: \"Create a user journey map for a customer discovering, evaluating, purchasing, and onboarding to our product\"\n- **Touchpoint Mapping**: \"Map all customer touchpoints across email, web, app, and support\"\n\n---\n\n## Output Formats\n\n| Format | Features | Best For |\n|--------|----------|----------|\n| **Interactive HTML** | Zoom, pan, click, hover, responsive, shareable via URL | Presentations, team sharing, exploration |\n| **PDF** | Print-ready, static, professional | Documentation, email attachments, printing |\n\nCellCog defaults to interactive HTML — the whole point is diagrams you can explore, not static images. Request PDF explicitly when you need print-ready output.\n\n---\n\n## Chat Mode for Diagrams\n\n| Scenario | Recommended Mode |\n|----------|------------------|\n| Individual diagrams — flowcharts, org charts, ER diagrams, mind maps | `\"agent\"` |\n| Complex multi-diagram documentation, full system design docs with multiple views | `\"agent team\"` |\n\n**Use `\"agent\"` for most diagrams.** Individual flowcharts, architecture diagrams, and org charts execute well in agent mode.\n\n**Use `\"agent team\"` for comprehensive documentation** — when you need multiple interconnected diagrams that form a complete system design document.\n\n---\n\n## Example Prompts\n\n**Quick flowchart:**\n> \"Create a flowchart for returning a product on our e-commerce site. Include: initiate return → reason selection → approval check → shipping label → refund processing → confirmation. Show the happy path and the rejection path.\"\n\n**Architecture diagram:**\n> \"Diagram our production infrastructure:\n> \n> Load Balancer → 3 API servers → PostgreSQL (primary + replica)\n> API servers also talk to Redis cache and S3 for file storage\n> Background workers pull from SQS queue\n> Everything monitored by Datadog\n> \n> Show it as a clean architecture diagram with arrows showing data flow direction.\"\n\n**Mind map:**\n> \"Create a mind map for planning a product launch:\n> \n> Center: Product Launch\n> Branches: Marketing, Engineering, Sales, Support, Legal\n> Each branch should have 4-6 specific tasks\n> Color-code by priority: red = critical path, yellow = important, green = nice to have\"\n\n**Database ER diagram:**\n> \"Create an ER diagram for a project management tool:\n> \n> Entities: User, Organization, Project, Task, Comment, Attachment, Label\n> \n> Key relationships:\n> - Users belong to Organizations (many-to-many)\n> - Projects belong to Organizations\n> - Tasks belong to Projects, assigned to Users\n> - Comments belong to Tasks, created by Users\n> - Tasks can have multiple Labels (many-to-many)\n> \n> Show primary keys, foreign keys, and cardinality.\"\n\n---\n\n## Tips for Better Diagrams\n\n1. **Describe the components and relationships**: \"A connects to B which talks to C\" is all CellCog needs. Don't worry about layout.\n\n2. **Specify the diagram type**: \"Flowchart\", \"sequence diagram\", \"ER diagram\" — naming the type helps CellCog choose the right rendering approach.\n\n3. **Include data flow direction**: For architecture diagrams, mention which way data flows. \"Frontend → API → Database\" is clearer than just listing components.\n\n4. **Request interactivity**: \"I want to zoom in\" or \"clickable components\" tells CellCog to build an interactive experience.\n\n5. **Color-coding helps**: \"Color-code by team\" or \"green for success paths, red for error paths\" makes diagrams immediately useful.\n\n6. **Think about audience**: \"For the engineering team\" vs. \"for the board presentation\" changes the level of technical detail.\n\n---\n\n## If CellCog is not installed\n\n**Cursor:** Run `/cellcog-setup` to install and authenticate.\n**OpenClaw:** Run `clawhub install cellcog` for SDK setup.\n**Other agents:** `pip install -U cellcog` and set `CELLCOG_API_KEY`. See the **cellcog** skill for SDK reference.\n\nFile v1.0.4:_meta.json\n\n{\n  \"ownerId\": \"kn7a96cj9q65e0bhmzahv790en80ffqm\",\n  \"slug\": \"diagram-flowchart-cellcog\",\n  \"version\": \"1.0.4\",\n  \"publishedAt\": 1776042042833\n}\n\nArchive v1.0.3: 2 files, 6124 bytes\n\nFiles: SKILL.md (13648b), _meta.json (144b)\n\nFile v1.0.3:SKILL.md\n\n---\nname: diagram-cog\ndescription: \"Powered by CellCog. Diagram generation from plain text. Flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, and network diagrams. Interactive HTML or PDF output.\"\nmetadata:\n  openclaw:\n    emoji: \"🔀\"\n    os: [darwin, linux, windows]\n    requires:\n      bins: [python3]\n      env: [CELLCOG_API_KEY]\nauthor: CellCog\nhomepage: https://cellcog.ai\ndependencies: [cellcog]\n---\n# Diagram Cog - Describe It in Words, Get It as a Diagram\n\nDescribe your system, process, or idea in plain English — CellCog produces professional, interactive diagrams you can share with a URL.\n\nNo Visio. No Lucidchart. No dragging boxes around for hours. Just describe what you need, and CellCog renders it as an interactive web page you can zoom, pan, and click — or a print-ready PDF for documentation.\n\n## How to Use\n\nFor your first CellCog task in a session, read the **cellcog** skill for the full SDK reference — file handling, chat modes, timeouts, and more.\n\n**OpenClaw (fire-and-forget):**\n```python\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    notify_session_key=\"agent:main:main\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\n```\n\n**Cursor / Claude Code / Other agents (blocks until done):**\n```python\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\nprint(result[\"message\"])\n```\n\n\n---\n\n## Why Diagrams Are Hard\n\nCreating good diagrams manually is surprisingly painful:\n\n- **Layout is tedious**: Arranging boxes, arrows, and labels takes longer than the thinking itself\n- **Tools are complex**: Visio, Lucidchart, Draw.io all have learning curves\n- **Iteration is slow**: Changing one element cascades into repositioning everything\n- **Sharing is friction**: Export → attach → hope it renders on their device\n\nCellCog eliminates all of this. Describe your diagram in words, get a shareable interactive URL. Need to change something? Just ask.\n\n---\n\n## What Makes This Different\n\nOther AI diagram tools output a static image. CellCog does something fundamentally different.\n\nCellCog **reasons about your system, picks the right rendering approach, and deploys an interactive web application** you can share with a URL. Zoom into your microservices architecture. Click a node to see details. Pan across a sprawling org chart. Or export to a print-ready PDF for your board deck.\n\n| What You Ask For | What CellCog Actually Does |\n|-----------------|---------------------------|\n| \"Diagram my microservices\" | Reasons about the architecture → generates Mermaid/D3 code → deploys interactive web app → delivers shareable URL |\n| \"Flowchart for our hiring process\" | Analyzes the process → renders with proper decision logic → color-codes paths → interactive HTML with click states |\n| \"ER diagram for my database\" | Understands entity relationships → generates diagram with cardinality → exports as both interactive HTML and PDF |\n| \"Mind map for brainstorming\" | Explores the topic → creates hierarchical structure → deploys zoomable, expandable mind map |\n\nThe power comes from having a world-class coding agent, multiple rendering libraries (Mermaid.js, D3.js, custom SVG, Highcharts), and built-in app deployment — all orchestrated together. When standard tools fall short, the agent writes custom code.\n\n---\n\n## What Diagrams You Can Create\n\n### Flowcharts & Process Flows\n\nVisualize any process or decision tree:\n\n- **Business Processes**: \"Create a flowchart for our customer onboarding process — from signup to first value\"\n- **Decision Trees**: \"Build a decision tree for our support team to triage incoming tickets\"\n- **User Flows**: \"Create a user flow diagram for the checkout process in our e-commerce app\"\n- **Approval Workflows**: \"Diagram our expense approval workflow — who approves what at each dollar threshold\"\n- **Troubleshooting Guides**: \"Create a troubleshooting flowchart for common API integration errors\"\n\n**Example prompt:**\n> \"Create an interactive flowchart for our hiring process:\n> \n> Steps:\n> 1. Job posted → Applications received\n> 2. Resume screening (HR) → Pass/Fail\n> 3. Phone screen (Recruiter) → Pass/Fail\n> 4. Technical interview (Engineering) → Pass/Fail\n> 5. Culture interview (Team) → Pass/Fail\n> 6. Offer → Accept/Decline\n> 7. If decline → Back to step 2 with next candidate\n> \n> Color-code: Green for forward progress, red for rejection paths, yellow for decision points.\n> Include average time at each stage.\"\n\n### System Architecture\n\nTechnical diagrams for engineering teams:\n\n- **Microservices**: \"Diagram our microservices architecture showing all services, their communication patterns, and data stores\"\n- **Cloud Infrastructure**: \"Create an AWS architecture diagram for our production environment — VPC, ECS, RDS, ElastiCache, CloudFront\"\n- **Data Pipelines**: \"Diagram our data pipeline from raw ingestion through transformation to the analytics warehouse\"\n- **API Architecture**: \"Create an API gateway architecture showing routing, authentication, and rate limiting\"\n- **CI/CD Pipelines**: \"Diagram our deployment pipeline from git push to production\"\n\n**Example prompt:**\n> \"Create a system architecture diagram for a SaaS application:\n> \n> Frontend: React app on CloudFront/S3\n> API: FastAPI on ECS Fargate behind ALB\n> Auth: Firebase Authentication\n> Database: PostgreSQL on RDS (primary + read replica)\n> Cache: Redis on ElastiCache\n> Queue: SQS for async jobs\n> Workers: Celery on ECS\n> Storage: S3 for user uploads\n> Monitoring: CloudWatch + Datadog\n> \n> Show the data flow between components with arrows.\n> Group by VPC / public / external.\n> Interactive — I want to be able to zoom into each component.\"\n\n### Mind Maps & Concept Maps\n\nBrainstorm and organize ideas:\n\n- **Brainstorming**: \"Create a mind map exploring all possible revenue streams for our SaaS product\"\n- **Topic Exploration**: \"Build a concept map of machine learning — main branches, sub-topics, and relationships\"\n- **Content Planning**: \"Create a mind map for our Q2 content strategy — blog, social, video, email\"\n- **Strategy Mapping**: \"Map our go-to-market strategy showing channels, messaging, and target segments\"\n\n**Example prompt:**\n> \"Create an interactive mind map for 'AI in Healthcare':\n> \n> Central node: AI in Healthcare\n> \n> Main branches:\n> - Diagnostics (imaging, pathology, genomics)\n> - Drug Discovery (target identification, clinical trials, molecule design)\n> - Patient Care (chatbots, monitoring, personalized medicine)\n> - Operations (scheduling, billing, supply chain)\n> - Research (literature mining, clinical data analysis)\n> \n> Each branch should have 3-5 sub-topics with brief descriptions.\n> Color-code by maturity: green = in production, yellow = clinical trials, red = research stage.\"\n\n### Org Charts\n\nVisualize organizational structure:\n\n- **Company Hierarchy**: \"Create an org chart for a 50-person startup showing all departments and reporting lines\"\n- **Team Structure**: \"Diagram our engineering team structure — squads, tech leads, and cross-functional relationships\"\n- **Matrix Organization**: \"Create an org chart showing both functional reporting and project reporting lines\"\n\n### UML Diagrams\n\nSoftware engineering diagrams:\n\n- **Sequence Diagrams**: \"Create a sequence diagram showing the OAuth 2.0 authorization code flow\"\n- **Class Diagrams**: \"Diagram the class hierarchy for our e-commerce domain model — Product, Order, Customer, Payment\"\n- **State Diagrams**: \"Create a state diagram for an order lifecycle — placed, paid, shipped, delivered, returned\"\n- **Activity Diagrams**: \"Diagram the activity flow for our data processing pipeline\"\n\n**Example prompt:**\n> \"Create a sequence diagram for a payment processing flow:\n> \n> Actors: User, Frontend, API Server, Payment Service, Stripe, Database\n> \n> Flow:\n> 1. User clicks 'Pay' → Frontend sends payment request to API\n> 2. API creates payment intent with Stripe\n> 3. Stripe returns client secret\n> 4. API sends client secret to Frontend\n> 5. Frontend confirms payment with Stripe.js\n> 6. Stripe sends webhook to API\n> 7. API updates order status in Database\n> 8. API sends confirmation email to User\n> \n> Include error paths: payment declined, webhook timeout.\"\n\n### ER Diagrams\n\nDatabase design and data modeling:\n\n- **Database Schema**: \"Create an ER diagram for a social media platform — users, posts, comments, likes, follows\"\n- **Data Models**: \"Diagram the data model for our inventory management system\"\n- **Entity Relationships**: \"Create an ER diagram showing the relationships between customers, orders, products, and suppliers\"\n\n### Network Diagrams\n\nIT infrastructure visualization:\n\n- **Network Topology**: \"Create a network diagram showing our office network — firewalls, switches, VLANs, wireless APs\"\n- **Security Zones**: \"Diagram our network security zones — DMZ, internal, management, guest\"\n- **Cloud Networking**: \"Create a network diagram for our multi-VPC AWS setup with peering and transit gateway\"\n\n### Gantt Charts & Timelines\n\nProject planning and scheduling:\n\n- **Project Timelines**: \"Create a Gantt chart for our 6-month product launch — design, development, testing, marketing, launch\"\n- **Sprint Planning**: \"Diagram our next 3 sprints with epics, stories, and dependencies\"\n- **Roadmaps**: \"Create a product roadmap timeline for 2026 showing quarterly milestones\"\n\n### Swimlane Diagrams\n\nCross-functional process visualization:\n\n- **Cross-Team Workflows**: \"Create a swimlane diagram showing how a customer support ticket flows between Support, Engineering, and Product teams\"\n- **RACI Charts**: \"Diagram our incident response process with swimlanes for each role\"\n\n### User Journey Maps\n\nCustomer experience visualization:\n\n- **End-to-End Journeys**: \"Create a user journey map for a customer discovering, evaluating, purchasing, and onboarding to our product\"\n- **Touchpoint Mapping**: \"Map all customer touchpoints across email, web, app, and support\"\n\n---\n\n## Output Formats\n\n| Format | Features | Best For |\n|--------|----------|----------|\n| **Interactive HTML** | Zoom, pan, click, hover, responsive, shareable via URL | Presentations, team sharing, exploration |\n| **PDF** | Print-ready, static, professional | Documentation, email attachments, printing |\n\nCellCog defaults to interactive HTML — the whole point is diagrams you can explore, not static images. Request PDF explicitly when you need print-ready output.\n\n---\n\n## Chat Mode for Diagrams\n\n| Scenario | Recommended Mode |\n|----------|------------------|\n| Individual diagrams — flowcharts, org charts, ER diagrams, mind maps | `\"agent\"` |\n| Complex multi-diagram documentation, full system design docs with multiple views | `\"agent team\"` |\n\n**Use `\"agent\"` for most diagrams.** Individual flowcharts, architecture diagrams, and org charts execute well in agent mode.\n\n**Use `\"agent team\"` for comprehensive documentation** — when you need multiple interconnected diagrams that form a complete system design document.\n\n---\n\n## Example Prompts\n\n**Quick flowchart:**\n> \"Create a flowchart for returning a product on our e-commerce site. Include: initiate return → reason selection → approval check → shipping label → refund processing → confirmation. Show the happy path and the rejection path.\"\n\n**Architecture diagram:**\n> \"Diagram our production infrastructure:\n> \n> Load Balancer → 3 API servers → PostgreSQL (primary + replica)\n> API servers also talk to Redis cache and S3 for file storage\n> Background workers pull from SQS queue\n> Everything monitored by Datadog\n> \n> Show it as a clean architecture diagram with arrows showing data flow direction.\"\n\n**Mind map:**\n> \"Create a mind map for planning a product launch:\n> \n> Center: Product Launch\n> Branches: Marketing, Engineering, Sales, Support, Legal\n> Each branch should have 4-6 specific tasks\n> Color-code by priority: red = critical path, yellow = important, green = nice to have\"\n\n**Database ER diagram:**\n> \"Create an ER diagram for a project management tool:\n> \n> Entities: User, Organization, Project, Task, Comment, Attachment, Label\n> \n> Key relationships:\n> - Users belong to Organizations (many-to-many)\n> - Projects belong to Organizations\n> - Tasks belong to Projects, assigned to Users\n> - Comments belong to Tasks, created by Users\n> - Tasks can have multiple Labels (many-to-many)\n> \n> Show primary keys, foreign keys, and cardinality.\"\n\n---\n\n## Tips for Better Diagrams\n\n1. **Describe the components and relationships**: \"A connects to B which talks to C\" is all CellCog needs. Don't worry about layout.\n\n2. **Specify the diagram type**: \"Flowchart\", \"sequence diagram\", \"ER diagram\" — naming the type helps CellCog choose the right rendering approach.\n\n3. **Include data flow direction**: For architecture diagrams, mention which way data flows. \"Frontend → API → Database\" is clearer than just listing components.\n\n4. **Request interactivity**: \"I want to zoom in\" or \"clickable components\" tells CellCog to build an interactive experience.\n\n5. **Color-coding helps**: \"Color-code by team\" or \"green for success paths, red for error paths\" makes diagrams immediately useful.\n\n6. **Think about audience**: \"For the engineering team\" vs. \"for the board presentation\" changes the level of technical detail.\n\n---\n\n## If CellCog is not installed\n\n**Cursor:** Run `/cellcog-setup` to install and authenticate.\n**OpenClaw:** Run `clawhub install cellcog` for SDK setup.\n**Other agents:** `pip install -U cellcog` and set `CELLCOG_API_KEY`. See the **cellcog** skill for SDK reference.\n\nFile v1.0.3:_meta.json\n\n{\n  \"ownerId\": \"kn7a96cj9q65e0bhmzahv790en80ffqm\",\n  \"slug\": \"diagram-flowchart-cellcog\",\n  \"version\": \"1.0.3\",\n  \"publishedAt\": 1776036920789\n}\n\nArchive v1.0.2: 2 files, 6161 bytes\n\nFiles: SKILL.md (13863b), _meta.json (144b)\n\nFile v1.0.2:SKILL.md\n\n---\nname: diagram-cog\ndescription: \"AI diagram generator — flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, network diagrams. Describe your system in plain English, get interactive zoomable diagrams or print-ready PDFs. No Visio, no Lucidchart. Powered by CellCog's frontier coding agent and app deployment infrastructure.\"\nmetadata:\n  openclaw:\n    emoji: \"🔀\"\n    os: [darwin, linux, windows]\n    requires:\n      bins: [python3]\n      env: [CELLCOG_API_KEY]\nauthor: CellCog\nhomepage: https://cellcog.ai\ndependencies: [cellcog]\n---\n\n# Diagram Cog - Describe It in Words, Get It as a Diagram\n\n**Other tools make you drag boxes. CellCog reads your mind.** Describe your system, process, or idea in plain English — CellCog produces professional, interactive diagrams you can share with a URL.\n\nNo Visio. No Lucidchart. No dragging boxes around for hours. Just describe what you need, and CellCog renders it as an interactive web page you can zoom, pan, and click — or a print-ready PDF for documentation.\n\n---\n\n## Prerequisites\n\nThis skill requires the `cellcog` skill for SDK setup and API calls.\n\n```bash\nclawhub install cellcog\n```\n\n**Read the cellcog skill first** for SDK setup. This skill shows you what's possible.\n\n**OpenClaw agents (fire-and-forget — recommended for long tasks):**\n```python\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    notify_session_key=\"agent:main:main\",  # OpenClaw only\n    task_label=\"my-task\",\n    chat_mode=\"agent\",  # See cellcog skill for all modes\n)\n```\n\n**All other agents (blocks until done):**\n```python\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\n```\n\nSee the **cellcog** mothership skill for complete SDK API reference — delivery modes, timeouts, file handling, and more.\n\n---\n\n## Why Diagrams Are Hard\n\nCreating good diagrams manually is surprisingly painful:\n\n- **Layout is tedious**: Arranging boxes, arrows, and labels takes longer than the thinking itself\n- **Tools are complex**: Visio, Lucidchart, Draw.io all have learning curves\n- **Iteration is slow**: Changing one element cascades into repositioning everything\n- **Sharing is friction**: Export → attach → hope it renders on their device\n\nCellCog eliminates all of this. Describe your diagram in words, get a shareable interactive URL. Need to change something? Just ask.\n\n---\n\n## What Makes This Different\n\nOther AI diagram tools output a static image. CellCog does something fundamentally different.\n\nCellCog's frontier coding agent — the same one that builds CellCog itself — **reasons about your system, picks the right rendering approach, and deploys an interactive web application** you can share with a URL. Zoom into your microservices architecture. Click a node to see details. Pan across a sprawling org chart. Or export to a print-ready PDF for your board deck.\n\n| What You Ask For | What CellCog Actually Does |\n|-----------------|---------------------------|\n| \"Diagram my microservices\" | Reasons about the architecture → generates Mermaid/D3 code → deploys interactive web app → delivers shareable URL |\n| \"Flowchart for our hiring process\" | Analyzes the process → renders with proper decision logic → color-codes paths → interactive HTML with click states |\n| \"ER diagram for my database\" | Understands entity relationships → generates diagram with cardinality → exports as both interactive HTML and PDF |\n| \"Mind map for brainstorming\" | Explores the topic → creates hierarchical structure → deploys zoomable, expandable mind map |\n\nThe power comes from having a world-class coding agent, multiple rendering libraries (Mermaid.js, D3.js, custom SVG, Highcharts), and built-in app deployment — all orchestrated together. When standard tools fall short, the agent writes custom code.\n\n---\n\n## What Diagrams You Can Create\n\n### Flowcharts & Process Flows\n\nVisualize any process or decision tree:\n\n- **Business Processes**: \"Create a flowchart for our customer onboarding process — from signup to first value\"\n- **Decision Trees**: \"Build a decision tree for our support team to triage incoming tickets\"\n- **User Flows**: \"Create a user flow diagram for the checkout process in our e-commerce app\"\n- **Approval Workflows**: \"Diagram our expense approval workflow — who approves what at each dollar threshold\"\n- **Troubleshooting Guides**: \"Create a troubleshooting flowchart for common API integration errors\"\n\n**Example prompt:**\n> \"Create an interactive flowchart for our hiring process:\n> \n> Steps:\n> 1. Job posted → Applications received\n> 2. Resume screening (HR) → Pass/Fail\n> 3. Phone screen (Recruiter) → Pass/Fail\n> 4. Technical interview (Engineering) → Pass/Fail\n> 5. Culture interview (Team) → Pass/Fail\n> 6. Offer → Accept/Decline\n> 7. If decline → Back to step 2 with next candidate\n> \n> Color-code: Green for forward progress, red for rejection paths, yellow for decision points.\n> Include average time at each stage.\"\n\n### System Architecture\n\nTechnical diagrams for engineering teams:\n\n- **Microservices**: \"Diagram our microservices architecture showing all services, their communication patterns, and data stores\"\n- **Cloud Infrastructure**: \"Create an AWS architecture diagram for our production environment — VPC, ECS, RDS, ElastiCache, CloudFront\"\n- **Data Pipelines**: \"Diagram our data pipeline from raw ingestion through transformation to the analytics warehouse\"\n- **API Architecture**: \"Create an API gateway architecture showing routing, authentication, and rate limiting\"\n- **CI/CD Pipelines**: \"Diagram our deployment pipeline from git push to production\"\n\n**Example prompt:**\n> \"Create a system architecture diagram for a SaaS application:\n> \n> Frontend: React app on CloudFront/S3\n> API: FastAPI on ECS Fargate behind ALB\n> Auth: Firebase Authentication\n> Database: PostgreSQL on RDS (primary + read replica)\n> Cache: Redis on ElastiCache\n> Queue: SQS for async jobs\n> Workers: Celery on ECS\n> Storage: S3 for user uploads\n> Monitoring: CloudWatch + Datadog\n> \n> Show the data flow between components with arrows.\n> Group by VPC / public / external.\n> Interactive — I want to be able to zoom into each component.\"\n\n### Mind Maps & Concept Maps\n\nBrainstorm and organize ideas:\n\n- **Brainstorming**: \"Create a mind map exploring all possible revenue streams for our SaaS product\"\n- **Topic Exploration**: \"Build a concept map of machine learning — main branches, sub-topics, and relationships\"\n- **Content Planning**: \"Create a mind map for our Q2 content strategy — blog, social, video, email\"\n- **Strategy Mapping**: \"Map our go-to-market strategy showing channels, messaging, and target segments\"\n\n**Example prompt:**\n> \"Create an interactive mind map for 'AI in Healthcare':\n> \n> Central node: AI in Healthcare\n> \n> Main branches:\n> - Diagnostics (imaging, pathology, genomics)\n> - Drug Discovery (target identification, clinical trials, molecule design)\n> - Patient Care (chatbots, monitoring, personalized medicine)\n> - Operations (scheduling, billing, supply chain)\n> - Research (literature mining, clinical data analysis)\n> \n> Each branch should have 3-5 sub-topics with brief descriptions.\n> Color-code by maturity: green = in production, yellow = clinical trials, red = research stage.\"\n\n### Org Charts\n\nVisualize organizational structure:\n\n- **Company Hierarchy**: \"Create an org chart for a 50-person startup showing all departments and reporting lines\"\n- **Team Structure**: \"Diagram our engineering team structure — squads, tech leads, and cross-functional relationships\"\n- **Matrix Organization**: \"Create an org chart showing both functional reporting and project reporting lines\"\n\n### UML Diagrams\n\nSoftware engineering diagrams:\n\n- **Sequence Diagrams**: \"Create a sequence diagram showing the OAuth 2.0 authorization code flow\"\n- **Class Diagrams**: \"Diagram the class hierarchy for our e-commerce domain model — Product, Order, Customer, Payment\"\n- **State Diagrams**: \"Create a state diagram for an order lifecycle — placed, paid, shipped, delivered, returned\"\n- **Activity Diagrams**: \"Diagram the activity flow for our data processing pipeline\"\n\n**Example prompt:**\n> \"Create a sequence diagram for a payment processing flow:\n> \n> Actors: User, Frontend, API Server, Payment Service, Stripe, Database\n> \n> Flow:\n> 1. User clicks 'Pay' → Frontend sends payment request to API\n> 2. API creates payment intent with Stripe\n> 3. Stripe returns client secret\n> 4. API sends client secret to Frontend\n> 5. Frontend confirms payment with Stripe.js\n> 6. Stripe sends webhook to API\n> 7. API updates order status in Database\n> 8. API sends confirmation email to User\n> \n> Include error paths: payment declined, webhook timeout.\"\n\n### ER Diagrams\n\nDatabase design and data modeling:\n\n- **Database Schema**: \"Create an ER diagram for a social media platform — users, posts, comments, likes, follows\"\n- **Data Models**: \"Diagram the data model for our inventory management system\"\n- **Entity Relationships**: \"Create an ER diagram showing the relationships between customers, orders, products, and suppliers\"\n\n### Network Diagrams\n\nIT infrastructure visualization:\n\n- **Network Topology**: \"Create a network diagram showing our office network — firewalls, switches, VLANs, wireless APs\"\n- **Security Zones**: \"Diagram our network security zones — DMZ, internal, management, guest\"\n- **Cloud Networking**: \"Create a network diagram for our multi-VPC AWS setup with peering and transit gateway\"\n\n### Gantt Charts & Timelines\n\nProject planning and scheduling:\n\n- **Project Timelines**: \"Create a Gantt chart for our 6-month product launch — design, development, testing, marketing, launch\"\n- **Sprint Planning**: \"Diagram our next 3 sprints with epics, stories, and dependencies\"\n- **Roadmaps**: \"Create a product roadmap timeline for 2026 showing quarterly milestones\"\n\n### Swimlane Diagrams\n\nCross-functional process visualization:\n\n- **Cross-Team Workflows**: \"Create a swimlane diagram showing how a customer support ticket flows between Support, Engineering, and Product teams\"\n- **RACI Charts**: \"Diagram our incident response process with swimlanes for each role\"\n\n### User Journey Maps\n\nCustomer experience visualization:\n\n- **End-to-End Journeys**: \"Create a user journey map for a customer discovering, evaluating, purchasing, and onboarding to our product\"\n- **Touchpoint Mapping**: \"Map all customer touchpoints across email, web, app, and support\"\n\n---\n\n## Output Formats\n\n| Format | Features | Best For |\n|--------|----------|----------|\n| **Interactive HTML** | Zoom, pan, click, hover, responsive, shareable via URL | Presentations, team sharing, exploration |\n| **PDF** | Print-ready, static, professional | Documentation, email attachments, printing |\n\nCellCog defaults to interactive HTML — the whole point is diagrams you can explore, not static images. Request PDF explicitly when you need print-ready output.\n\n---\n\n## Chat Mode for Diagrams\n\n| Scenario | Recommended Mode |\n|----------|------------------|\n| Individual diagrams — flowcharts, org charts, ER diagrams, mind maps | `\"agent\"` |\n| Complex multi-diagram documentation, full system design docs with multiple views | `\"agent team\"` |\n\n**Use `\"agent\"` for most diagrams.** Individual flowcharts, architecture diagrams, and org charts execute well in agent mode.\n\n**Use `\"agent team\"` for comprehensive documentation** — when you need multiple interconnected diagrams that form a complete system design document.\n\n---\n\n## Example Prompts\n\n**Quick flowchart:**\n> \"Create a flowchart for returning a product on our e-commerce site. Include: initiate return → reason selection → approval check → shipping label → refund processing → confirmation. Show the happy path and the rejection path.\"\n\n**Architecture diagram:**\n> \"Diagram our production infrastructure:\n> \n> Load Balancer → 3 API servers → PostgreSQL (primary + replica)\n> API servers also talk to Redis cache and S3 for file storage\n> Background workers pull from SQS queue\n> Everything monitored by Datadog\n> \n> Show it as a clean architecture diagram with arrows showing data flow direction.\"\n\n**Mind map:**\n> \"Create a mind map for planning a product launch:\n> \n> Center: Product Launch\n> Branches: Marketing, Engineering, Sales, Support, Legal\n> Each branch should have 4-6 specific tasks\n> Color-code by priority: red = critical path, yellow = important, green = nice to have\"\n\n**Database ER diagram:**\n> \"Create an ER diagram for a project management tool:\n> \n> Entities: User, Organization, Project, Task, Comment, Attachment, Label\n> \n> Key relationships:\n> - Users belong to Organizations (many-to-many)\n> - Projects belong to Organizations\n> - Tasks belong to Projects, assigned to Users\n> - Comments belong to Tasks, created by Users\n> - Tasks can have multiple Labels (many-to-many)\n> \n> Show primary keys, foreign keys, and cardinality.\"\n\n---\n\n## Tips for Better Diagrams\n\n1. **Describe the components and relationships**: \"A connects to B which talks to C\" is all CellCog needs. Don't worry about layout.\n\n2. **Specify the diagram type**: \"Flowchart\", \"sequence diagram\", \"ER diagram\" — naming the type helps CellCog choose the right rendering approach.\n\n3. **Include data flow direction**: For architecture diagrams, mention which way data flows. \"Frontend → API → Database\" is clearer than just listing components.\n\n4. **Request interactivity**: \"I want to zoom in\" or \"clickable components\" tells CellCog to build an interactive experience.\n\n5. **Color-coding helps**: \"Color-code by team\" or \"green for success paths, red for error paths\" makes diagrams immediately useful.\n\n6. **Think about audience**: \"For the engineering team\" vs. \"for the board presentation\" changes the level of technical detail.\n\nFile v1.0.2:_meta.json\n\n{\n  \"ownerId\": \"kn7a96cj9q65e0bhmzahv790en80ffqm\",\n  \"slug\": \"diagram-flowchart-cellcog\",\n  \"version\": \"1.0.2\",\n  \"publishedAt\": 1775627874345\n}\n\nArchive v1.0.1: 2 files, 6161 bytes\n\nFiles: SKILL.md (13862b), _meta.json (144b)\n\nFile v1.0.1:SKILL.md\n\n---\nname: diagram-cog\ndescription: \"AI diagram generator — flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, network diagrams. Describe your system in plain English, get interactive zoomable diagrams or print-ready PDFs. No Visio, no Lucidchart. Powered by CellCog's frontier coding agent and app deployment infrastructure.\"\nmetadata:\n  openclaw:\n    emoji: \"🔀\"\n    os: [darwin, linux, windows]\n    requires:\n      bins: [python3]\n      env: [CELLCOG_API_KEY]\nauthor: CellCog\nhomepage: https://cellcog.ai\ndependencies: [cellcog]\n---\n\n# Diagram Cog - Describe It in Words, Get It as a Diagram\n\n**Other tools make you drag boxes. CellCog reads your mind.** Describe your system, process, or idea in plain English — CellCog produces professional, interactive diagrams you can share with a URL.\n\nNo Visio. No Lucidchart. No dragging boxes around for hours. Just describe what you need, and CellCog renders it as an interactive web page you can zoom, pan, and click — or a print-ready PDF for documentation.\n\n---\n\n## Prerequisites\n\nThis skill requires the `cellcog` skill for SDK setup and API calls.\n\n```bash\nclawhub install cellcog\n```\n\n**Read the cellcog skill first** for SDK setup. This skill shows you what's possible.\n\n**OpenClaw agents (fire-and-forget — recommended for long tasks):**\n```python\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    notify_session_key=\"agent:main:main\",  # OpenClaw only\n    task_label=\"my-task\",\n    chat_mode=\"agent\",  # See cellcog skill for all mode","readmeExcerpt":"Skill: Flowchart Owner: cellcog Summary: AI diagram and flowchart generation powered by CellCog. Flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, network diagrams. Describe your system in plain English, get interactive diagrams or print-ready PDFs. Tags: latest:1.0.10 Version history: v1.0.10 | 2026-08-24T02:01:52.299Z | user Content updated. v1.0.9 | 2026-08-24T01","codeSnippets":[],"executableExamples":[{"language":"python","snippet":"result = client.create_chat(\n    prompt=\"[your task prompt]\",\n    notify_session_key=\"agent:main:main\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)"},{"language":"python","snippet":"from cellcog import CellCogClient\nclient = CellCogClient(agent_provider=\"openclaw|cursor|claude-code|codex|...\")\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\nprint(result[\"message\"])"},{"language":"python","snippet":"result = client.create_chat(\n    prompt=\"[your task prompt]\",\n    notify_session_key=\"agent:main:main\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)"},{"language":"python","snippet":"from cellcog import CellCogClient\nclient = CellCogClient(agent_provider=\"openclaw|cursor|claude-code|codex|...\")\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\nprint(result[\"message\"])"},{"language":"python","snippet":"result = client.create_chat(\n    prompt=\"[your task prompt]\",\n    notify_session_key=\"agent:main:main\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)"},{"language":"python","snippet":"from cellcog import CellCogClient\nclient = CellCogClient(agent_provider=\"openclaw|cursor|claude-code|codex|...\")\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\nprint(result[\"message\"])"}],"parameters":null,"dependencies":[],"permissions":[],"extractedFiles":[{"path":"SKILL.md","content":"---\nname: diagram-flowchart-cellcog\ndescription: \"AI diagram and flowchart generation powered by CellCog. Flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, network diagrams. Describe your system in plain English, get interactive diagrams or print-ready PDFs.\"\nmetadata:\n  openclaw:\n    emoji: \"🔀\"\n    os: [darwin, linux, windows]\n    requires:\n      bins: [python3]\n      env: [CELLCOG_API_KEY]\nauthor: CellCog\nhomepage: https://cellcog.ai\ndependencies: [cellcog]\n---\n# Diagram & Flowchart - Describe It in Words, Get It as a Diagram\n\nDescribe your system, process, or idea in plain English — CellCog produces professional, interactive diagrams you can share with a URL.\n\nNo Visio. No Lucidchart. No dragging boxes around for hours. Just describe what you need, and CellCog renders it as an interactive web page you can zoom, pan, and click — or a print-ready PDF for documentation.\n\n## How to Use\n\nFor your first CellCog task in a session, read the **cellcog** skill for the full SDK reference — file handling, chat modes, timeouts, and more.\n\n**OpenClaw (fire-and-forget):**\n```python\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    notify_session_key=\"agent:main:main\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\n```\n\n**All agents except OpenClaw (blocks until done):**\n```python\nfrom cellcog import CellCogClient\nclient = CellCogClient(agent_provider=\"openclaw|cursor|claude-code|codex|...\")\nresult = client.create_chat(\n    prompt=\"[your task prompt]\",\n    task_label=\"my-task\",\n    chat_mode=\"agent\",\n)\nprint(result[\"message\"])\n```\n\n\n---\n\n## Why Diagrams Are Hard\n\nCreating good diagrams manually is surprisingly painful:\n\n- **Layout is tedious**: Arranging boxes, arrows, and labels takes longer than the thinking itself\n- **Tools are complex**: Visio, Lucidchart, Draw.io all have learning curves\n- **Iteration is slow**: Changing one element cascades into repositioning everything\n- **Sharing is friction**: Export → attach → hope it renders on their device\n\nCellCog eliminates all of this. Describe your diagram in words, get a shareable interactive URL. Need to change something? Just ask.\n\n---\n\n## What Makes This Different\n\nOther AI diagram tools output a static image. CellCog does something fundamentally different.\n\nCellCog **reasons about your system, picks the right rendering approach, and deploys an interactive web application** you can share with a URL. Zoom into your microservices architecture. Click a node to see details. Pan across a sprawling org chart. Or export to a print-ready PDF for your board deck.\n\n| What You Ask For | What CellCog Actually Does |\n|-----------------|---------------------------|\n| \"Diagram my microservices\" | Reasons about the architecture → generates Mermaid/D3 code → deploys interactive web app → delivers shareable URL |\n| \"Flowchart for our hiring process\" | Analyzes the process → renders with proper decision logic → color-codes paths → interactive HTML with "},{"path":"_meta.json","content":"{\n  \"ownerId\": \"kn7a96cj9q65e0bhmzahv790en80ffqm\",\n  \"slug\": \"diagram-flowchart-cellcog\",\n  \"version\": \"1.0.10\",\n  \"publishedAt\": 1787536912299\n}"},{"path":"skill-card.md","content":"## Description:\n\nFlowchart helps agents use CellCog to generate interactive diagrams and print-ready PDFs from plain-language descriptions, including flowcharts, system architecture diagrams, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, and network diagrams.\n\nThis skill is ready for commercial/non-commercial use.\n\n## Publisher:\n\n[cellcog](https://clawhub.ai/user/cellcog)\n\n### License/Terms of Use:\n\nMIT-0\n\n## Use Case:\n\nDevelopers, architects, product teams, and technical writers use this skill to turn process, system, data, and planning descriptions into shareable diagrams. It is suited for flowcharts, architecture diagrams, mind maps, org charts, UML, ER diagrams, network diagrams, timelines, swimlanes, and user journey maps.\n\n### Deployment Geography for Use:\n\nGlobal\n\n## Known Risks and Mitigations:\n\nRisk: User prompts and provided materials may be sent to CellCog and may be used to create a shareable hosted diagram output.\n\nMitigation: Do not include secrets, credentials, regulated data, or internal-only architecture details unless sharing them with CellCog and producing a shareable output is intended.\n\nRisk: The skill requires installing and using the CellCog dependency and API key.\n\nMitigation: Install only from a trusted CellCog source, prefer pinned versions where possible, and keep CELLCOG_API_KEY out of shared prompts, files, and logs.\n\n## Reference(s):\n\n- [ClawHub skill page](https://clawhub.ai/cellcog/skills/diagram-flowchart-cellcog)\n- [CellCog homepage](https://cellcog.ai)\n\n## Skill Output:\n\n**Output Type(s):** [Guidance, Code, Shell commands, Configuration]\n\n**Output Format:** [Markdown guidance with Python snippets and setup commands; generated diagrams are delivered as interactive HTML or PDF.]\n\n**Output Parameters:** [1D]\n\n**Other Properties Related to Output:** [Requires the CellCog package, python3, and CELLCOG_API_KEY; diagram work may create a shareable hosted output.]\n\n## Skill Version(s):\n\n1.0.10 (source: server release metadata)\n\n## Ethical Considerations:\n\nUsers should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment."}],"languages":[],"docsSourceLabel":"CLAWHUB","editorialOverview":"AI diagram and flowchart generation powered by CellCog. Flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, network diagrams. Describe your system in plain English, get interactive diagrams or print-ready PDFs. Skill: Flowchart Owner: cellcog Summary: AI diagram and flowchart generation powered by CellCog. Flowcharts, system architecture, mind maps, org charts, ER diagrams, sequence diagrams, Gantt charts, network diagrams. Describe your system in plain English, get interactive diagrams or print-ready PDFs. Tags: latest:1.0.10 Version history: v1.0.10 | 2026-08-24T02:01:52.299Z | user Content updated. v1.0.9 | 2026-08-24T01","editorialQuality":{"score":100,"threshold":65,"status":"ready","wordCount":1227,"uniquenessScore":52,"reasons":[]}},"media":{"evidence":{"source":"no-media","verified":false,"confidence":"low","updatedAt":"2026-10-09T23:09:36.833Z","emptyReason":"No screenshots, media assets, or demo links are available."},"primaryImageUrl":null,"mediaAssetCount":0,"assets":[],"demoUrl":null},"ownerResources":{"evidence":{"source":"unclaimed","verified":false,"confidence":"low","updatedAt":"2026-10-09T23:09:36.833Z","emptyReason":"This page has not been claimed by the agent owner."},"hasCustomPage":false,"customPageUpdatedAt":null,"customLinks":[],"structuredLinks":{"docsUrl":null,"demoUrl":null,"supportUrl":null,"pricingUrl":null,"statusUrl":null},"customPage":null},"relatedAgents":{"evidence":{"source":"protocol-neighbors","verified":false,"confidence":"medium","updatedAt":"2026-10-10T07:40:06.488Z","emptyReason":null},"items":[{"id":"8ebccd8e-3863-4187-8355-c3f14e1f9edf","entityType":"agent","canonicalPath":"/agent/iofficeai-aionui","slug":"iofficeai-aionui","name":"AionUi","description":"Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!","url":"https://github.com/iOfficeAI/AionUi","homepage":"https://www.aionui.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-10-09T19:11:12.944Z","createdAt":"2026-02-25T03:38:16.584Z","downloads":null},{"id":"b917f68a-ebff-438e-84f8-3f4b2494c0bc","entityType":"agent","canonicalPath":"/agent/activepieces-activepieces","slug":"activepieces-activepieces","name":"activepieces","description":"AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents","url":"https://github.com/activepieces/activepieces","homepage":"https://www.activepieces.com","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-15T02:22:12.426Z","createdAt":"2026-02-25T03:38:12.412Z","downloads":null},{"id":"5cb26759-3a39-483f-94cf-276a98c13bb8","entityType":"agent","canonicalPath":"/agent/cherryhq-cherry-studio","slug":"cherryhq-cherry-studio","name":"cherry-studio","description":"AI productivity studio with smart chat, autonomous agents, and 300+ assistants. Unified access to frontier LLMs","url":"https://github.com/CherryHQ/cherry-studio","homepage":"https://cherry-ai.com","source":"GITHUB_REPOS","protocols":["MCP","OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-04-11T14:38:40.986Z","createdAt":"2026-02-25T03:38:19.379Z","downloads":null},{"id":"6f6582d0-5d76-4f0f-b81d-86520247950b","entityType":"agent","canonicalPath":"/agent/copilotkit-copilotkit","slug":"copilotkit-copilotkit","name":"CopilotKit","description":"The Frontend for Agents & Generative UI. React + Angular","url":"https://github.com/CopilotKit/CopilotKit","homepage":"https://docs.copilotkit.ai","source":"GITHUB_REPOS","protocols":["OPENCLAW"],"capabilities":[],"safetyScore":100,"overallRank":70,"updatedAt":"2026-03-25T09:50:57.846Z","createdAt":"2026-02-25T03:39:14.617Z","downloads":null}],"links":{"hub":"/agent","source":"/agent/source/clawhub","protocols":[{"label":"OpenClaw","href":"/agent/protocol/openclew"}]}}}