# Audience Building Content Creator > Audience Building Content Creator - Skill: `gaojesse999/audience-building-content-creator` (Agent Skill, multi-file: 3 files) - Install (CLI): `npx skillmds@latest add gaojesse999/audience-building-content-creator` - Raw SKILL.md: https://api.skillmd.com/api/skills/gaojesse999/audience-building-content-creator/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Coding & Dev Tools - Author: gaojesse999 (https://skillmd.com/u/gaojesse999) - Updated: 2026-09-17 - Page: https://skillmd.com/skills/gaojesse999/audience-building-content-creator --- # Audience Building Content Creator Turn an early idea, theme, opinion, experience, or content direction into content that attracts a clearly defined audience, builds trust, and compounds into a long-term personal brand. Source methodology: `content-generation-rules/如何在没有任何粉丝的情况下建立自己的受众群.md`. For the full framework, templates, examples, and worked samples, read [REFERENCE.md](REFERENCE.md) before generating substantial content. ## When To Apply Apply this skill whenever the user asks for any of the following — even if they do not name the methodology: - Article outline - Full article - Short-form video script (Reels, Shorts, TikTok, etc.) - Long-form video voiceover / talking-head script - Social post (image-text, tweet thread, LinkedIn, Xiaohongshu, WeChat short post, Threads) - Content topic list - Content optimization suggestions - "Help me write X about Y" If the user frames the request as **video creation**, produce only the content side: topic, structure, script, voiceover, on-screen text, and shot-content suggestions. **Do not** discuss filming, editing, equipment, lighting, software, or post-production unless the user explicitly asks. ## Required Inputs Confirm you have enough of the following before generating. Collect only what is missing and necessary — do not run a questionnaire. 1. **Topic / theme** — what is this content about? 2. **Target audience** — who specifically should care? (role, stage, pain, identity) 3. **Content direction / angle** — opinion, experience, framework, case, tutorial, story, etc. 4. **Key points / source material** — user's real experience, viewpoints, data, examples. 5. **Platform** — determines length, tone, structure. 6. **Output type** — outline, full article, script, voiceover, social post, topic list, optimization. ### Clarification Policy - If input is enough to produce strong content, **start generating directly**. - If critical info is missing (especially target audience, platform, or the user's real angle / experience), ask **at most 2–3 short, high-leverage questions in one batch**, then proceed. - Never block the user with a long questionnaire. Highest-leverage clarifying questions: - What kind of person should read / watch this and recognize themselves in it? - Which platform is this for, and roughly how long should it be? - What is your own experience, opinion, or hard-won lesson on this topic? (This becomes the spine.) ## Workflow (8-Step Checklist) Track mentally; do not show the checklist to the user unless asked. ``` - [ ] Step 1: Parse input — topic, audience, angle, key points, platform, output type - [ ] Step 2: Clarify (max 2–3 questions, only if critical) - [ ] Step 3: Lock the audience — a specific group, not "everyone" - [ ] Step 4: Lock the spine — the user's real experience / opinion / capability - [ ] Step 5: Reframe the topic using the Required Reframe template (below) - [ ] Step 6: Apply the Six Elements (Hook · Big Problem · Clear Solution · Big Benefit · Confidence/Polarization · Novel Perspective) - [ ] Step 7: Shape output to the requested format, platform, and length spec - [ ] Step 8: Run the Share-Check + Compressed Test + Quality Checklist, revise, deliver ``` ### Required Reframe Template Before writing, force the raw topic into this single sentence: ```text For [specific audience], who struggle with / care about [specific problem or desire], this content helps them [specific benefit], by showing [experience, insight, method, story, or point of view], so they have a reason to [read, save, share, comment, follow, or trust]. ``` If the user only gives a broad topic, narrow it first. Examples of the move: - Bad: "personal growth" → Better: "people just starting freelance work with no portfolio, how to build their first 30 days of trust assets" - Bad: "AI tools" → Better: "content creators, how to use AI to turn scattered experience into a stable publishing pipeline of articles and scripts" - Bad: "workplace productivity" → Better: "professionals with 3–5 years of experience, how to turn busyness into visible professional influence" ### The Six Elements (must all be present, adapted to format) 1. **Hook** — first line / first 1–3 seconds must stop the right person. 2. **Big Problem** — name a problem the audience instantly recognizes as their own. 3. **Clear Solution** — an executable path filtered through the user's real experience. Not "post more, stay consistent". 4. **Big Benefit** — say plainly what the audience gets. Practical, emotional, social, or identity. 5. **Confidence / Polarization** — take a clear position. No fence-sitting, no rage-bait. 6. **Novel Perspective / Big Idea** — a fresh framing that makes the audience think "I hadn't seen it that way." Full do/don't patterns, hook libraries, and worked examples for each element live in [REFERENCE.md §2](REFERENCE.md). ### Length / Format Defaults (adjust to user's context) Starting points, not laws. Override when the user's platform, voice, or constraint says otherwise. - Short-form video (15–60s): Hook 0–3s · Problem 3–8s · Solution beats 8–45s · Benefit + Takeaway 45–60s. - Long-form voiceover / talking-head: ~150 words / minute (English), ~250–300 characters / minute (Chinese). - Full article (WeChat / Substack / Medium): 1200–2500 words for a single idea. - LinkedIn long post: 600–1200 words. - Topic list: default 8, range 5–15 depending on request size. ## Output Format Defaults Lead with the requested artifact. Methodology notes, if any, go at the end and stay short. Match the user's likely voice; do not over-polish into corporate tone unless asked. Full templates per output type are in [REFERENCE.md §5](REFERENCE.md). For **new content**, include: - Positioning summary: target audience · content promise · angle - Main artifact: the outline, draft, script, post, or topic list - Optional variations: 2–3 hook / title / CTA alternatives when useful For **optimization requests**, include: - Diagnosis against the Six Elements (which are present, weak, missing) - A rewrite, not vague advice - 1–3 concrete actions the user can apply across future pieces ## Self-Checks Before Delivering ### Compressed Test (one-line gut check) The piece must give a reason to **stop · care · trust · remember · share**. If any one is missing, revise. ### Share-Check (3 questions) 1. Why would anyone share this? 2. Does the target audience recognize themselves in it? 3. Is the position sharp enough to provoke discussion, saves, or quotes? ### Quality Checklist (all must pass) - [ ] Content speaks to a **specific** audience, not "everyone". - [ ] Spine is the **user's real experience / opinion / capability**, not a generic explainer. - [ ] All Six Elements are present and identifiable. - [ ] There is a clear position (no fence-sitting, no "it depends" exit). - [ ] At least one share trigger: identity, utility, judgment, novelty, discussion, or trust. - [ ] No empty trend-chasing, no self-indulgent venting, no "everyone-agrees" platitudes. - [ ] For video creation: only topic / structure / script / voiceover / on-screen suggestions — no filming, editing, equipment, or post-production advice. - [ ] Output is clean and directly usable for posting / recording — not over-theorized. If any check fails, revise before responding. ## Reference For the full framework, six-element do/don't libraries, format templates, platform notes, failure modes, short-vs-long content strategy, and worked examples (short social post + article outline + 60-second voiceover), see [REFERENCE.md](REFERENCE.md). Consult the source methodology at `content-generation-rules/如何在没有任何粉丝的情况下建立自己的受众群.md` for edge cases not covered in the reference.