[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AMFAA8FDFJQPT9AZ9178E4":3,"skill-same:01M7AMFAA8FDFJQPT9AZ9178E4":69},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7AMFAA8FDFJQPT9AZ9178E4","draw-io",null,"draw.io diagram creation, editing, and review. Use for .drawio XML editing, PNG conversion, layout adjustment, and AWS icon usage.","GongYuanCaiJi\u002Fdsh-claude-code-templates","GongYuanCaiJi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129952120?v=4","01M7AK39Q4W3VPF7C1K8M58BFX","劉昱廷 Yu-Ting Liu","01M7AK39QPS2RAJKRQY0EPQJPZ",0,"MIT","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fcreative-design\u002Fdraw-io\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: draw-io\ndescription: draw.io diagram creation, editing, and review. Use for .drawio XML editing, PNG conversion, layout adjustment, and AWS icon usage.\n---\n\n# draw.io Diagram Skill\n\n## 1. Basic Rules\n\n- Edit only `.drawio` files\n- Do not directly edit `.drawio.png` files\n- Use auto-generated `.drawio.png` by pre-commit hook in slides\n\n## 2. Font Settings\n\nFor diagrams used in Quarto slides,\nspecify `defaultFontFamily` in mxGraphModel tag:\n\n```xml\n\u003CmxGraphModel defaultFontFamily=\"Noto Sans JP\" ...>\n```\n\nAlso explicitly specify `fontFamily` in each text element's style attribute:\n\n```xml\nstyle=\"text;html=1;fontSize=27;fontFamily=Noto Sans JP;\"\n```\n\n## 3. Conversion Commands\n\nSee conversion script at [scripts\u002Fconvert-drawio-to-png.sh](scripts\u002Fconvert-drawio-to-png.sh).\n\n```sh\n# Convert all .drawio files\nmise exec -- pre-commit run --all-files\n\n# Convert specific .drawio file\nmise exec -- pre-commit run convert-drawio-to-png --files assets\u002Fmy-diagram.drawio\n\n# Run script directly (using skill's script)\nbash ~\u002F.claude\u002Fskills\u002Fdraw-io\u002Fscripts\u002Fconvert-drawio-to-png.sh assets\u002Fdiagram1.drawio\n```\n\nInternal command used:\n\n```sh\ndrawio -x -f png -s 2 -t -o output.drawio.png input.drawio\n```\n\n| Option | Description |\n|--------|-------------|\n| `-x` | Export mode |\n| `-f png` | PNG format output |\n| `-s 2` | 2x scale (high resolution) |\n| `-t` | Transparent background |\n| `-o` | Output file path |\n\n## 4. Layout Adjustment\n\n### 4.1. Coordinate Adjustment Steps\n\n1. Open `.drawio` file in text editor (plain XML format)\n2. Find `mxCell` for element to adjust (search by `value` attribute for text)\n3. Adjust coordinates in `mxGeometry` tag\n   - `x`: Position from left\n   - `y`: Position from top\n   - `width`: Width\n   - `height`: Height\n4. Run conversion and verify\n\n### 4.2. Coordinate Calculation\n\n- Element center coordinate = `y + (height \u002F 2)`\n- To align multiple elements, calculate and match center coordinates\n\n## 5. Design Principles\n\n### 5.1. Basic Principles\n\n- Clarity: Create simple, visually clean diagrams\n- Consistency: Unify colors, fonts, icon sizes, line thickness\n- Accuracy: Do not sacrifice accuracy for simplification\n\n### 5.2. Element Rules\n\n- Label all elements\n- Use arrows to indicate direction\n  (prefer 2 unidirectional arrows over bidirectional)\n- Use latest official icons\n- Add legend to explain custom symbols\n\n### 5.3. Accessibility\n\n- Ensure sufficient color contrast\n- Use patterns in addition to colors\n\n### 5.4. Progressive Disclosure\n\nSeparate complex systems into staged diagrams:\n\n| Diagram Type | Purpose |\n|--------------|---------|\n| Context Diagram | System overview from external perspective |\n| System Diagram | Main components and relationships |\n| Component Diagram | Technical details and integration points |\n| Deployment Diagram | Infrastructure configuration |\n| Data Flow Diagram | Data flow and transformation |\n| Sequence Diagram | Time-series interactions |\n\n### 5.5. Metadata\n\nInclude title, description, last updated, author, and version in diagrams.\n\n## 6. Best Practices\n\n### 6.1. Background Color\n\n- Remove `background=\"#ffffff\"`\n- Transparent background adapts to various themes\n\n### 6.2. Font Size\n\n- Use 1.5x standard font size (around 18px) for PDF readability\n\n### 6.3. Japanese Text Width\n\n- Allow 30-40px per character\n- Insufficient width causes unintended line breaks\n\n```xml\n\u003C!-- For 10-character text, allow 300-400px -->\n\u003CmxGeometry x=\"140\" y=\"60\" width=\"400\" height=\"40\" \u002F>\n```\n\n### 6.4. Arrow Placement\n\n- Always place arrows at back (position in XML right after Title)\n- Position arrows to avoid overlapping with labels\n- Keep arrow start\u002Fend at least 20px from label bottom edge\n\n```xml\n\u003C!-- Title -->\n\u003CmxCell id=\"title\" value=\"...\" ...\u002F>\n\n\u003C!-- Arrows (back layer) -->\n\u003CmxCell id=\"arrow1\" style=\"edgeStyle=...\" ...\u002F>\n\n\u003C!-- Other elements (front layer) -->\n\u003CmxCell id=\"box1\" ...\u002F>\n```\n\n### 6.5. Arrow Connection to Text Labels\n\nFor text elements, exitX\u002FexitY don't work, so use explicit coordinates:\n\n```xml\n\u003C!-- Good: Explicit coordinates with sourcePoint\u002FtargetPoint -->\n\u003CmxCell id=\"arrow\" style=\"...\" edge=\"1\" parent=\"1\">\n  \u003CmxGeometry relative=\"1\" as=\"geometry\">\n    \u003CmxPoint x=\"1279\" y=\"500\" as=\"sourcePoint\"\u002F>\n    \u003CmxPoint x=\"119\" y=\"500\" as=\"targetPoint\"\u002F>\n    \u003CArray as=\"points\">\n      \u003CmxPoint x=\"1279\" y=\"560\"\u002F>\n      \u003CmxPoint x=\"119\" y=\"560\"\u002F>\n    \u003C\u002FArray>\n  \u003C\u002FmxGeometry>\n\u003C\u002FmxCell>\n```\n\n### 6.6. edgeLabel Offset Adjustment\n\nAdjust offset attribute to distance arrow labels from arrows:\n\n```xml\n\u003C!-- Place above arrow (negative value to distance) -->\n\u003CmxPoint x=\"0\" y=\"-40\" as=\"offset\"\u002F>\n\n\u003C!-- Place below arrow (positive value to distance) -->\n\u003CmxPoint x=\"0\" y=\"40\" as=\"offset\"\u002F>\n```\n\n### 6.7. Remove Unnecessary Elements\n\n- Remove decorative icons irrelevant to context\n- Example: If ECR exists, separate Docker icon is unnecessary\n\n### 6.8. Labels and Headings\n\n- Service name only: 1 line\n- Service name + supplementary info: 2 lines with line break\n- Redundant notation (e.g., ECR Container Registry): shorten to 1 line\n- Use `&lt;br&gt;` tag for line breaks\n\n### 6.9. Background Frame and Internal Element Placement\n\nWhen placing elements inside background frames (grouping boxes),\nensure sufficient margin.\n\n- YOU MUST: Internal elements must have at least 30px margin from frame boundary\n- YOU MUST: Account for rounded corners (`rounded=1`) and stroke width\n- YOU MUST: Always visually verify PNG output for overflow\n\nCoordinate calculation verification:\n\n```text\nBackground frame: y=20, height=400 -> range is y=20-420\nInternal element top: frame y + 30 or more (e.g., y=50)\nInternal element bottom: frame y + height - 30 or less (e.g., up to y=390)\n```\n\nBad example (may overflow):\n\n```xml\n\u003C!-- Background frame -->\n\u003CmxCell id=\"bg\" style=\"rounded=1;strokeWidth=3;...\">\n  \u003CmxGeometry x=\"500\" y=\"20\" width=\"560\" height=\"400\" \u002F>\n\u003C\u002FmxCell>\n\u003C!-- Text: y=30 is too close to frame top (y=20) -->\n\u003CmxCell id=\"label\" value=\"Title\" style=\"text;...\">\n  \u003CmxGeometry x=\"510\" y=\"30\" width=\"540\" height=\"35\" \u002F>\n\u003C\u002FmxCell>\n```\n\nGood example (sufficient margin):\n\n```xml\n\u003C!-- Background frame -->\n\u003CmxCell id=\"bg\" style=\"rounded=1;strokeWidth=3;...\">\n  \u003CmxGeometry x=\"500\" y=\"20\" width=\"560\" height=\"430\" \u002F>\n\u003C\u002FmxCell>\n\u003C!-- Text: y=50 is 30px from frame top (y=20) -->\n\u003CmxCell id=\"label\" value=\"Title\" style=\"text;...\">\n  \u003CmxGeometry x=\"510\" y=\"50\" width=\"540\" height=\"35\" \u002F>\n\u003C\u002FmxCell>\n```\n\n## 7. Reference\n\n- [Layout Guidelines](references\u002Flayout-guidelines.md)\n- [AWS Icons](references\u002Faws-icons.md)\n- [AWS Icon Search Script](scripts\u002Ffind_aws_icon.py)\n\nAWS icon search examples:\n\n```sh\npython ~\u002F.claude\u002Fskills\u002Fdraw-io\u002Fscripts\u002Ffind_aws_icon.py ec2\npython ~\u002F.claude\u002Fskills\u002Fdraw-io\u002Fscripts\u002Ffind_aws_icon.py lambda\n```\n\n## 8. Checklist\n\n- [ ] No background color set (page=\"0\")\n- [ ] Font size appropriate (larger recommended)\n- [ ] Arrows placed at back layer\n- [ ] Arrows not overlapping labels (verify in PNG)\n- [ ] Arrow start\u002Fend sufficiently distant from labels (at least 20px)\n- [ ] Arrows not penetrating boxes or icons (verify in PNG)\n- [ ] Internal elements not overflowing background frame (verify in PNG)\n- [ ] 30px+ margin between background frame and internal elements\n- [ ] AWS service names are official names\u002Fcorrect abbreviations\n- [ ] AWS icons are latest version (mxgraph.aws4.*)\n- [ ] No unnecessary elements remaining\n- [ ] Visually verified PNG conversion\n\n## 9. Image Display in reveal.js Slides\n\nAdd `auto-stretch: false` to YAML header:\n\n```yaml\n---\ntitle: \"Your Presentation\"\nformat:\n  revealjs:\n    auto-stretch: false\n---\n```\n\nThis ensures correct image display on mobile devices.\n","# draw.io Diagram Skill\n\n## 1. Basic Rules\n\n- Edit only `.drawio` files\n- Do not directly edit `.drawio.png` files\n- Use auto-generated `.drawio.png` by pre-commit hook in slides\n\n## 2. Font Settings\n\nFor diagrams used in Quarto slides,\nspecify `defaultFontFamily` in mxGraphModel tag:\n\n```xml\n\u003CmxGraphModel defaultFontFamily=\"Noto Sans JP\" ...>\n```\n\nAlso explicitly specify `fontFamily` in each text element's style attribute:\n\n```xml\nstyle=\"text;html=1;fontSize=27;fontFamily=Noto Sans JP;\"\n```\n\n## 3. Conversion Commands\n\nSee conversion script at [scripts\u002Fconvert-drawio-to-png.sh](scripts\u002Fconvert-drawio-to-png.sh).\n\n```sh\n# Convert all .drawio files\nmise exec -- pre-commit run --all-files\n\n# Convert specific .drawio file\nmise exec -- pre-commit run convert-drawio-to-png --files assets\u002Fmy-diagram.drawio\n\n# Run script directly (using skill's script)\nbash ~\u002F.claude\u002Fskills\u002Fdraw-io\u002Fscripts\u002Fconvert-drawio-to-png.sh assets\u002Fdiagram1.drawio\n```\n\nInternal command used:\n\n```sh\ndrawio -x -f png -s 2 -t -o output.drawio.png input.drawio\n```\n\n| Option | Description |\n|--------|-------------|\n| `-x` | Export mode |\n| `-f png` | PNG format output |\n| `-s 2` | 2x scale (high resolution) |\n| `-t` | Transparent background |\n| `-o` | Output file path |\n\n## 4. Layout Adjustment\n\n### 4.1. Coordinate Adjustment Steps\n\n1. Open `.drawio` file in text editor (plain XML format)\n2. Find `mxCell` for element to adjust (search by `value` attribute for text)\n3. Adjust coordinates in `mxGeometry` tag\n   - `x`: Position from left\n   - `y`: Position from top\n   - `width`: Width\n   - `height`: Height\n4. Run conversion and verify\n\n### 4.2. Coordinate Calculation\n\n- Element center coordinate = `y + (height \u002F 2)`\n- To align multiple elements, calculate and match center coordinates\n\n## 5. Design Principles\n\n### 5.1. Basic Principles\n\n- Clarity: Create simple, visually clean diagrams\n- Consistency: Unify colors, fonts, icon sizes, line thickness\n- Accuracy: Do not sacrifice accuracy for simplification\n\n### 5.2. Element Rules\n\n- Label all elements\n- Use arrows to indicate direction\n  (prefer 2 unidirectional arrows over bidirectional)\n- Use latest official icons\n- Add legend to explain custom symbols\n\n### 5.3. Accessibility\n\n- Ensure sufficient color contrast\n- Use patterns in addition to colors\n\n### 5.4. Progressive Disclosure\n\nSeparate complex systems into staged diagrams:\n\n| Diagram Type | Purpose |\n|--------------|---------|\n| Context Diagram | System overview from external perspective |\n| System Diagram | Main components and relationships |\n| Component Diagram | Technical details and integration points |\n| Deployment Diagram | Infrastructure configuration |\n| Data Flow Diagram | Data flow and transformation |\n| Sequence Diagram | Time-series interactions |\n\n### 5.5. Metadata\n\nInclude title, description, last updated, author, and version in diagrams.\n\n## 6. Best Practices\n\n### 6.1. Background Color\n\n- Remove `background=\"#ffffff\"`\n- Transparent background adapts to various themes\n\n### 6.2. Font Size\n\n- Use 1.5x standard font size (around 18px) for PDF readability\n\n### 6.3. Japanese Text Width\n\n- Allow 30-40px per character\n- Insufficient width causes unintended line breaks\n\n```xml\n\u003C!-- For 10-character text, allow 300-400px -->\n\u003CmxGeometry x=\"140\" y=\"60\" width=\"400\" height=\"40\" \u002F>\n```\n\n### 6.4. Arrow Placement\n\n- Always place arrows at back (position in XML right after Title)\n- Position arrows to avoid overlapping with labels\n- Keep arrow start\u002Fend at least 20px from label bottom edge\n\n```xml\n\u003C!-- Title -->\n\u003CmxCell id=\"title\" value=\"...\" ...\u002F>\n\n\u003C!-- Arrows (back layer) -->\n\u003CmxCell id=\"arrow1\" style=\"edgeStyle=...\" ...\u002F>\n\n\u003C!-- Other elements (front layer) -->\n\u003CmxCell id=\"box1\" ...\u002F>\n```\n\n### 6.5. Arrow Connection to Text Labels\n\nFor text elements, exitX\u002FexitY don't work, so use explicit coordinates:\n\n```xml\n\u003C!-- Good: Explicit coordinates with sourcePoint\u002FtargetPoint -->\n\u003CmxCell id=\"arrow\" style=\"...\" edge=\"1\" parent=\"1\">\n  \u003CmxGeometry relative=\"1\" as=\"geometry\">\n    \u003CmxPoint x=\"1279\" y=\"500\" as=\"sourcePoint\"\u002F>\n    \u003CmxPoint x=\"119\" y=\"500\" as=\"targetPoint\"\u002F>\n    \u003CArray as=\"points\">\n      \u003CmxPoint x=\"1279\" y=\"560\"\u002F>\n      \u003CmxPoint x=\"119\" y=\"560\"\u002F>\n    \u003C\u002FArray>\n  \u003C\u002FmxGeometry>\n\u003C\u002FmxCell>\n```\n\n### 6.6. edgeLabel Offset Adjustment\n\nAdjust offset attribute to distance arrow labels from arrows:\n\n```xml\n\u003C!-- Place above arrow (negative value to distance) -->\n\u003CmxPoint x=\"0\" y=\"-40\" as=\"offset\"\u002F>\n\n\u003C!-- Place below arrow (positive value to distance) -->\n\u003CmxPoint x=\"0\" y=\"40\" as=\"offset\"\u002F>\n```\n\n### 6.7. Remove Unnecessary Elements\n\n- Remove decorative icons irrelevant to context\n- Example: If ECR exists, separate Docker icon is unnecessary\n\n### 6.8. Labels and Headings\n\n- Service name only: 1 line\n- Service name + supplementary info: 2 lines with line break\n- Redundant notation (e.g., ECR Container Registry): shorten to 1 line\n- Use `&lt;br&gt;` tag for line breaks\n\n### 6.9. Background Frame and Internal Element Placement\n\nWhen placing elements inside background frames (grouping boxes),\nensure sufficient margin.\n\n- YOU MUST: Internal elements must have at least 30px margin from frame boundary\n- YOU MUST: Account for rounded corners (`rounded=1`) and stroke width\n- YOU MUST: Always visually verify PNG output for overflow\n\nCoordinate calculation verification:\n\n```text\nBackground frame: y=20, height=400 -> range is y=20-420\nInternal element top: frame y + 30 or more (e.g., y=50)\nInternal element bottom: frame y + height - 30 or less (e.g., up to y=390)\n```\n\nBad example (may overflow):\n\n```xml\n\u003C!-- Background frame -->\n\u003CmxCell id=\"bg\" style=\"rounded=1;strokeWidth=3;...\">\n  \u003CmxGeometry x=\"500\" y=\"20\" width=\"560\" height=\"400\" \u002F>\n\u003C\u002FmxCell>\n\u003C!-- Text: y=30 is too close to frame top (y=20) -->\n\u003CmxCell id=\"label\" value=\"Title\" style=\"text;...\">\n  \u003CmxGeometry x=\"510\" y=\"30\" width=\"540\" height=\"35\" \u002F>\n\u003C\u002FmxCell>\n```\n\nGood example (sufficient margin):\n\n```xml\n\u003C!-- Background frame -->\n\u003CmxCell id=\"bg\" style=\"rounded=1;strokeWidth=3;...\">\n  \u003CmxGeometry x=\"500\" y=\"20\" width=\"560\" height=\"430\" \u002F>\n\u003C\u002FmxCell>\n\u003C!-- Text: y=50 is 30px from frame top (y=20) -->\n\u003CmxCell id=\"label\" value=\"Title\" style=\"text;...\">\n  \u003CmxGeometry x=\"510\" y=\"50\" width=\"540\" height=\"35\" \u002F>\n\u003C\u002FmxCell>\n```\n\n## 7. Reference\n\n- [Layout Guidelines](references\u002Flayout-guidelines.md)\n- [AWS Icons](references\u002Faws-icons.md)\n- [AWS Icon Search Script](scripts\u002Ffind_aws_icon.py)\n\nAWS icon search examples:\n\n```sh\npython ~\u002F.claude\u002Fskills\u002Fdraw-io\u002Fscripts\u002Ffind_aws_icon.py ec2\npython ~\u002F.claude\u002Fskills\u002Fdraw-io\u002Fscripts\u002Ffind_aws_icon.py lambda\n```\n\n## 8. Checklist\n\n- [ ] No background color set (page=\"0\")\n- [ ] Font size appropriate (larger recommended)\n- [ ] Arrows placed at back layer\n- [ ] Arrows not overlapping labels (verify in PNG)\n- [ ] Arrow start\u002Fend sufficiently distant from labels (at least 20px)\n- [ ] Arrows not penetrating boxes or icons (verify in PNG)\n- [ ] Internal elements not overflowing background frame (verify in PNG)\n- [ ] 30px+ margin between background frame and internal elements\n- [ ] AWS service names are official names\u002Fcorrect abbreviations\n- [ ] AWS icons are latest version (mxgraph.aws4.*)\n- [ ] No unnecessary elements remaining\n- [ ] Visually verified PNG conversion\n\n## 9. Image Display in reveal.js Slides\n\nAdd `auto-stretch: false` to YAML header:\n\n```yaml\n---\ntitle: \"Your Presentation\"\nformat:\n  revealjs:\n    auto-stretch: false\n---\n```\n\nThis ensures correct image display on mobile devices.\n",{"name":5,"description":7},"main","51493f354fd03e3f941d4df7fd64c0b8c7a2632d","skills\u002Fcreative-design\u002Fdraw-io","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi","漏洞研究、根因分析、黑箱測試｜做 AI agent 工具｜Vulnerability research, root-cause analysis, AI agent tooling","2026-08-16 02:24:07",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill draw-io",{"tool":37,"command":38},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill draw-io",{"tool":40,"command":41},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill draw-io","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fcreative-design\u002Fdraw-io\u002FSKILL.md",true,[45,51,55,59,65],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"README.md","REFERENCE","参考文档",7854,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fcreative-design\u002Fdraw-io\u002FREADME.md",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Faws-icons.md",28597,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fcreative-design\u002Fdraw-io\u002Freferences\u002Faws-icons.md",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Flayout-guidelines.md",1515,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fcreative-design\u002Fdraw-io\u002Freferences\u002Flayout-guidelines.md",{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"scripts\u002Fconvert-drawio-to-png.sh","SCRIPT","脚本",638,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fcreative-design\u002Fdraw-io\u002Fscripts\u002Fconvert-drawio-to-png.sh",{"path":66,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":67,"sourceHtmlUrl":68},"scripts\u002Ffind_aws_icon.py",2208,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fcreative-design\u002Fdraw-io\u002Fscripts\u002Ffind_aws_icon.py",[70,77,86,93,100,107],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7ARMYTZ5D4B7N5SKFXV345V","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":81,"licenseFileUrl":82,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7ARMX1BVNEAR98SBANMDF2V","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7ARMPR4RQ417MG1HMPGNQHH","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7ARMHBERDMKGDMV7K6MQ6YP","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7ARME0A7KFT330Q2H25HE2B","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7ARM8D87V18WDG0GEZS11ZT","planning-with-files","Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[]]