scouter-actions

Mutating actions in Scouter are executed only on explicit user requests. The Skill enforces explicit consent and uses deterministic CLI commands with guardrails that prevent automatic mutations across lead drafting, pipeline execution, and review workflows.

To generate a draft for a lead, run the generate-draft command with the --lead-id and --wait flags. This routes the request to the Executor model to create a controlled lead draft without automatic mutations.

Yes, you can execute the scoring and enrichment pipeline by running the run-pipeline command. This deterministic CLI command processes the pipeline while enforcing explicit consent and clear model routing.

The review workflow uses review-lead, review-draft, and review-reply commands to approve or finalize content. It routes requests to the Reviewer model, ensuring all mutations across leads, drafts, and replies require explicit user consent.

Yes, explicit consent is required for all mutating actions including pipeline execution and lead drafting. The Skill enforces guardrails that prevent automatic mutations, ensuring deterministic CLI commands only run on direct user requests.

Deterministic CLI commands for Scouter mutations are limited by explicit consent guardrails, meaning they cannot execute automatically. Mutations across lead drafting, pipeline execution, and review workflows strictly require manual user invocation.