skills/linkedin-infographic-autopilot/references/tool-usage-policy.md

# Tool usage policy

Autopilot uses a tool only when it can materially improve correctness, evidence quality, artifact quality, or verification for a named job.

## Selection rule

Before a call, state internally what job the tool serves and what result is required. After a call, consume the tool result in the relevant artifact or verification report.

Examples:

- fresh web research for claims whose truth can change
- connected files/apps for user-authorized source material
- code execution for deterministic transforms, validation, rendering, or packaging
- image inspection for actual still/frame critique
- GitHub for community contribution only after explicit consent and the publishing contract passes

## Truthfulness

Never claim a tool was called because the host normally supports it, because a plugin is installed somewhere else, or because the output could have been produced by that tool.

Never claim a build, render, screenshot, search, connector read, write, or publication action without an observed tool result.

If a tool fails, record the failure and either retry once when safe or degrade the execution path.

## App and connector boundaries

- Use connected apps only for the user's task and only when the current host exposes them
- Preserve source boundaries; do not substitute public web search for private connected data when the task depends on private data
- Do not write to external services unless the requested workflow calls for it and the user has supplied the required consent
- Community publishing requires explicit consent even when GitHub is available

## Sandbox and shell

- Prefer the least privilege that completes the job
- Use read-only for evidence and review jobs
- Use workspace-write for build roles that must create artifacts
- Do not request unrestricted execution merely for convenience
- Keep generated work inside the task workspace when possible

## Verification

A successful tool call is evidence of execution, not evidence of quality. Still, motion, evidence, and final verification gates remain mandatory after tool execution.