tools-script-executor

Centralized script execution uses a single Python proxy entry point to invoke targeted scripts with notation like bundle:skill:script, ensuring consistent environments, standardized error handling, and traceable logging across bundle boundaries.

You run a marketplace script by executing the Python proxy and passing notation plus subcommand, such as python3 .plan/execute-script.py plan-marshall:manage-files:manage-files add --plan-id my-plan to invoke the targeted script.

Yes, notation-based invocation supports plan-aware workflows by mapping notation to script paths and handling plan context, allowing you to execute scripts across different bundles using the single proxy entry point.

Script execution logging generates both plan-scoped and global logs with trace-plan-id support, capturing results for auditing and ensuring consistent traceability across all marketplace script executions.

Yes, the script execution proxy is extensible via scripts/ and references/ directories, allowing you to add support for build, document, and reference operations while maintaining centralized execution and logging.

Using a single proxy entry point ensures deterministic behavior, standardized environments, and consistent error handling across all marketplace scripts, eliminating environment inconsistencies and fragmented execution paths.