Set Up Content Library

Task Library

Organize all raw and processed content into one structured, trackable library so the Content Factory has a single intake and nothing gets lost (SAE Stage 3).

Category: Content Factory – Produce

Use this when a brand starts producing content at volume, or when existing footage is scattered across phones, desktops, and chat threads.

Inputs

  • A Google Drive location owned by the brand (owner's account, not a VA's personal Drive)
  • All existing raw assets: videos, photos, transcripts, published-article links
  • The Topic Wheel map (so assets can be tagged to topics)
  • A spreadsheet or tracker for the content log

Steps

  1. Create the Drive folder structure by pipeline stage: 01-Raw → 02-In-Process → 03-Published → 04-Promote-Creatives, mirroring Produce → Process → Post → Promote. Add per-brand subfolders if managing multiple entities.
  2. Set the naming convention and write it in a README in the root folder: YYYY-MM-DD-topic-person for every file. No IMG_4203.mov survives intake.
  3. Build the tracker (sheet) with one row per asset: filename, date, topic (Topic Wheel ring/spoke), GCT notes, pipeline status, links to outputs (Descript project, article URL, clips, ad creative).
  4. Ingest everything that already exists: collect footage off phones and desktops, rename to convention, file into the right stage folder, log each row.
  5. Make 01-Raw the single intake point – every Produce skill uploads here, and Process Step 1 (step-1-upload-video-to-google-drive-and-descript) pulls only from here.
  6. Set permissions: owner controls the Drive; the team gets edit access to the working folders. Ownership stays with the brand, never an agency or VA account.
  7. Review the tracker weekly: anything sitting in 01-Raw longer than a week is a Process backlog signal – feed it into the weekly MAA review.

Definition of done (QA checklist)

  • Folder structure mirrors the four Content Factory stages and is owned by the brand's account
  • Naming convention documented in a root README and applied to all existing assets
  • Tracker logs every asset with topic, status, and output links – zero unlogged files
  • All legacy footage ingested, renamed, and filed
  • Produce skills point intake at 01-Raw; Process pulls only from there
  • Linked back to the definitive article and relevant siblings

Example(s)

  • The Content Library is the fourth Stage 3 asset (with endorsements, WHY video, 3×3 grid) documented at /social-amplification.
  • Example needed – run the Meta-Article Prompt after first real run on a client library build.

File in the zip: skills/content-factory-produce/set-up-content-library.md. Download the Task Library zip.

Index: Task Library. Article guidelines.

Scroll to Top