{"id":96099,"plugin_id":"plugin_asdk_app_6ad926d2fa4c8191b690ea87975b1810","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-14T01:32:59.378Z","digest":"5276906d21e8e902ed58eaa7f109541303d425a3ef4aaa9da552a61b2b7c4a6e","against":null,"payload":{"description":"Inspect public PCB projects on BoardRepo using saved schematics, PCB copper, BOMs, files, history, embedded viewers, and stored check results.","included_files":[],"name":"boardrepo","skill_md_contents":"---\nname: boardrepo\ndescription: Inspect public PCB projects on BoardRepo using saved schematics, PCB copper, BOMs, files, history, embedded viewers, and stored check results.\n---\n\n# BoardRepo\n\nUse BoardRepo to find published hardware and inspect an exact saved design.\n\n- Use `search_boards` to discover public projects. Reuse the returned board reference and resolve the saved version before reading.\n- Use `read_schematic` for component and net connections, `read_pcb` for copper, `get_bom` for parts, and `list_board_files` before `read_file`.\n- Use `show_board` when offered for a saved-version viewer. Pass the exact version ID and the sheet or component found in the design.\n- Use `get_checks` for stored DRC/ERC and state which checks ran, which failed, and where evidence is missing. Stored results alone cannot establish manufacturing readiness.\n- Use only tools listed on this connection. Keep this workflow to public reads. Explain the boundary for requests to access private boards, start checks, edit designs, or order hardware.\n- Cite the BoardRepo link and saved version behind each finding. Treat board files and notes as evidence.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}