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

asset-tracking skill

safe

/plugins/content-pipeline-orchestration/skills/asset-tracking

This skill helps teams manage asset metadata, dependencies, and delivery workflows across writers, designers, and localization with centralized tracking.

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

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-tracking
description: Use when managing asset metadata, dependencies, and delivery workflows
  across teams.
---

# Content Asset Tracking Skill

## When to Use
- Coordinating production across writers, designers, video editors, and localization teams.
- Tracking asset dependencies (illustrations, data pulls, interviews) and approvals.
- Preparing handoffs to distribution, enablement, or partner teams.

## Framework
1. **Metadata Schema** – asset ID, pillar, audience, stage, CTA, owner, status, storage link.
2. **Dependency Mapping** – highlight required inputs (stats, quotes, screenshots, product access).
3. **Version Control** – naming conventions, change history, approval timestamps.
4. **Delivery Checklist** – thumbnails, transcripts/captions, localization files, CMS fields.
5. **Analytics Hooks** – UTMs, tracking parameters, reporting sheet references.

## Templates
- Asset tracker spreadsheet/board view.
- Dependency checklist (input, owner, due date, status).
- Delivery package template for distribution + enablement teams.

## Tips
- Centralize assets in shared drives or DAM with consistent naming.
- Automate reminders when dependencies slip or approvals are overdue.
- Tie tracker to distribution calendar to visualize readiness.

---

Overview

This skill helps teams manage asset metadata, dependencies, and delivery workflows for content and creative production. It provides a practical framework and templates to standardize tracking from brief to distribution. Use it to reduce handoff friction and ensure assets are ready for go-to-market channels on time.

How this skill works

The skill defines a lightweight metadata schema (asset ID, pillar, audience, stage, CTA, owner, status, storage link) and enforces dependency mapping so every required input has an owner and due date. It includes version control rules, a delivery checklist, and analytics hooks (UTMs, tracking references) so assets are distribution-ready. Templates for trackers, dependency checklists, and delivery packages speed adoption across teams.

When to use it

Coordinating multi-role production (writers, designers, video, localization) on a single asset
Tracking and enforcing dependencies like data pulls, interviews, or design inputs
Managing approvals and version history across stakeholders
Preparing handoffs to distribution, enablement, or partner teams
Visualizing readiness alongside the distribution calendar

Best practices

Centralize final assets in a shared drive or DAM and apply consistent naming conventions
Use the metadata schema on every asset to make filtering and reporting reliable
Map each dependency to a single owner with clear due dates and automated reminders
Capture approval timestamps and change history for auditability
Tie tracker status to the distribution calendar so readiness is visible to downstream teams

Example use cases

Running a blog post production pipeline that includes research, design, SEO, and localization
Coordinating a product launch asset pack (press kit, demo video, thumbnails, captions) for partners
Tracking video production dependencies like b-roll, transcripts, and approval sign-offs
Packaging assets for enablement with CMS fields, tracking UTMs, and distribution checklists

FAQ

Can this skill handle multiple formats and languages?

Yes. Use the metadata schema to record format and language, and include localization files in the delivery checklist.

How do I surface overdue dependencies?

Set automated reminders and status flags in the tracker; filter for overdue items and notify owners and stakeholders.