agentleFS
Eugenevdm01Eugenevdm01/eugenes-meta-agent/skills/weekly-content-operator/SKILL.md

weekly-content-operator

Skill4 starsChanged 6 months agoMITView on GitHub

Fully automated weekly content generation system for Funnel Junkies (B2C), VAN Studios (B2B), and ecomm_adventures (Brand). Use when the user asks to generate the weekly content pack, run the content automation, update the content schedule, or modify the content generation logic. Pulls live config from the Content Command Centre dashboard (channels, brand voice, post type mix, CTAs, events, specials, influencers, research sources) and produces copy, video scripts, AI images, Google Drive delivery, and VanX Funnels social planner scheduling.

  • Reads credentials

The file

Show its rules and text

We split this skill into the rules it gives an agent

15 rules. About 0 are common, 6 are distinctive, and 9 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 9

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the full integration guide: /home/ubuntu/skills/weekly-content-operator/references/dashboard-config-integration.md

    line 42
  2. Distinctive:

    If the dashboard API is unreachable, fall back to hardcoded defaults (see script).

    line 56
  3. Distinctive:

    Default research sources (if dashboard unavailable):

    line 62
  4. Very specific:

    Read the copy generation patterns before writing any posts: …

    line 72
  5. Very specific:

    Read the content mix calculator to determine how many posts of each type: …

    line 75
  6. Very specific:

    Use the post type distribution from postTypeConfig table

    line 82
  7. Distinctive:

    Every post must have: hook, caption, CTA (matching dashboard CTA config), hashtags, image prompt

    line 83
  8. Very specific:

    Use map tool to generate all posts in parallel (split by brand, 3 parallel subtasks).

    line 85
  9. Very specific:

    Read the image generation guide: /home/ubuntu/skills/weekly-content-operator/references/image-generation-guide.md

    line 89
  10. Distinctive:

    Use brand colour palettes from the guide

    line 93
  11. Very specific:

    Use the image_prompt field generated in Step 3

    line 94
  12. Distinctive:

    Write markdown files per brand:

    line 100
  13. Very specific:

    Use gws CLI. Root folder ID: 1mp3KlETTyr-pO88X_4oRxKSfVwLErGJd

    line 118
  14. Very specific:

    Read the gws best practices skill before using gws CLI: /home/ubuntu/skills/gws-best-practices/SKILL.md

    line 120
  15. Distinctive:

    If GHL API is unavailable or key is not set, save posts as drafts and notify the user.

    line 149

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Weekly Content Operator

What This Skill Does

Generates a complete week of social media content across all active channels for all three brands. The output is a structured content pack delivered to Google Drive and scheduled into VanX Funnels (GHL) Social Planner.

Output per run:

  • 20 B2C posts (Funnel Junkies — Facebook + Instagram)
  • 20 B2B posts (VAN Studios — Facebook + LinkedIn)
  • 5 Brand posts (ecomm_adventures — Instagram)
  • 40+ AI-generated images (8 rotating layout styles)
  • Reel/video scripts for video posts
  • Google Drive folder with all assets (public link)
  • VanX Funnels social planner entries (scheduled or draft)
  • Automation log entry posted to the dashboard

Quick Start — Run the Weekly Automation

python3 /home/ubuntu/skills/weekly-content-operator/scripts/weekly_automation.py

The script outputs Google Drive folder links on completion. Deliver these to the user.


Workflow Overview

The weekly automation follows 9 steps in order. Each step is described below with the key decision points.

Step 1: Fetch Dashboard Config

Always start here. Pull live config from the Content Command Centre before generating anything.

Read the full integration guide: /home/ubuntu/skills/weekly-content-operator/references/dashboard-config-integration.md

Key config pulled:

  • Enabled channels + post/story counts per channel
  • Brand voice per brand (tone, keywords, avoid words, audience, offer, UVP)
  • Post type distribution per brand
  • Active CTAs per brand and platform
  • Active events/promotions (within lead-time window)
  • Active day-of-week specials
  • Active influencers (for inspiration context in prompts)
  • Enabled research sources (RSS/Reddit feeds)
  • Global settings (schedule, language, hashtag strategy, AI creativity level)

If the dashboard API is unreachable, fall back to hardcoded defaults (see script).

Step 2: Research Trending Topics

Pull from enabled research sources in the dashboard config. Use RSS feeds and Reddit sources.

Default research sources (if dashboard unavailable):

  • RSS: TechCrunch AI, VentureBeat AI, Entrepreneur, Forbes Entrepreneurs, Inc.com, HubSpot Blog, Neil Patel, Social Media Examiner, Affiliate Marketing Blog
  • Reddit: r/affiliatemarketing, r/digitalnomad, r/entrepreneur, r/Entrepreneur

Extract 5 B2C trends and 5 B2B trends. Each trend = headline + brief summary.

Design theme rotation: Vary the visual theme each week. Track the last theme used and rotate to the next. Themes: Tech/AI, Lifestyle/Freedom, Results/Proof, Education/Framework, Community/Social.

Step 3: Generate Copy

Read the copy generation patterns before writing any posts: /home/ubuntu/skills/weekly-content-operator/references/copy-generation-patterns.md

Read the content mix calculator to determine how many posts of each type: /home/ubuntu/skills/weekly-content-operator/references/content-mix-calculator.md

Key rules:

  • Build the system prompt from dashboard brand voice config (not hardcoded)
  • Inject active events/specials into the last N posts per brand
  • Include influencer handles as inspiration context (not to copy — to draw style from)
  • Use the post type distribution from postTypeConfig table
  • Every post must have: hook, caption, CTA (matching dashboard CTA config), hashtags, image prompt

Use map tool to generate all posts in parallel (split by brand, 3 parallel subtasks).

Step 4: Generate AI Images

Read the image generation guide: /home/ubuntu/skills/weekly-content-operator/references/image-generation-guide.md

  • Rotate through 8 layout styles (cycle by post index mod 8)
  • Use brand colour palettes from the guide
  • Use the image_prompt field generated in Step 3
  • Generate in parallel using map tool (batches of 10)
  • Name files: {brand}_week{XX}_{type}_{seq}.jpg

Step 5: Save Content Files

Write markdown files per brand:

  • b2c_content.md — all B2C posts with copy, CTAs, hashtags, image filenames
  • b2b_content.md — all B2B posts
  • ig_content.md — all Brand/IG posts

Format each post as:

## Post B2C_001 — Educational — Facebook
**Publish:** 2026-05-04 09:00
**Hook:** [hook text]
**Caption:** [full caption]
**CTA:** [cta text] → [url]
**Hashtags:** #tag1 #tag2 ...
**Image:** b2c_week18_educational_001.jpg

Step 6: Create Google Drive Folders

Use gws CLI. Root folder ID: 1mp3KlETTyr-pO88X_4oRxKSfVwLErGJd

Read the gws best practices skill before using gws CLI: /home/ubuntu/skills/gws-best-practices/SKILL.md

Folder structure:

Funnel Junkies (root)
└── Week {XX} — {Month} {Year}
    ├── B2C — Funnel Junkies
    │   └── Images/
    ├── B2B — VAN Studios
    │   └── Images/
    └── Brand — ecomm_adventures
        └── Images/

Step 7: Upload Assets

Upload markdown content files and all generated images to their respective Drive folders. Set public sharing on the week folder after upload.

Step 8: Schedule in VanX Funnels (GHL)

Post to GHL Social Planner via the GHL API. Distribute posts evenly across Monday–Friday of the target week.

GHL Social Planner endpoint:

POST https://services.leadconnectorhq.com/social-media-posting/posts
Authorization: Bearer {GHL_API_KEY}

If GHL API is unavailable or key is not set, save posts as drafts and notify the user.

Step 9: Log the Run

POST to the dashboard automation log endpoint:

POST {DASHBOARD_URL}/api/trpc/scheduled.logRun
Cookie: app_session_id={SCHEDULED_TASK_COOKIE}
Body: {"json": {"status": "success", "totalPosts": 45, "channelsProcessed": 5, "notes": "Week {XX} complete"}}

Scheduled Task Setup

The automation runs every Sunday at 10:00 AM to prepare content for the coming week.

Schedule tool config:

type: cron
cron: 0 0 10 * * 0   (Sunday 10am)
repeat: true
name: Weekly Content Generator

Scheduled task prompt must include:

  • Instruction to run python3 /home/ubuntu/skills/weekly-content-operator/scripts/weekly_automation.py
  • Dashboard URL for config fetching
  • Google Drive root folder ID
  • GHL API key env var name
  • Dashboard URL for logging the run

Modifying Content Logic

What to changeWhere to change it
Post counts per channelContent Command Centre → Channel Routing
Content mix (post types)Content Command Centre → Post Type Config
Brand voice, tone, keywordsContent Command Centre → Brand Voice
CTAs and destination URLsContent Command Centre → CTA Config
Active promotionsContent Command Centre → Events Calendar
Day-of-week specialsContent Command Centre → Specials & Promos
Research sourcesContent Command Centre → Research Sources
Influencer inspirationContent Command Centre → Influencer Tracker
Image layout stylesreferences/image-generation-guide.md → Layout Styles
Copy prompt structurereferences/copy-generation-patterns.md
Dashboard API integrationreferences/dashboard-config-integration.md

Never hardcode brand voice, CTAs, or post counts in the script. Always pull from the dashboard.


Bundled Resources

  • scripts/weekly_automation.py — Core execution engine (research, generation, Drive upload, GHL scheduling)
  • references/dashboard-config-integration.md — How to fetch and use live dashboard config
  • references/content-mix-calculator.md — Post count distribution and scheduling logic
  • references/copy-generation-patterns.md — LLM prompts per post type, hook formulas, quality checklist
  • references/image-generation-guide.md — Layout styles, brand palettes, image prompt templates

Common Issues

IssueFix
Dashboard API returns 401Check SCHEDULED_TASK_COOKIE env var is set; ensure app is deployed
GHL Social Planner returns 422Check location ID is set in Content Settings; verify post format
Image generation failsRetry once; if still failing, skip and note in log
Google Drive upload failsCheck gws CLI is authenticated; re-run gws auth if needed
RSS feeds return emptyFeeds may be rate-limited; fall back to search-based research
Week folder already existsCheck for existing folder before creating; append timestamp if duplicate

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.