[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C4MCGT8VE95H167GW3ZMSM":3,"skill-same:01M6C4MCGT8VE95H167GW3ZMSM":73},{"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":23,"publishedAt":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":14,"repositoryHtmlUrl":40,"repositoryHomepageUrl":6,"ownerHtmlUrl":41,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":42,"install":43,"resources":56},"01M6C4MCGT8VE95H167GW3ZMSM","circuit-json-analysis",null,"Analyzes Circuit JSON files for structural component relationships, domain mappings (source, schematic, pcb, cad), and geometric layout DRC violations (courtyard overlaps, solder paste misalignments, pad clearances). Trigger this skill whenever analyzing a circuit.json file, inspecting PCB placement, or performing design rule checks on Circuit JSON data.","vivekvjnk\u002Fthree-wise-monkeys","vivekvjnk","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F57674825?v=4","01M6C4KWVXPJ0AG14HH8G6R07Y","Vivek Vijayan","01M6C4KX0DKKJ9JGJKMV2K2W54",0,"GPL-2.0","https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fprocesses\u002Fcomponent-placement\u002Fskills\u002Fcircuit-json-analysis\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31],"analysis","json","circuit json analysis","design","component","file","analyzing","data","2026-11-10 10:12:30",false,"---\nname: circuit-json-analysis\ndescription: Analyzes Circuit JSON files for structural component relationships, domain mappings (source, schematic, pcb, cad), and geometric layout DRC violations (courtyard overlaps, solder paste misalignments, pad clearances). Trigger this skill whenever analyzing a circuit.json file, inspecting PCB placement, or performing design rule checks on Circuit JSON data.\n---\n\n# Circuit JSON Analysis Skill\n\nThis skill provides step-by-step guidance and deterministic tooling for inspecting, validating, and performing Design Rule Checks (DRC) on `circuit.json` files.\n\n---\n\n## 1. Operational Knowledge\n\nThe core diagnostic executable for this capability is bundled in the `tools\u002F` directory.\n\n### Running Analysis & DRC\nExecute the automated analysis tool against a target `circuit.json` file:\n\n```bash\npython3 tools\u002Fanalyze_circuit.py path\u002Fto\u002Fcircuit.json\n```\n\nThe tool produces a diagnostic report containing:\n- **Summary**: Element counts by domain prefix (`source_`, `schematic_`, `pcb_`, `cad_`).\n- **Component Mapping**: Inter-domain structural links between `source_component` and `pcb_component`.\n- **Overlap Issues**: Precise bounding-box overlaps in courtyards (`pcb_courtyard_rect`) and solder paste stencil layers (`pcb_solder_paste`).\n- **DRC Warnings & Errors**: Built-in warning\u002Ferror objects contained within the Circuit JSON.\n\n---\n\n## 2. Reasoning Guidance\n\nWhen inspecting or diagnosing Circuit JSON layout artifacts:\n\n### Deep Domain Knowledge Reference\nRefer to `references\u002Fcircuit_json_schema.md` for in-depth structural models, domain prefix definitions (`source_`, `schematic_`, `pcb_`, `cad_`), and foreign key hierarchies.\n\n### Structural Integrity Rules\n1. **Source Domain**: Every logical component MUST have a unique `source_component_id`. Associated `source_port` items reference `source_component_id`.\n2. **PCB Domain**: Every physical footprint (`pcb_component`) MUST link to `source_component_id`. Sub-geometries (`pcb_smtpad`, `pcb_solder_paste`, `pcb_silkscreen_*`, `pcb_courtyard_*`) MUST link to their parent `pcb_component_id`.\n3. **CAD Domain**: 3D models (`cad_component`) MUST reference both `pcb_component_id` and `source_component_id`.\n\n### Diagnostic Decision Flow\n- **Courtyard Overlaps**: Indicates physical collisions between components on the board layout.\n- **Solder Paste Overlaps at Origin `(0,0)`**: Indicates unapplied coordinate transformation matrices (child elements remain at local origin instead of world coordinates).\n- **Unconnected Pins**: Search for `source_pin_missing_trace_warning` objects in the JSON payload.\n\n---\n\n## 3. Workflow Instructions\n\nFollow this standard procedure when working with Circuit JSON:\n\n1. **Step 1: Automated DRC Run**  \n   Run `python3 tools\u002Fanalyze_circuit.py \u003Cpath_to_circuit.json>` to capture immediate layout issues.\n2. **Step 2: Relational Hierarchy Validation**  \n   If errors are reported, consult `references\u002Fcircuit_json_schema.md` to verify missing foreign key references or unlinked components.\n3. **Step 3: Geometry & Clearance Inspection**  \n   Check generated DRC warnings for courtyard overlaps, pad clearance errors, or unmapped `pcb_component` instances.\n\n---\n\n## 4. Verification\n\nAn agent must verify the following criteria to confirm successful execution and validity of a `circuit.json` file:\n\n1. **Zero Courtyard Overlaps**: Confirm `overlap_issues` section in the output of `tools\u002Fanalyze_circuit.py` contains 0 `courtyard_overlap` errors.\n2. **Zero Solder Paste Misalignments**: Confirm no `solder_paste_overlap` errors exist at `(0, 0)`.\n3. **Valid Domain Mappings**: Ensure all `source_component` objects have corresponding `pcb_component` objects assigned.\n4. **Clean DRC Log**: Verify `drc_warnings_errors` list contains no unresolved critical errors.\n","# Circuit JSON Analysis Skill\n\nThis skill provides step-by-step guidance and deterministic tooling for inspecting, validating, and performing Design Rule Checks (DRC) on `circuit.json` files.\n\n---\n\n## 1. Operational Knowledge\n\nThe core diagnostic executable for this capability is bundled in the `tools\u002F` directory.\n\n### Running Analysis & DRC\nExecute the automated analysis tool against a target `circuit.json` file:\n\n```bash\npython3 tools\u002Fanalyze_circuit.py path\u002Fto\u002Fcircuit.json\n```\n\nThe tool produces a diagnostic report containing:\n- **Summary**: Element counts by domain prefix (`source_`, `schematic_`, `pcb_`, `cad_`).\n- **Component Mapping**: Inter-domain structural links between `source_component` and `pcb_component`.\n- **Overlap Issues**: Precise bounding-box overlaps in courtyards (`pcb_courtyard_rect`) and solder paste stencil layers (`pcb_solder_paste`).\n- **DRC Warnings & Errors**: Built-in warning\u002Ferror objects contained within the Circuit JSON.\n\n---\n\n## 2. Reasoning Guidance\n\nWhen inspecting or diagnosing Circuit JSON layout artifacts:\n\n### Deep Domain Knowledge Reference\nRefer to `references\u002Fcircuit_json_schema.md` for in-depth structural models, domain prefix definitions (`source_`, `schematic_`, `pcb_`, `cad_`), and foreign key hierarchies.\n\n### Structural Integrity Rules\n1. **Source Domain**: Every logical component MUST have a unique `source_component_id`. Associated `source_port` items reference `source_component_id`.\n2. **PCB Domain**: Every physical footprint (`pcb_component`) MUST link to `source_component_id`. Sub-geometries (`pcb_smtpad`, `pcb_solder_paste`, `pcb_silkscreen_*`, `pcb_courtyard_*`) MUST link to their parent `pcb_component_id`.\n3. **CAD Domain**: 3D models (`cad_component`) MUST reference both `pcb_component_id` and `source_component_id`.\n\n### Diagnostic Decision Flow\n- **Courtyard Overlaps**: Indicates physical collisions between components on the board layout.\n- **Solder Paste Overlaps at Origin `(0,0)`**: Indicates unapplied coordinate transformation matrices (child elements remain at local origin instead of world coordinates).\n- **Unconnected Pins**: Search for `source_pin_missing_trace_warning` objects in the JSON payload.\n\n---\n\n## 3. Workflow Instructions\n\nFollow this standard procedure when working with Circuit JSON:\n\n1. **Step 1: Automated DRC Run**  \n   Run `python3 tools\u002Fanalyze_circuit.py \u003Cpath_to_circuit.json>` to capture immediate layout issues.\n2. **Step 2: Relational Hierarchy Validation**  \n   If errors are reported, consult `references\u002Fcircuit_json_schema.md` to verify missing foreign key references or unlinked components.\n3. **Step 3: Geometry & Clearance Inspection**  \n   Check generated DRC warnings for courtyard overlaps, pad clearance errors, or unmapped `pcb_component` instances.\n\n---\n\n## 4. Verification\n\nAn agent must verify the following criteria to confirm successful execution and validity of a `circuit.json` file:\n\n1. **Zero Courtyard Overlaps**: Confirm `overlap_issues` section in the output of `tools\u002Fanalyze_circuit.py` contains 0 `courtyard_overlap` errors.\n2. **Zero Solder Paste Misalignments**: Confirm no `solder_paste_overlap` errors exist at `(0, 0)`.\n3. **Valid Domain Mappings**: Ensure all `source_component` objects have corresponding `pcb_component` objects assigned.\n4. **Clean DRC Log**: Verify `drc_warnings_errors` list contains no unresolved critical errors.\n",{"name":5,"description":7},"main","8413773f2869ef1060cdff2a70ff224b4fbb64a1","crazy_orca\u002FVHL\u002Fprocesses\u002Fcomponent-placement\u002Fskills\u002Fcircuit-json-analysis","https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys","https:\u002F\u002Fgithub.com\u002Fvivekvjnk","2026-08-23 20:15:00",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add vivekvjnk\u002Fthree-wise-monkeys --skill circuit-json-analysis",{"tool":49,"command":50},"bunx","bunx skills add vivekvjnk\u002Fthree-wise-monkeys --skill circuit-json-analysis",{"tool":52,"command":53},"pnpm","pnpm dlx skills add vivekvjnk\u002Fthree-wise-monkeys --skill circuit-json-analysis","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fprocesses\u002Fcomponent-placement\u002Fskills\u002Fcircuit-json-analysis\u002FSKILL.md",true,[57,63,67],{"path":58,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":61,"sourceHtmlUrl":62},"manifest.json","REFERENCE","参考文档",112,"https:\u002F\u002Fgithub.com\u002Fmanagedcode\u002Fdotnet-skills\u002Fblob\u002Fmain\u002Fcatalog\u002FPlatform\u002FOfficial-DotNet-Advanced\u002Fskills\u002Fvectorization\u002Fmanifest.json",{"path":64,"resourceType":59,"resourceTypeDesc":60,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fcircuit_json_schema.md",2727,"https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fprocesses\u002Fcomponent-placement\u002Fskills\u002Fcircuit-json-analysis\u002Freferences\u002Fcircuit_json_schema.md",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"tools\u002Fanalyze_circuit.py","SCRIPT","脚本",4791,"https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fprocesses\u002Fcomponent-placement\u002Fskills\u002Fcircuit-json-analysis\u002Ftools\u002Fanalyze_circuit.py",[74,85,98,122,127,134],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":32},"01M6C4MJNVM205XN83K79M9B9M","cypress-tuning","Systematically diagnoses, tunes, and executes Cypress GPU-accelerated PCB placement optimization runs. Trigger when running DREAMPlace\u002FCypress component placement, diagnosing placement divergence or clumping, or tuning wirelength, density, rotation, and net crossing parameters.","https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fprocesses\u002Fcomponent-placement\u002Fskills\u002Fcypress-tuning\u002FSKILL.md",[],[81,82,83,84,28],"cypress tuning","tuning","Optimization","gpu",{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":92,"publishedAt":32},"01M6C4MFEJV3TJBTD6Q72R10SD","circuitjson-bookshelf-converter","Converts Circuit JSON PCB and schematic designs into Bookshelf physical design format (.nodes, .nets, .pl, .scl, .aux) with courtyard keep-out boundary modeling, and back-annotates Cypress placement optimization results back into Circuit JSON. Trigger this skill whenever converting circuit.json files to Bookshelf format or back-annotating .pl \u002F .gp.pl placement outputs into Circuit JSON.","https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fprocesses\u002Fcomponent-placement\u002Fskills\u002Fcircuitjson-bookshelf-converter\u002FSKILL.md",[91],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[93,94,27,95,96,25,97,83],"circuitjson bookshelf converter","converter","results","format","boundary",{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":108,"publishedAt":32},"01M6C4M9D400A6HAVWVYA6S4DW","vhl-concepts","Architectural foundation for Virtual Hardware Laboratory (VHL). Explains the four fundamental VHL concepts (Module vs Assembly, Interface Boundary, Git Worktree Workspace Isolation, and Shared Circuit Understanding Document), why VHL uses them, their core invariants, and when an agent must reason about them. Trigger this skill whenever reasoning about VHL architecture, defining boundaries, identifying module\u002Fassembly scope, or referencing SCUD artifacts.","https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fconcepts\u002FVEC\u002Fskills\u002FVHL_Concepts\u002FSKILL.md",[104,107],{"categoryNo":105,"categoryName":106,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[109,110,111,112,113,114,115,116,117,118,97,119,120,121],"vhl concepts","architecture","reasoning","core","SCUD","assembly","workspace","virtual","git worktree","why","worktree","artifacts","git",{"skillNo":123,"name":113,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":32},"01M6C4M84NXPYJP0MQBK1KCPGR","https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fconcepts\u002FVEC\u002Fskills\u002FSCUD\u002FSKILL.md",[],[113],{"skillNo":128,"name":129,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":32},"01M6C4M74376ZGW7PVHA3A7WZV","Module_Synthesis","https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fconcepts\u002FVEC\u002Fskills\u002FModule_Synthesis\u002FSKILL.md",[],[133],"Module Synthesis",{"skillNo":135,"name":136,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":32},"01M6C4M5QGD7QHY9TZ153VJY6D","Boundary_Reconciliation","https:\u002F\u002Fgithub.com\u002Fvivekvjnk\u002Fthree-wise-monkeys\u002Fblob\u002Fmain\u002Fcrazy_orca\u002FVHL\u002Fconcepts\u002FVEC\u002Fskills\u002FBoundary_Reconciliation\u002FSKILL.md",[],[140,97],"Boundary Reconciliation"]