菜单
Use when the user needs substantial written content such as an article, tutorial, guide, brand story, thought leadership piece, press release, or news-style announcement. Best for long-form writing where structure, voice, credibility, and content-type-specific formatting matter.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when a founder, CEO, owner, or business leader needs an outside-in company diagnosis before action, especially when the issue is broad, ambiguous, cross-functional, knowledge-base-backed, or may involve strategy, growth, sales, organization, operations, finance, or legal risk.
Use when the user wants a customer profile, company research, website analysis, BD due diligence, sentiment analysis, partnership risk review, breach-risk judgment, or global customer intelligence from a company name and official website. Produces a customer-facing BD intelligence brief using Tavily API and Serper.dev API signals, with product pricing, customer persona, buying committee, ICP fit, market positioning, and commercial fulfillment risk. Also supports VBUY/威佰-specific customer development analysis using the bundled VBUY fit reference layer.
Use when the writing assistant should clarify a usable brief through multi-turn conversation before generating any copy, especially when the content type, platform, audience, goal, key message, tone, or constraints are still unclear. Covers social media copy, emails, website copy, newsletters, lifecycle emails, ads, case studies, product copy, articles, guides, speeches, and scripts.
Write professional emails across cold outreach, business communication, replies, follow-ups, meeting requests, status updates, and sensitive messages. Use when the user wants to write a cold email, outbound email, prospecting email, follow-up sequence, professional email, reply, meeting request, internal update, difficult message, or business correspondence. Covers both single emails and cold outreach sequences, but not newsletters, lifecycle campaigns, or non-email sales collateral.
Write China-platform social content for WeChat Official Account, Xiaohongshu, Weibo, and Douyin. Use when the user wants a WeChat article, Xiaohongshu note, Weibo post, Douyin short-video script, or one idea adapted into multiple China-platform versions. This skill is for downstream writing only, not content calendars, account strategy, posting schedules, analytics reviews, trend monitoring, livestream scripts, or full production planning.
Use when the user needs spoken-first content for a speech, keynote, remarks, opening remarks, closing remarks, host script, emcee script, or spoken presentation script. Best for formal spoken content that must sound natural aloud, fit a live setting, and work with audience, time, and event constraints.
| name | longform-writing |
| description | Use when the user needs substantial written content such as an article, tutorial, guide, brand story, thought leadership piece, press release, or news-style announcement. Best for long-form writing where structure, voice, credibility, and content-type-specific formatting matter. |
Long-form Content Writer
Write long-form content that is structurally correct for the requested format, credible in tone, and ready to publish or hand off with minimal extra clarification.
This is a downstream writing skill. If the user already provided a usable brief, write directly instead of restarting broad discovery.
Use this skill for:
Do not use this skill for:
By default, a press release here means a company or brand announcement, not a third-party news report.
Before drafting, decide which mode fits the request.
Use for:
Primary goal:
Use for:
Primary goal:
Use for:
Primary goal:
If the request could fit multiple modes, choose the primary user outcome first. Do not write a tutorial like a blog essay, do not write brand content like a brochure, and do not write a press release like a founder blog post.
Prefer when the piece needs:
Default shape:
Prefer when the piece needs:
Default shape:
If needed, ask for:
If needed, ask for:
Unless the user requests a lighter format, include:
If needed, ask for:
If the brief is already usable, write directly.
If key information is missing:
Ask only for the minimum critical gap. Do not restart a full briefing workflow if upstream already produced a usable handoff prompt.
Before finalizing, verify that:
