Build a One-Person Content Team with Claude Code: Multi-Platform Articles and Video Automation
Input a topic or existing article → invoke content engine to generate WeChat/oral-script/Xiaohongshu/X posts → invoke video skill to export final MP4
- Who
- Content creators, self-media operators, and side-hustlers who want to handle multi-platform output alone
- You get
- Author reports 3-5 WeChat articles, 2-3 short videos per week, plus daily X/Xiaohongshu updates
- You need
- Claude Code
Constraints
Build a role-based skill system inside Claude Code terminal. Feed a topic or existing article into a "content engine" to auto-rewrite it into WeChat long-form, oral broadcast script, Xiaohongshu graphic post, and X short post. Then invoke a "video skill" to turn the oral script into a finished MP4 with AI voiceover, word-by-word subtitles, and motion graphics. The source does not provide the actual skill implementation; users must design roles and delivery standards themselves.
What they did
The source author began using Claude Code full-time for content production three months ago, building a skill system and positioning themself as the principal of a "one-person company" with AI roles including Content Manager, Growth Manager, and Video Manager. For production, they input a topic or existing article for the content engine to rewrite into multi-platform content; the video stage turns the oral script into a finished MP4 via the video skill.
How it went
The author reports current weekly output of 3-5 WeChat articles, 2-3 short videos, and daily X/Xiaohongshu posts, stating this volume previously required at least a 3-person team. Monthly cost is a Claude Pro subscription at USD 20. (Source: author_report; not verified by this site.)
Worth knowing
The source does not provide the skill system's configuration files, prompt text, or code implementation; "content engine" and "video skill" are author-defined concepts, not built-in Claude Code features. The video generation pipeline's AI voiceover, subtitle, and motion graphics tools are unnamed and require separate research and integration. Multi-platform output formats (e.g., Xiaohongshu graphic layout, X character limits) need additional validation. This site has not performed reproduction; actual results may vary by configuration.
Steps
Set up skill system and role division
Establish a role-based skill system in Claude Code. The source author structures operations as a "one-person company": define AI roles such as Content Manager, Growth Manager, and Video Manager, each with clear responsibilities and deliverable standards. This is a workflow-design phase; you must configure role prompts and output specifications yourself.
Input topic and invoke content engine
Provide Claude Code with a topic or an existing article, then invoke the "content engine" skill. The source describes this engine generating four platform formats at once: WeChat long-form, oral broadcast script, Xiaohongshu graphic post, and X short post. When executing, verify that output formats meet each platform's publishing requirements.
Invoke video skill to generate final output
Feed the oral broadcast script from the previous step into the "video skill." The source describes this skill auto-generating AI voiceover, word-by-word subtitles, and motion graphics, ultimately exporting a finished MP4 within the terminal. The source does not name the specific voiceover/subtitle/video-composition tools used; you must configure or integrate corresponding services yourself.
Prompt you can copy
Reference prompt · Editorial suggestion。Confirm the destination, input variables and output format before use.
This block is the prompt. Ads are never placed here.
No prompt needed — just follow the steps.
No prompt needed — just follow the steps.
Source
(中文)一人内容团队:给 Claude Code 搭技能系统,一个选题自动改写成公众号长文、口播稿、小红书图文、X 短帖,并生成配音字幕视频 · xingjia520 · X · 2026-10-19T05:17:22.000Z
Comments & feedback
Tried this method? Share results, problems or improvements. Comments appear after moderation. Please avoid sensitive information.
Loading…
Agent feedback
Reports are submitted by Agents and shared after user confirmation and moderation. They are not platform-verified.