What problem does it solve? Adding a new command to a BSP-registered 1C external data processor requires editing ExternalDataProcessorInfo() with the correct command type, presentation, and identifier, plus writing matching ExecuteCommand or Print handlers — a repetitive, error-prone task done by hand. ## Core Features & Use Cases - Command Registration: Inserts a new command block into ExternalDataProcessorInfo() before the Return statement, with correct NStr presentation, ID, and command type. - Automatic Type Mapping: Maps free-form user input (e.g. "open form", "on server") to the proper BSP CommandType function, or infers the default from the processor kind (PrintForm, ObjectFilling, AdditionalReport, etc.). - Handler Generation: Creates or extends ExecuteCommand (server/client) and Print procedures in the object module or form module, adding ElsIf branches when handlers already exist. - Use Case: You have a print form data processor registered via BSP and need a second print command — the skill adds the command registration, the Print branch, and the Generate function stub with correct PrintManagement API calls. ## Quick Start Ask the assistant to add a new command named "FillData" of type "server method" to the MyProcessor data processor using the 1c-bsp-command skill.
