Make .SchLib parameter updation first-class (schlib_write.py): standalone trigger + workflow note

SKILL.md

@@ -11,11 +11,15 @@ description: >-
   Library/Footprint columns, assembles a part folder (xlsx, datasheet, symbol, footprint) and
   pushes it to the library repo under its Class. Can also UPDATE a part already in the library
   (revise its values, symbol, footprint, or datasheet) instead of hard-stopping on a duplicate.
-  Every Description it writes follows Vecmocon's strict Altium Description Format. Use WHENEVER
-  the user uploads a component datasheet, builds a library entry, adds a parameter to a type
-  template, updates/revises/corrects an existing part, or pushes a part to Gitea. ALWAYS trigger
-  on "\datasheet", "\library", or "\library-manager", or any component-library /
-  datasheet-extraction / library-update task.
+  Can also WRITE Vecmocon's mandatory SOP parameters directly into an Altium symbol (.SchLib)
+  file - filling Value, Manufacturer, Manufacturer Part, Process, Operating Temperature,
+  Tolerance, RoHS, Datasheet, etc. and removing the Ultra-Librarian default params - via a
+  pure-Python OLE rewrite. Every Description it writes follows Vecmocon's strict Altium
+  Description Format. Use WHENEVER the user uploads a component datasheet, builds a library
+  entry, adds a parameter to a type template, updates/revises/corrects an existing part, wants
+  to fill/write/update parameters in a .SchLib symbol file, or pushes a part to Gitea. ALWAYS
+  trigger on "\datasheet", "\library", "\library-manager", or "\schlib", or any
+  component-library / datasheet-extraction / library-update / schlib-parameter task.
 ---
 
 # Library Manager
@@ -320,6 +324,11 @@ Temperature`, `ROHS`, `Datasheet`, `Process`, `Vecmocon Part Code`, and the two
 fields — with the **Comment** set to the MPN. The skill can stamp these onto the symbol from
 the datasheet.
 
+This runs **as its own task too**, not only inside new-part creation: whenever the user hands
+over one or more `.SchLib` files and wants their parameters filled/updated (e.g. "\schlib", "add
+these parameters to this symbol", "update the schlib"), read the datasheet/specs for each part,
+build its `params.json`, and run `scripts/schlib_write.py` per file — same steps as below.
+
 The skill writes these **directly into the `.SchLib` in pure Python** with
 `scripts/schlib_write.py` (it rebuilds the OLE around the enlarged `Data` stream, preserving
 every other byte, and strips the Ultra-Librarian `Manufacturer_Name` / `Manufacturer_Part_Number`