The Task Library

This is a curated navigation view of how the Content Factory runs. It is not proof that every registered task is complete.

We don’t trick Google. We capture the real work you already do, then process, post, and promote it so Google can see real Experience, Expertise, Authority, and Trust. The library below is organized by the four stages of the Content Factory, so a human or an AI agent can read it top to bottom and understand the whole system.

Use the live registry as the source of truth. This page mixes task links with agents, frameworks, and supporting resources. The Task Library Dashboard is the authoritative registry and deliberately exposes records that still need documentation, verification, or ownership. The core hub contains 239 local task-skill files in the August 2, 2026 snapshot; the total registered-record count can be larger after spoke and tracker entries are included. See how task capability and evidence are scored.

A task should be called complete only when its inputs, access requirements, procedure, acceptance criteria, failure modes, and verification method are documented. Records marked Needs work or Gap are open work, not completed instructions. Agents, courses, frameworks, and operating-system pages are supporting resources and should not be counted as task records.

⚙ Foundation · Plumbing — connect the pipes before the factory runs (5 checks, no exceptions)
🧭 Reason / Plan is cross-cutting — outcome, audience, proof, constraints, and judgment guide every stage; it is not Stage 1.5.
Stage 1ProduceCapture the raw ingredients
→
Stage 2ProcessTurn ingredients into assets
→
Stage 3PostDistribute everywhere
→
Stage 4PromoteAmplify the winners

The loop closes: every weekly MAA brief feeds new learnings back into Stage 1. Capture → Reason → Process → Post → Promote → measure → repeat.

● published definitive article  ·  agents marked “coming soon” get their definitive article next; until then, run the stage’s SOPs below. The current roster of registered agents — with status, skill file, and a machine-readable index — lives on the Agent Roster.

Foundation · Plumbing

Before the factory runs, the pipes must connect. Tracking, hosting, plugins, and access have to work or every stage downstream leaks.

Agents that run this layer

Christopher — Local Service Website Auditor ●  · 
Stephanie — Operations Assistant (definitive article coming soon)

Technical setup

Foundation · Access & Governance

Who can touch what, how work is tracked, and how the team runs. The discipline that keeps the factory shipping instead of drowning in process questions.

Stage 1 · Produce — capture the raw ingredients

Produce means capturing what is already happening — not creating from nothing. Job-site photos, one-minute videos, customer love, podcasts, speaking, mentions. Build the structured knowledge base before reasoning.

Agents on the floor

Capture Coordinator (coming soon)  · 
Ethan — Positive Mentions ●  · 
Company KB Builder ●  · 
Olivia — Knowledge Panel Helper ●

Capture & inventory SOPs

Cross-cutting · Reason / Plan

Only with a complete knowledge base can this agent reason about who to build relationships with and what to talk about. A pre-condition for everything downstream.

Agent on the floor

Topic Wheel Generator (definitive article coming soon)

Build next: granular SOPs for setting authority spokes and ranking the named humans per spoke. The definitive article is the source until those ship.

Stage 2 · Process — turn ingredients into assets

Convert raw video, audio, and photos into review-ready assets: transcripts, articles, snippets, and captioned images. Evaluate each candidate against documented acceptance criteria and tag it to the Topic Wheel. Do not publish until the named reviewer accepts it.

Agents on the floor

Descript (coming soon)  · 
Brandon — Blog Post Helper ●  · 
Jennifer — Article Grader ●  · 
Library Curator (coming soon)

Edit & transcribe

Build the asset (article & library)

Stage 3 · Post — distribute everywhere that matters

Place each accepted asset only on the channels that serve the Goals, Content, and Targeting plan, adapted natively for that channel. Distribution is selective, not blanket syndication.

Agents on the floor

Adrian — Local Service Page Builder (coming soon)  · 
Personal Brand Site Engineer ●  · 
Cross-Posting Agent (coming soon)

Publish & crosspost

Entity & authority distribution

Stage 4 · Promote — amplify the proven winners

Put paid wind in the sails of organic content that already works. Don’t run ads to guess what works — run ads to multiply what’s already winning. Dollar a Day. Score every mention out of 30. The weekly MAA brief closes the loop.

Agents on the floor

Boost Manager — Dollar a Day ●  · 
Google Ads Agent (coming soon)  · 
Redirect-Hygiene Auditor ●  · 
MAA Reporter ●

The Dollar a Day Boost Team — seven agents, one conductor, all published

The team that runs the Dollar a Day master course:  
Boost Manager ●  · 
Unicorn Hunter ●  · 
Signal Setter ●  · 
Campaign Builder ●  · 
Boost Scorer ●  · 
Funnel Sequencer ●  · 
MAA Reporter ●

Each page ends with the full copy-paste skill.md. Vertical spin-offs: Landscapers · HVAC · Dentists · Real Estate — proof in the Dollar a Day stories.

Boost & advertise

Core Components — the frameworks under the factory

The mental models that make every part fit. Reference these as you run any stage.

  • Personal Brand Manager — your reputation is what others say; track and score every mention.
  • Topic Wheel — who you know × what you know (see Reason / Plan above).
  • The 3×3 Video Grid — Awareness/Engagement/Conversion × Why/How/What.
  • Content Library + Pillar/Micro/Distribution pyramid — one pillar yields a dozen micro-pieces.
  • 3 Components of Authority — score everything out of 30 (What 0–10, Who 0–10, Where 0–10). See Score for Content Authority.

Build Meaningful Relationships

AI can help prepare, remember, and amplify, but a human still owns consent, trust, promises, and consequences. Show up with people, then let the factory support the relationship.

  • Geo Category Grid — be your trade × your geography.
  • Network Power — co-create with the people on your Topic Wheel.
  • Books — use AI to assist research and drafting while a named human author owns accuracy, originality, and usefulness. A book can support authority; it does not create it instantly.
  • Cold Email — give before you ask.
  • Speaking — borrow other people’s stages.

Perform — measure what matters

Review what is not working, pause or change it under the named owner’s authority, and repeat on the documented cadence. Record metrics, analysis, and the next action each cycle.

Agents on the floor

MAA Reporter ●  · 
Christopher — Quick Audit ●

Also under Perform: MAA (Metrics · Analysis · Action), Google Search Console, Google Maps & Guides, Google Bowling defense, and Funnel Hacking. Build these as definitive articles next.

Frameworks & Strategy (reference, not step-by-step tasks)

The thinking tools behind the work. Acronyms the team runs on.

Moved out of the Task Library

These pages are valuable but they are not tasks, so they no longer live in the library. They have new homes (with redirects), which keeps the library a clean, executable list:

  • Recruitment / Hiring: Be a Filipino Agent · Be a Pakistani Agent · Agent Welcome (Kosovo) · Agent General (Nigeria, onlinejobs.ph, Pakistan) · Partner Management – Pakistan
  • Services / Offers: Content Engine Monthly Retainer · Micro Course
  • Help / FAQ: Coach Yu – Guest FAQ · “Are You a Content Wrangler?”

For AI agents reading this page

Published entries with a resolvable skill can be executed, not just read. The current registered set is listed on the Agent Roster, which embeds its machine-readable registry (stable IDs, statuses, article URLs, and skill-file names) as a JSON block: <script type="application/json" id="agent-registry">. A plain-text index lives at llms.txt. To run a published agent: fetch its definitive article, copy the skill file between the START and END markers, and load it into a Claude project. Statuses are exactly published or coming-soon.

This library mirrors the Content Factory Field Guide. Each definitive article ends with a copy-paste skill.md file. Each real client run becomes a short meta article that links back here and points to the next step — so the system documents and improves itself.