---
name: freewheel-creative
description: "Manage FreeWheel creative validation, approval, testing, and lifecycle."
version: 2.0.0
author: Hermes Agent (rebuild)
license: Proprietary site content
platforms: [linux, macos, windows]
metadata:
  hermes:
    tags: [Operations, Routing, Verification]
    related_skills: [change-approval-rollback, credential-pii-safety, ad-operations-incident-response]
---

# FreeWheel Creative Operations

Use this primary skill to route related workflows without loading every detailed procedure. Existing standalone slugs remain compatibility entry points; the references below are the canonical grouped procedures.

## When to Use

- The request spans multiple workflows in this domain.
- The user names a workflow command listed below.
- A consistent approval, failure-handling, and verification contract is needed.

## Safety and Authorization

Default to read-only inspection or sandbox work. Require explicit approval before production changes, campaign mutations, portal actions, billing changes, routing changes, or publishing results. Protect credentials, client data, audience data, financial data, and secrets.

## Command Router

| Workflow | Reference |
|---|---|
| `freewheel-creative-validator` | `references/freewheel-creative-validator.md` |
| `freewheel-vast-validator` | `references/freewheel-vast-validator.md` |
| `freewheel-creative-lifecycle` | `references/freewheel-creative-lifecycle.md` |
| `freewheel-test-automation` | `references/freewheel-test-automation.md` |

## Routing Procedure

1. Identify the requested workflow, target, environment, owner, and expected outcome.
2. Load only the matching reference file unless the request spans multiple workflows.
3. Check prerequisites, authorization, and current state before acting.
4. Follow the reference procedure and preserve evidence.
5. Read back approved changes from the authoritative source.
6. Report status, evidence, assumptions, confidence, approvals, unresolved risks, and next actions.

## Failure Handling

Classify failures as validation, authentication, permission, dependency, timeout, stale-data, platform, or verification failures. Do not retry mutations blindly. Check current state and partial completion before retrying. Escalate material customer, revenue, privacy, launch, or production impact.

## Verification

- Confirm the selected reference exists and every requested workflow was handled.
- Confirm the authoritative source reflects any approved change.
- Confirm relevant delivery, creative, API, incident, or campaign metrics.
- Confirm no unrelated files, accounts, environments, or records were changed.

## Output Contract

Provide the selected workflow, scope, inputs, checks performed, result, evidence, assumptions, confidence, approvals, exceptions, rollback status, and next actions.