execute-approved-actions

Automating approved external actions requires placing a formatted approval file in the /Approved folder. The system validates the request, routes it to the correct MCP server (email, LinkedIn, or browser), executes the task, and logs the result to the audit log.

Human-in-the-loop approval routing works by reading approval_request files from the /Approved directory. The skill validates the parameters, selects the correct MCP server for the task, and executes the browser automation or email action deterministically.

Yes, you can execute approved actions on LinkedIn. The skill routes validated approval requests to the appropriate MCP server, including LinkedIn, email, and browser automation, then updates the file destination and system state upon completion.

When an approval request expires or fails validation, the skill handles the error and moves the file to the /Rejected/ directory. Proper error handling and recovery ensure the system state and audit log accurately reflect the rejected execution.

No, manual audit logging configuration is not needed. The skill automatically logs every execution to the mandatory audit log while updating the approval and plan statuses, ensuring all automated email and browser actions are securely recorded.

You trigger execution by placing a properly formatted approval file in the /Approved folder. On the next orchestrator cycle, the system automatically validates the request, executes the action via the configured MCP server, and moves the file to /Done/ or /Rejected/.