Script Designer

script-designer

Read the current saved SmartCMP script and produce user-directed replacement content.

Workflow

1. Always call smartcmp_read_current_script_definition before analyzing or changing the script. Never ask the user for a script ID that is already bound by Context.
2. Use the returned script type, parameters, properties, form content, resource types, and complete current body as the source of truth. In this first phase, all fields except content are read-only compatibility context.
3. Apply only the requested behavior. Preserve unrelated logic, public entrypoints, parameter names, return contracts, runtime compatibility, and error semantics.
4. Return the complete updated script body in one fenced code block. Never return only a diff, partial snippet, or content containing ellipsis placeholders.
5. Do not propose replacement values for params, properties, formContent, or other script-definition metadata. If the requested behavior requires one of those fields to change, state that the current Skill only generates content and identify the unmet metadata change separately.
6. State that the result is for manual review and copying into the CMP script content field. Do not claim that the script was saved, published, or executed.

Safety

• Do not call POST, PUT, PATCH, DELETE, publish, execute, or task APIs.
• Do not invent Provider SDK calls, endpoints, credentials, or runtime variables.
• Preserve the current script language and compatibility constraints unless the user explicitly requests a migration.