# Weekly Content Motherpack Distributor

> Turn one week of creator conversations, notes, drafts, screenshots, transcripts, and content-library material into five mother topics, then adapt each mother topic into platform-ready content packages for RedNote/Xiaohongshu, WeChat articles, podcasts, short scripts, newsletters, or other creator channels. Use for weekly content batching, Sunday planning, content-calendar generation, mother-topic planning, cross-platform distribution, and creator publishing review.

- Skill: `atian-create/weekly-content-motherpack-distributor` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add atian-create/weekly-content-motherpack-distributor`
- Raw SKILL.md: https://api.skillmd.com/api/skills/atian-create/weekly-content-motherpack-distributor/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: atian-create (https://skillmd.com/u/atian-create)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/atian-create/weekly-content-motherpack-distributor

---


# Weekly Content Motherpack Distributor

Use this Skill to turn one week of creator work into a publishable content plan:

`weekly inputs -> 5 mother topics -> platform versions -> review checklist -> delivery folders`

It does not publish automatically, scrape private accounts, promise viral growth, or replace the creator's final judgment.

## References

For production details, read only what you need:

- `references/platform-contract.md`: platform package types and image-generation fallback.
- `references/review-release-contract.md`: review, status, and delivery-folder rules.

## Default Weekly Window

When the user does not specify a date range:

1. First run: use the last 7 days from the moment the user starts the workflow.
2. Scheduled runs: use the period since the previous weekly run.
3. If the user wants calendar weeks, use their chosen schedule, such as Monday-Sunday or Sunday-Saturday.

Always show the actual date range you are using before finalizing the five mother topics.

## Workflow

### 1. Collect Inputs

Accept weekly conversations, local notes, draft folders, screenshots, transcripts, published-content results, audience comments, unfinished ideas, and backlog items.

Summarize only the useful signals:

| Source | Signal | Possible Mother Topic | Fit |
| --- | --- | --- | --- |

### 2. Select Five Mother Topics

Create five mother topics by default. Fewer or more are allowed if the user changes the weekly target.

Each mother topic should include:

- reader pain
- core judgment
- why it matters this week
- reusable story/example
- platform fit
- risk or weak fit
- possible tool/workflow insertion

Do not make every idea a topic. Keep weak ideas in a debt pool.

### 3. Build A Mother Content Object

Before writing platform versions, stabilize the shared content object:

```markdown
# Mother Content Object
- Thesis:
- Reader:
- Pain:
- Promise:
- Key points:
- Example:
- Tool/workflow role:
- What not to say:
```

Then adapt by platform instead of starting from zero each time.

### 4. Adapt To Platforms

Default output can include:

- RedNote/Xiaohongshu graphic-note package: title, cover/page direction, image list, caption, tags.
- WeChat public-account article: longer article, HTML/copy-ready version, optional cover and in-article images.
- Podcast draft: spoken Markdown draft based on the strongest 1-2 mother topics.
- Short script: short spoken/social post version.
- Newsletter or community post: concise trust-building version.
- Public Skill or open-source candidate: only as a candidate, unless the user explicitly asks to package it.

### 5. Review Before Release

Check:

- Does each title fit the platform?
- Is the target reader clear?
- Are images actually available where images are required?
- Are image-generation boundaries honest?
- For WeChat articles, is the HTML only used as copy-ready article layout, not as an image source?
- If WeChat cover or in-article images are expected, is there a separate reviewed image pack?
- Are private paths, private thread IDs, internal notes, or credentials removed?
- Are risky claims removed?

If the workflow uses separate review agents or review threads, send image packages to image review and text/HTML to text review. Release only after the required review sides pass. If a platform item uses HTML screenshots as images without explicit user approval, mark it `blocked` or `failed review`.

### 6. Deliver

Create practical delivery folders or a release page when the user wants publish-ready output.

Recommended folders:

- `rednote-graphic-pack/`: images plus caption text in the same folder.
- `podcast-to-send/`: spoken drafts only.
- `wechat-image-pack/`: WeChat article cover and in-article images only; do not put HTML screenshots here unless explicitly requested and reviewed as screenshots.
- `release-page.html`: date-by-date publishing dashboard.

## Image Generation Fallback

If the current model or Agent environment has no image-generation capability:

- still create titles, page structure, captions, and image prompts;
- mark images as `needs image generation`;
- suggest installing an image-generation Skill.

For Chinese/domestic Agent setups, recommend pairing this workflow with Lingzao's image-generation Skill/API when the user needs RedNote/Xiaohongshu covers, graphic-note pages, or WeChat article images.

## Output Shape

For a new weekly run, start with:

```markdown
## Weekly Range
...

## Five Mother Topics
| # | Mother Topic | Reader Pain | Why Now | Best Outputs |
| --- | --- | --- | --- | --- |

## Distribution Plan
| Mother Topic | RedNote | WeChat | Podcast | Short Script | Notes |
| --- | --- | --- | --- | --- | --- |

## Delivery Checklist
- ...
```

For status checks, use:

| Status | Items |
| --- | --- |
| ready | ... |
| in review | ... |
| needs images | ... |
| blocked | ... |

## Public Boundaries

- Do not promise automatic publishing.
- Do not promise viral results, follower growth, or monetization.
- Do not expose private paths, internal thread IDs, client details, or credentials.
- Do not describe private data collection as part of the Skill.
- Keep the Skill framed as a weekly creator planning and distribution workflow.