← Solder ComponentsCONTENT HISTORY

Update to Solder Components

Snapshot Nov 13, 2026 · 00:10 UTC · version 0.1.3

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Solder Components and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Answer engineering questions about an exact electronic component using Solder's component expert, including pin connections, operating limits, supporting parts, and reference circuits. Use when component selection or integration needs datasheet and reference evidence.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 249
    }
  ],
  "name": "component-expert",
  "skill_md_contents": "---\nname: component-expert\ndescription: Answer engineering questions about an exact electronic component using Solder's component expert, including pin connections, operating limits, supporting parts, and reference circuits. Use when component selection or integration needs datasheet and reference evidence.\n---\n\nUse this plugin's `component_expert` tool. Explicit user requirements take priority over the workflow below.\n\nThe expert requires an exact public LCSC `productCode` such as `C12345`; that example is a format, not a part recommendation. If the user supplies a manufacturer part number or a family name, resolve it through `component_search` first. Preserve variant and package identity. When multiple variants differ in a way that affects the answer, establish which one the user means.\n\nPass the exact product code and a focused `query` containing the user's relevant operating conditions. Calls are stateless: include the facts needed for a follow-up instead of inventing a conversation or session identifier. Do not send local paths, private-library IDs, arbitrary PDF URLs, or unrelated conversation history.\n\nExplain the returned answer in the context of the user's question. Keep datasheet source links unchanged and immediately next to the claims they support. Distinguish absolute maximum ratings from recommended operating conditions, and distinguish verified facts from suggestions or unresolved limitations. Missing evidence is not proof of suitability.\n\nTreat `isError`, cancellation, and timeout as unsuccessful work. Report the limitation instead of turning an error into an engineering answer. Do not silently substitute the legacy `datasheet_query` tool for the full component expert.\n"
}

SHA-256 of public snapshot: 4c6053b929533d4c924e7b2c24c2bf9e3d8d541c5bd3da74384d1f4e90f0ea19