Initial commit
This commit is contained in:
31
skills/asset-tracking/SKILL.md
Normal file
31
skills/asset-tracking/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
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.
|
||||
|
||||
---
|
||||
31
skills/distribution-checklist/SKILL.md
Normal file
31
skills/distribution-checklist/SKILL.md
Normal file
@@ -0,0 +1,31 @@
|
||||
---
|
||||
name: distribution-checklist
|
||||
description: Use when planning multi-channel publishing, promotions, and measurement
|
||||
for content pillars.
|
||||
---
|
||||
|
||||
# Distribution & Amplification Checklist Skill
|
||||
|
||||
## When to Use
|
||||
- Launching new hero assets or campaigns across multiple channels.
|
||||
- Coordinating owned, earned, and paid amplification efforts.
|
||||
- Auditing distribution readiness before go-live.
|
||||
|
||||
## Framework
|
||||
1. **Channel Readiness** – confirm CMS/social/email templates, personalization, localization plans.
|
||||
2. **Publishing Steps** – detail scheduling, approvals, assets (thumbnails, snippets, UTMs).
|
||||
3. **Amplification** – partner drops, paid boosts, influencer outreach, employee advocacy, enablement kits.
|
||||
4. **Measurement** – define KPIs, UTMs, dashboards, alerting thresholds, reporting cadence.
|
||||
5. **Feedback & Recycling** – plan check-ins for performance review, comments, repurposing opportunities.
|
||||
|
||||
## Templates
|
||||
- Distribution checklist per channel (tasks, owner, due date, status).
|
||||
- Amplification matrix (partner, asset, CTA, logistics).
|
||||
- Reporting sheet linking metrics to assets/UTMs.
|
||||
|
||||
## Tips
|
||||
- Align UTMs + naming conventions before scheduling to keep analytics clean.
|
||||
- Document embargoes and partner requirements to avoid misfires.
|
||||
- Schedule follow-up touchpoints to convert top performers into evergreen assets.
|
||||
|
||||
---
|
||||
30
skills/editorial-calendar/SKILL.md
Normal file
30
skills/editorial-calendar/SKILL.md
Normal file
@@ -0,0 +1,30 @@
|
||||
---
|
||||
name: editorial-calendar
|
||||
description: Use when structuring pillar calendars, approvals, and cadence governance.
|
||||
---
|
||||
|
||||
# Editorial Calendar Systems Skill
|
||||
|
||||
## When to Use
|
||||
- Planning multi-asset campaigns or pillar programs.
|
||||
- Coordinating cross-functional review cycles.
|
||||
- Auditing content backlog, status, and alignment to GTM themes.
|
||||
|
||||
## Framework
|
||||
1. **Cadence** – map publish dates, lead times, and dependencies.
|
||||
2. **Ownership** – assign writers, reviewers, approvers, localization partners.
|
||||
3. **Workflow Stages** – draft → review → design → legal → ready → scheduled → live.
|
||||
4. **Metadata** – persona, stage, CTA, channels, asset type, pillar tag.
|
||||
5. **Governance** – color-coding, status thresholds, reminder automation.
|
||||
|
||||
## Templates
|
||||
- Calendar view (by week) with status tags.
|
||||
- Intake brief + approval checklist.
|
||||
- Monday/Asana/Notion board schema for pipeline tracking.
|
||||
|
||||
## Tips
|
||||
- Keep a backlog column for ideas; groom weekly.
|
||||
- Automate reminders for approvals to shorten cycle time.
|
||||
- Document freeze windows (holidays, launches) to avoid conflicts.
|
||||
|
||||
---
|
||||
Reference in New Issue
Block a user