Artifacts

Use this Skill after the desired durable-output outcome is known. For generic Recipe execution, Runs, persistence, or diagnosis, follow actors; this Skill only selects artifact behavior.

Choose the outcome

Prefer bundle when both durable content and inventory evidence are required. Prefer write for one accepted file. Use report while content still needs review. Do not use file-write as a content generator. If one selected outcome should become a recurring named tool, use the persistent-capability workflow in actors; do not copy its graph.

Inputs and boundaries

• Keep input bounded and evidence-based; choose the current model explicitly where the Recipe requires model.
• Supply caller-owned artifact_path and, for bundle, a distinct manifest_path.
• write_mode=create is the safe default and stops if the target exists. Use overwrite or append only when the requested mutation is explicit.
• Parent directories are created by the writer. ~ is resolved for artifact paths.
• manifest reports existence, size, and modification evidence; it does not validate artifact meaning.
• Validation in bundle runs only when run_validation=true and uses the caller-supplied trusted command and scope.

Stop rules

Stop rather than guessing when the target path, overwrite policy, accepted content, model, or validation command is unclear. Do not claim a durable artifact from report or manifest alone. After a Run starts, use the actors evidence and lifecycle protocol; this Skill does not redefine it.