What problem does it solve? Registering an external data processor or report in the 1C SSL (BSP) "Additional Reports and Data Processors" subsystem requires a correctly structured ExternalDataProcessorInfo function with the right kind, command type, purpose objects, and server handlers. Writing this boilerplate by hand is error-prone, since each processor kind (print form, object filling, additional report, etc.) demands different API calls and conditional sections. ## Core Features & Use Cases - Kind-aware code generation: Maps free-form user input (e.g., "print form", "filling") to the correct BSP API methods such as ProcessorKindPrintForm() and CommandTypeServerMethodCall(). - Conditional template sections: Automatically includes Purpose entries for assignable kinds and the PrintMXL modifier for print forms, omitting them for global processors. - Server handler scaffolding: Adds the matching ExecuteCommand or Print export procedure when the command type requires a server method call. - Use Case: You need to register MyProcessor as a print form for Document.SalesInvoice. The skill locates src/MyProcessor/Ext/ObjectModule.bsl, inserts ExternalDataProcessorInfo with the correct kind, purpose, and modifier, plus the Print handler procedure, all inside the PublicInterface region. ## Quick Start Ask the assistant to register your external data processor with the BSP subsystem, for example: register MyProcessor as a print form for Document.SalesInvoice.
