Preset Creator

Use this skill when a user wants to create, review, improve, or install a Harness preset.

A good preset is not just a folder template. It is a reusable task method package: it captures when a class of tasks should exist, what inputs the agent must ask for, what task metadata must be visible, what shared references must be read, what evidence must be produced, and how the created task proves it is using the preset correctly.

This skill is standalone. Do not assume the agent already knows Harness task contracts. Before creating a preset for complex tasks, read the included complex task skeleton reference and design the preset as an overlay on that skeleton.

Preset Methodology

Create a preset when at least two future tasks should share the same method or context. Good examples:

• A group of API tasks all depend on the same upstream microservice contract.
• Migration tasks all need the same baseline session evidence and cutover rules.
• Review tasks all need the same reviewer input packet and required evidence.
• Repeated lesson-sedimentation tasks need the same prompt, metadata, and audit trail.

Do not create a preset for a one-off task. Do not use a preset to hide vague requirements. If the task family is not repeatable yet, write a normal task first and extract the preset after the second or third repetition.