home / skills / gtmagents / gtm-agents / asset-approval

asset-approval skill

safe

/plugins/partner-co-marketing-orchestration/skills/asset-approval

This skill helps manage co-marketing asset reviews with traceable evidence, SLAs, and sign-off logging to prevent delays.

npx playbooks add skill gtmagents/gtm-agents --skill asset-approval

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

1.3 KB

---
name: asset-approval
description: Use to manage co-marketing asset reviews with traceable evidence and
  SLAs.
---

# Asset Approval Workflow Skill

## When to Use
- Coordinating creative reviews across multiple partner stakeholders.
- Auditing compliance for regulated industries.
- Preventing go-live delays caused by unclear feedback loops.

## Framework
1. **Review Matrix** – define reviewers per asset type (brand, legal, product, regional) and required evidence.
2. **SLA Cadence** – set response times, reminder schedule, and escalation triggers.
3. **Feedback Channels** – standardize annotation tools, version naming, and acceptance criteria.
4. **Sign-off Logging** – capture final approvals with timestamps, approver names, and file hashes.
5. **Change Control** – document post-approval edits, expiration dates, and refresh plans.

## Templates
- Approval tracker (asset → reviewer → status → notes → evidence link).
- SLA chart outlining response times by priority level.
- Change request form for post-approval edits.

## Tips
- Use shared storage with permissions per partner to prevent accidental edits.
- Pair with `co-branding` skill to auto-check brand compliance before review.
- Automate reminders via project tools to keep cross-company teams on schedule.

---

Overview

This skill manages co-marketing asset reviews with traceable evidence and configurable SLAs. It centralizes reviewer assignments, captures sign-off metadata, and enforces response cadences to prevent go-live delays. The workflow supports audit-ready logs, version control, and post-approval change tracking for regulated and partner-facing campaigns.

How this skill works

Define a review matrix that maps asset types to required reviewers and evidence. Configure SLA cadences for response times, reminders, and escalation rules, and standardize feedback channels and version naming. The skill logs final approvals with timestamps, approver identities, and file hashes, and records change requests and expiration/refresh rules for approved assets.

When to use it

Coordinating creative reviews across multiple internal and partner stakeholders
Auditing compliance and maintaining an evidence trail for regulated industries
Preventing go-live delays caused by unclear feedback loops or missing approvals
Managing cross-regional or multi-brand reviews with different reviewer sets
Tracking post-approval edits and expiration or refresh cycles for assets

Best practices

Create a clear review matrix up front that lists required reviewers by asset type and region
Set realistic SLA tiers (e.g., 24h for high priority, 72h for routine) and automate reminders
Use standardized annotation tools and version naming to avoid ambiguity during reviews
Store assets in shared, permissioned storage to prevent accidental overwrites
Log sign-offs with timestamps and file hashes to create an audit-ready evidence trail

Example use cases

A co-branded campaign where legal, brand, and partner reps must approve creative before launch
A regulated product update requiring documented approvals and time-stamped evidence for audit
Coordinating localized asset reviews across regional marketing teams with staggered SLAs
Automating reminders and escalations to reduce time-to-approval and avoid launch slippage
Managing post-approval change requests and tracking asset expiration for scheduled refreshes

FAQ

Can SLAs be customized per partner or region?

Yes. SLAs are configurable by priority, partner, and region so you can enforce different response times and escalation rules.

How does the skill ensure auditability?

All approvals are logged with approver name, timestamp, and file hashes. Change requests and version history are recorded to maintain an auditable trail.