據 AlphaMoat 統計,截至 2026-10,Draw.io Skill 累計下載 9,370 次、獲 0 個星標,按累計下載量在本次參與排名的 10,914 個 AI 技能中排名第 2,944 位,在「設計創意」分類(1,116 個)中排名第 382 位。
列表預設按累計下載量排序,也可按星標排序;詳情頁排名按累計下載量計算。
| 平台 | 累計下載 | 星標 | 評論 |
|---|---|---|---|
| ClawHub ↗ | 4311 | - | 1 |
| SkillHub ↗ | 9370 | - | — |
各平台的計數口徑不同,統計時間不一致。
該技能要求先讀取當前圖表再編輯,並可匯出可編輯原始檔或用於分享的 SVG。技能卡提示推薦的第三方 MCP 服務包未固定版本,操作可能修改即時圖表或在工作區寫入匯出檔案,且依賴外部 MCP 連線及當前會話狀態。安裝前審查固定版本;編輯前讀取現有內容並保留使用者變更,匯出後檢查檔案。 新建工作或在新連線中檢查前先啟動 session,編輯前讀取真實 cell ID。技能本身不打包或安裝 MCP 服務,工具缺失時應重新連線並確認可用性。
資料釋出於 2026-10-29
以下是根據技能文件生成的示例,不代表實際執行結果。
2026-09 起統計方法調整:同名技能按作者分別統計,並覆蓋全部技能。圖中虛線為調整前的月份,與之後的資料不直接比較,也不計算跨越調整的增長。
| 月份 | 累計下載 | 環比 | 星標 |
|---|---|---|---|
| 2026-10 | 9370 | — | - |
| 2026-09 | 5060 | — | - |
| 2026-08 | 3818 | +27.6% | - |
| 2026-07 | 2992 | +67.7% | - |
| 2026-06 | 1784 | +41.8% | - |
| 2026-05 | 1258 | — | - |
| 2026-03 | 191 | — | - |
以下是作者釋出的原始檔案,按純文字顯示,本站未做修改或稽核;其中的連結不可點選,命令請核實後再執行。抓取於 2026-10-23。
--- name: drawio-skill description: Create and edit draw.io diagrams through the configured drawio MCP server, including flowcharts, architecture diagrams, ML model diagrams, Chinese labels, animated connectors, and svg export. --- # Draw.io Skill Use this skill for all draw.io and diagrams.net work. This skill wraps the configured `drawio` MCP server; it does not replace the server. ## Required workflow
1. Start the draw.io session first. - Call `start_session` before creating a new diagram or before inspecting or editing a diagram in a fresh session. 2. Create new diagrams from complete XML. - Use `create_new_diagram` with a full `mxGraphModel`. - Keep the diagram within a single viewport when practical. 3. Read before editing. - Always call `get_diagram` before `edit_diagram`. - Do not guess cell IDs. - Preserve user changes already present in the live session. 4. Export deliverables. - Export `.drawio` for editable source. - Export `.svg` when the user needs a shareable artifact or when the diagram uses animated connectors. 5. Report outputs clearly. - Tell the user which files were exported and where they were written. ## Export naming convention - Write exports to the current workspace unless the user specifies a path. - Derive a short kebab-case basename from the main topic when possible, such as `user-login-flow`, `payment-architecture`, or `event-pipeline`. - If the topic is unclear, use `diagram`. - For Chinese-language outputs, prefer an ASCII basename with a `-zh` suffix, such as `order-flow-zh`. - For architecture diagrams, prefer `-architecture`, `-topology`, or `-flow` suffixes when they improve clarity. - For machine-learning diagrams, prefer model-aware basenames such as `lstm-architecture`, `transformer-blocks`, or `cnn-pipeline`. - When exporting both editable and shareable artifacts, keep the same basename for both, such as `diagram.drawio` and `diagram.svg`. - Avoid spaces and non-ASCII characters in filenames unless the user explicitly requests them. ## Language and labeling rules - If the request is primarily in Simplified Chinese, reply in Simplified Chinese. - If the user wants Chinese labels, legends, or summaries, keep the diagram wording in Simplified Chinese. - Keep standard abbreviations and proper nouns in their common form, such as API, Kafka, Redis, Kubernetes, LSTM, CNN, and Transformer. - Keep node text short enough to fit inside shapes. ## General diagram rules - Prefer clear left-to-right or top-to-bottom flow. - Use explicit edge routing and waypoints when edges would otherwise overlap. - Use titles, legends, and note boxes sparingly. - Use color intentionally to separate data flow, control flow, or state. ## Architecture-specific rules - Identify the major layers first, such as clients, edge, services, data, and external systems. - Draw boundaries for environments or trust zones when relevant, such as browser, VPC, cluster, region, or third-party systems. - Keep arrows directional and semantically consistent. - Label protocols, topics, or data contracts only when they matter to the reader. - Use containers for service groups, domains, or infrastructure groups instead of loose boxes. ## ML-diagram rules - Show the main flow clearly from input to output. - Use repeated blocks, grouped containers, and stage labels for model structure. - Label tensor shape, sequence length, channel count, or embedding size only when it helps understanding. - Use consistent color semantics for inputs, hidden states, attention paths, residual paths, and outputs. - For recurrent or temporal models, make state flow visually distinct from data flow. - For LSTM and RNN diagrams, separate cell state and hidden state. - For Transformer diagrams, distinguish embeddings, attention, feed-forward blocks, residual paths, and normalization. - For CNN diagrams, emphasize feature-map progression, pooling, skip paths, and classifier head. ## Animated connectors When the user asks for animated connectors, flowing lines, or moving dashed lines: - Add edge styling such as `dashed=1;dashPattern=8 4;flowAnimation=1;`. - Keep arrowheads explicit with `endArrow=classic` unless the requested style suggests otherwise. - Export to `.svg` because the animation is preserved there. ## Setup and recovery This skill expects the `drawio` MCP server to already be configured and available. - If the server is unavailable, tell the user that the drawio MCP connection needs to be configured or reconnected before continuing. - After the connection is restored, restart the Codex session or reload the IDE window if the tools still do not appear. ## Good triggers - "Create a system diagram in draw.io" - "Create a Chinese-labeled draw.io diagram" - "Edit this flowchart" - "Export the current diagram as draw.io and svg" - "Create a diagram with animated connectors" - "Turn this process into a draw.io diagram" - "Create a cloud architecture diagram" - "Map a deployment topology" - "Draw a business process flowchart" - "Create an animated LSTM diagram" - "Draw a Transformer architecture" - "Create a CNN block diagram" - "Update the existing draw.io layout and keep the same structure" - "Generate a box-and-arrow diagram for this workflow" ## Limitations - This skill depends on a working `drawio` MCP server. - The editing workflow operates on the live draw.io session state exposed by the MCP tools. - This skill does not bundle or install the MCP server by itself.
透過同一個AI創作工具完成AI圖片、影片、音樂與語音創作,查詢公開社交資料,編輯視覺成果,並集中檢視和管理生成資產。Beatra 全能創作支援AI圖片生成(文生圖)、AI影片生成(圖生影片)和AI影片編輯,透過AI音樂生成把想法做成歌曲或純音樂,也可用AI語音生成(文字轉語音)、多語言旁白和AI語音克隆完成跨媒介內容;還能查詢抖音資料、小紅書資料,以及 YouTube、TikTok、Instagram 與 X 上的公開帖子、筆記、評論、賬號和趨勢,把社交媒體資料用於競品調研和創作。它是一款面向AI內容創作與多模態內容創作的AI創作套件,用起來就是一個把圖片、影片、音樂與語音收在同一處的AI創作助手,適用於社交內容、產品展示、行銷素材、課程、播客、短片和跨媒介專案;還能在不同媒介間複用原始素材、已有成果和查到的公開資料,檢視製作進度、返回檔案、實際用量和積分記錄。
用一張人像和一段短指令碼或語音,製作有明確講述內容的數位人口播影片。可使用現成錄音,也可以先選擇音色,把指令碼生成旁白,讓畫面中的人物隨聲音完成穩定、自然的口播。適合 AI 主播、虛擬主播影片、數位人講解、讓照片說話、照片說話影片、產品講解影片、數位人培訓影片、公告和社交口播,並在交付後檢查人物一致性、聲音清晰度、口型同步和動作穩定性。一節課的講解也能做成課程口播。
ContextWeave 架構圖一鍵生成
將一段活動描述、一張產品照片或品牌參考圖,轉化為抓人眼球的活動海報、宣傳 banner 或社交媒體配圖。這款 AI海報設計與製作工具生成圖片豐富的海報,在海報排版上搭配清晰視覺層級、按品類匹配的風格和預留文字區域,覆蓋活動、音樂節、電影、產品釋出和促銷場景。你可以把它當作 AI宣傳單製作工具來製作促銷宣傳單,當作活動海報設計工具,當作電影海報生成器,當作音樂節海報設計工具,當作產品釋出會海報的 banner設計 AI,或當作平面設計海報工作室。從活動主題出發,用品牌風格參考圖變換產品或場景照片,或在已認可草稿上做定向精修,完成可印刷或可分享的成品。
抖音短影片雙路徑生產體系(單 Skill 版)。Path A[付費·高質量]:策略大腦→(可選:素材混剪/AI高光提取)→指令碼最佳化→AI生圖/素材準備→配音渲染(百鍊/GPT-SoVITS/CosyVoice/VoxCPM2+剪映/Remotion/ffmpeg/數位人)。Path B[免費·動畫風]:採集熱點→指令碼→edge-tts免費配音+HyperFrames開源渲染→MP4,零雲費開箱快。觸發詞分層:①"抖音短影片/選題規劃/合規閘門/營運策略" ②"口播指令碼/AI生圖/AI配音/影片渲染/Remotion渲染" ③"蹭熱點/快速出片/免費做影片" ④"混剪/高光提取/素材粗剪/autoclip
GPT Image 2.5生圖是一款 AI 工具,用 GPT-Image-2.5 和 ChatGPT Images 2.5 出一張圖。GPT Image 2.5 Studio 支援 gpt-image-2.5-flare 與 gpt-image-2.5-sunburst,可文生圖或參考圖生圖,做中文海報、商品圖、資訊圖和社媒畫面。
用 MiniMax H3 這款 AI影片生成器創作高質感 2K AI 影片。從文字創意出發完成文生影片,讓靜態圖片自然動起來,用首尾畫面做首尾幀影片的完整轉場,也可以結合圖片、影片和音訊參考,以多模態影片生成塑造統一場景。適合 AI 廣告影片、電商產品影片、品牌宣傳影片、動態海報、遊戲 UI、電影片頭和社交短影片創作,形成電影感畫面與同步的原生立體聲。使用 Beatra 賬號即可開始,創作進度與成片集中管理。
輸入品牌名稱、行業方向或參考圖,生成專業 AI Logo、品牌標識和應用圖示。這款 AI logo 設計工具從你的品牌簡報出發——公司名、行業氣質、配色偏好——先探索多個商標設計方向,再用精確品牌色、簡潔幾何和可縮放構圖精修最強概念。製作企業 logo、創業公司標誌、字母標、徽章、組合標識和 VI設計中的主標,從網站 favicon 到門頭招牌都清晰可辨。從文字描述出發,將已有草圖和品牌素材轉化為精緻標識,或在已認可草稿上做定向精修。
資料月份:2026-10 · 下載/星標數聚合自公開技能註冊庫(ClawHub、SkillHub),按月更新。口徑說明見資料方法。