Content & publishing
Trend-to-article publishing
Turn RSS feeds and search results into a typeset WeChat article, end to end.
Paid $9 list, $7 until 2026-12-31 · one skill, yours for good. The outline, the steps and the file open after purchase.
Background
Not a prompt-only skill but a local application (Deno + TypeScript, MIT). This skill only does four things: locate the project, run commands, read the outputs, and diagnose failures; writing quality is the responsibility of the pipeline inside the project.
Why it is built this way
The gate is deno task doctor, and it runs before any article is built. A full run spends one model pass over every fetched item and writes into src/temp/. Deno below 2.0 stops at the version check, and an empty providers.ai stops after fetching has already happened, so one failure is free and the other is not. Doctor collapses both into one cheap command with a narrow pass line: all OK, or a single FAIL on LLM.
The skill keeps four jobs: locate the project, run the command, read the outputs, name the failure. It reads src/temp/ rather than the last line of the terminal because every run writes its steps, errors and quality review there, and a run that fetched 0 items still exits clean. dryRun stays on for a related reason. Publishing needs appId, appSecret and the IP whitelist on the account side, and only the run record shows whether the HTML is worth sending.
Where it bites
- A clean exit, zero items The RSS source is dead, or sourceLimits.maxAgeDays cuts too narrow, and the fetch stage returns 0 items. Doctor still says all OK, the terminal still ends on success, and src/temp/ holds an HTML shell with an empty body. Reading the run record before judging is the step that catches this.
- Flipping dryRun without the whitelist Set dryRun to false while the Official Account IP whitelist is still empty and the publish call returns an IP error after the article has been assembled. Filled appId and appSecret only say the config is complete, they do not say the account accepts this machine. Three conditions have to hold before the switch moves.
- The template picks itself dynamic fails partway through rendering, the pipeline falls back to minimal on its own, and this batch ships with a layout the earlier articles do not share. deno task preview renders every WeChat template before you commit to one, and template: minimal pins the fallback so it stops being a surprise.
- A key inside a commit The apiKey sits in trendpublish.config.ts, which one git add . puts into the repository, and from then on every clone carries the credential until it is rotated. The rule that this file is never committed is what keeps the key out of the artifacts the pipeline writes.
This part is for buyers
The outline, the steps and the SKILL.md stay closed until this address owns the skill.
$9 early bird $7 until 2026-12-31
Checkout opens soon — leave your address and we will tell you when it does.
all 28 skills for $149, list $430
Sign in first so we can check your purchase.
When to use it
Use TrendPublish to turn RSS feeds and search results into WeChat Official Account articles automatically (topic → evidence → body copy → typeset HTML → draft/publish). Use when the user asks to \"write a WeChat Official Account article automatically\", \"gather an article from news sources\", \"run a WeChat Official Account dry-run\", or \"publish to a WeChat Official Account on a schedule\".