Update to PartsPlan

{
  "description": "Read electronic-component datasheets with PartsPlan — find the manufacturer's document for a part number, go straight to the page that holds the answer, and read the printed source (text, table images, graph values). Use for ratings, pinouts, package drawings, graphs, register maps, comparison rubrics and BOM checks.",
  "included_files": [],
  "name": "get-started",
  "skill_md_contents": "---\nname: get-started\ndescription: Read electronic-component datasheets with PartsPlan — find the manufacturer's document for a part number, go straight to the page that holds the answer, and read the printed source (text, table images, graph values). Use for ratings, pinouts, package drawings, graphs, register maps, comparison rubrics and BOM checks.\n---\n\n# PartsPlan datasheets\n\nPartsPlan holds archived electronic-component datasheets and shows where each section, table and figure sits in a document. It returns locations and the printed source; the engineering judgement stays with the conversation.\n\n## Connect\nSign in with a PartsPlan account when ChatGPT asks (Google or email). Daily and monthly call limits depend on the account; when a limit is reached the tool says so and when it resets.\n\n## Setting up\nWhen the user asks to set up PartsPlan or get started, make one read-only lookup to confirm the connection: `find_datasheet` for a part the user mentioned, otherwise a common part such as TPS563200 (Texas Instruments). Show what it returned — the manufacturer document and, when the response gives one, a page to read first; do not state a page the response did not give. Then suggest a few things to ask: a value with its page, a pinout, a BOM check, or comparing candidates. Do not call `request_datasheet_collection` or `report_problem` while setting up.\n\n## The basic path (one part, one question)\n1. `find_datasheet(mpn, brand)` — the document of the requested manufacturer comes first (`requested_maker_document`); other manufacturers' documents for the same part number are listed separately and describe other parts.\n2. `get_datasheet_map(doc_sha256, kind=...)` — jump to the section: `abs_max`, `elec_char`, `rec_op`, `thermal`, `pinmap`, `package`, `land_pattern`, `figure`, `app_circuit`, `ordering` …\n3. Read the page:\n   - text: `get_page_blocks(doc_sha256, page)`\n   - tables: the page image is the reference — table blocks come with a `table_image_requests` entry for `get_page_image`\n   - graphs: `get_figure_data` (numbers only when they can be read with certainty) or `get_page_image` for the figure region\n4. Cite `doc_sha256` + page for every number used.\n\n`search_datasheet(doc_sha256, q=[...], mode=\"context\")` finds terms, conditions and footnotes inside one document when the map is not enough.\n\n## Other paths\n- BOM: `check_bom` reports per line whether that manufacturer's datasheet is in the archive and readable; `request_datasheet_collection` queues missing lines when the user wants them collected.\n- Comparing candidates: `compare_points(source, candidates, device)` (39 device types — `device` lists them) returns an adjustable default rubric — hard lines, weighted items summing to 100 and checks — with the datasheet pages to read for each item and part. The candidates are the ones the conversation chose; `scenario`, `purpose`, `exclude_groups`, `exclude_items`, `relax_items` and `weights` adjust the rubric and `applied` records each change. It gives no scores, rankings or compatibility verdicts, and a located page does not establish which variant or package a table applies to.\n- Candidate parts: `search_parts` by description, device type or manufacturer.\n- Reference circuits: `reference_circuits(mpn)` gives application-circuit pages in the manufacturer's datasheet, and `related_documents` lists the manufacturer's reference designs and user guides that print that exact part number (documents to read — a printed part number does not establish that a design uses or suits the part).\n- A wrong answer: `report_problem` with the document, page and block.\n\n## What the answers mean\n- A value always comes with the document and page it was read from; missing values are not estimated.\n- Absence (`no_document`) covers the PartsPlan archive only. A web search or the manufacturer's site can still answer — say which parts of an answer came from outside PartsPlan.\n- `text_source=ocr` text is a reading of an image; confirm numbers on the page image.\n- PartsPlan has no stock, price or lead-time data and does not validate circuits.\n"
}