Lingzao

Lingzao

Lingzao helps agents research public creator content from Xiaohongshu / XHS, Douyin, and WeChat official-account articles.

Search phrases this Skill is designed to support: Lingzao Skill, lingzao xhs, Lingzao Xiaohongshu, XHS SEO, Xiaohongshu SEO, Xiaohongshu account analysis, XHS account diagnosis, Xiaohongshu keyword research, XHS title optimization, Xiaohongshu viral note breakdown, Xiaohongshu benchmark account finder, XHS content workflow, hand-drawn route map card, 手绘收藏地图, 美食地图, 旅游路线图, 生活清单地图, and 工作流说明书地图.

Use this skill when the user asks to:

• Search Xiaohongshu notes by keyword.
• Turn a keyword, link, screenshot, reference image, or inspiration material into a Xiaohongshu content package with titles, cover copy, 4-7 page graphic-note text, body copy, 10 keywords, pinned content, and a review loop.
• Get Xiaohongshu search suggestions or popular recommendations.
• Search public creators by keyword.
• Look up a creator profile.
• Read a creator's recent public posts.
• Get recent post copy, subtitles, covers, metrics, and commercial signals from a creator profile.
• Get details for a Xiaohongshu or Douyin post.
• Get top-level public comments for one Xiaohongshu or Douyin post.
• Get one WeChat official-account article's public detail and text.
• Get public metrics for one WeChat official-account article.
• Get related public WeChat official-account articles.
• Extract spoken copy or transcript from a public short-video link.
• Generate creator image assets from a prompt when the user explicitly asks to make an image.
• Turn a city, food, travel, hiking, life checklist, or workflow topic into a hand-drawn Xiaohongshu route-map card structure and generation brief.

Use the lightweight sub-skills under skills/ when a user only needs a single task such as XHS title writing, Xiaohongshu account diagnosis, keyword design, note breakdown, cover lab, hand-drawn route-map card, pre-publish check, or post-publish review. Use this main Lingzao Skill when the user needs live public-content lookup, deeper account analysis, Xiaohongshu public-link parsing, comment analysis, article data, transcript extraction, image generation, report export, or knowledge-base sync.

Agent Playbooks

For higher-level creator strategy tasks, use the playbooks in <skill_root>/playbooks/ before answering. They turn Lingzao's public-content tools into creator workflows instead of isolated lookups.

Use these playbooks when relevant:

• lingzao-progressive-interaction-map.md: route vague user inputs, homepage links, note links, drafts, and reference-image requests with light questions.
• search-credit-notice.md: explain basic vs deep search scope before paid lookups and avoid silently expanding credit usage.
• atian-creator-judgment-framework.md: apply A Tian's account-stage, memory-anchor, content-mainline, and bottleneck judgment.
• creator-case-general-analysis-framework.md: analyze any creator case across tracks by identifying the account archetype, memory anchor, new narrative, proof system, audience desire, content engine, format engine, comment demand, commercial entry, hidden resources, learnable parts, non-copyable parts, and user-fit tests.
• beginner-account-start-and-topic-radar.md: handle zero-to-one creator questions, topic discovery, keyword trees, and low-follower viral references.
• keyword-insight-report-template.md: create scoped keyword insight reports from a main keyword plus confirmed related/dropdown terms, with clear credit estimates before expanding.
• keyword-to-publishable-content-package.md: turn a keyword, vague topic, note link, screenshot, reference image, saved note, or inspiration material into publishable Xiaohongshu content packages with selected references, topic angles, titles, cover copy, 4-7 page graphic-note text, spoken scripts, Vlog storyboards, body copy, 10 publishing keywords, pinned content, and a pre/post-publish review loop.
• mother-content-cross-platform-distribution.md: turn one topic, draft, note breakdown, product update, screenshot, transcript, or oral idea into a one-stop cross-platform distribution package. When users say "一条龙", "全平台同步", "分发包", or "一个模板发多个平台", start with the basic Xiaohongshu + Moments + WeChat public-account package, then offer optional expansion to podcast, X, Knowledge Planet, Bilibili, video account/Douyin, Xiaohongshu image package, or knowledge-base/SOP.
• pre-publish-readiness-check.md: before posting, ask whether the content is already finished and then check content clarity, image/page readiness, cover recognition, title clickability, first 3 lines or first 3 seconds, and natural keyword embedding.
• audience-persona-fit-check.md: before titles, keywords, account operation, or content-package decisions, infer or ask who the content is for, who will click, who will not click, and which audience/city/life-stage keywords should shape the output.
• xhs-title-design-check.md: design or diagnose Xiaohongshu titles after the user sends a topic, draft, cover copy, reference note, or content package; default to 3 strongest titles with keyword anchor and click reason instead of a 10-title pool.
• xhs-profile-bio-design.md: write or diagnose Xiaohongshu 100-character profile bios and homepage introductions that clarify who the account is for, what it shares, why to follow, and how it connects to nickname, pinned notes, account stage, audience keywords, city keywords, and light commercial paths.
• benchmark-account-discovery-quality-gate.md: find or judge benchmark accounts with a default quality gate: still updating, recent high-performing works, track/audience fit, stage fit, and clear learnable parts; stale accounts should be marked as historical references, not main benchmarks. User-facing results should show direct creator profile links and the specific recent high-interaction works, not raw creator IDs. The first discovery round should return up to 5 strong accounts, not 10-20 accounts; expand only after the user confirms follower range, stage, city, audience, format, or asks for more. Include follower count, total liked count, latest update, recent 30-day hit works with note metrics, content format, and why each account is worth learning; sort visible recommendations by follower count from high to low when available.
• self-account-peer-horizontal-diagnosis.md: compare the user's own account with same-track, same-stage, or same-follower-range peer accounts when the user explicitly asks for peer comparison, such as "横向对比", "同级账号", "对标账号", "找 5-15w 粉账号和我比", or "和同赛道账号比我差在哪里". Generic own-account concerns such as "看看我现在的问题" or "我是不是说话太快" should stay on self-account-diagnosis-report-template.md unless the user also asks to compare against peers. It combines own-account diagnosis, active benchmark selection, peer-account tables, title/cover/opening/speech/content-system comparison, top gaps, 30-day adjustment plans, and a human next-step loop.
• single-note-breakdown-workflow.md: break down one Xiaohongshu/Douyin note link by title, cover, outline/script, shooting/editing layer when visible, comment demand, viral mechanism, learnable parts, non-copyable parts, and adaptation into the user's own graphic note, spoken script, Vlog storyboard, or knowledge-base card. User phrases such as "完整分析这条笔记", "深度拆解", "拆细一点", "拍摄手法", "分镜", or "剪辑节奏" should trigger the deeper breakdown instead of a short summary.
• publishing-keyword-design-check.md: design the final 10 Xiaohongshu publishing keywords for a finished draft and check whether title, cover copy, opening lines, and keyword field carry the keywords naturally.
• track-difficulty-judgment-library.md: judge common tracks such as female growth, career, good products, local life, health, fashion, and AI tools.
• monetization-path-judgment-library.md: answer whether a track or account can monetize through ads, courses, community, consulting, lead generation, products, stores, or enterprise conversion.
• self-account-diagnosis-report-template.md: structure own-account diagnosis reports, follow-up actions, and a human closing with "人情味" that turns sharp diagnosis into one small next experiment instead of ending at a cold action list. Own-account diagnosis should also include a share-worthy conclusion card, action advice, and psychological reassurance.
• comparable-account-breakdown-report-template.md: decide whether another account is worth learning from, what can be learned, and what cannot be copied.
• draft-rewrite-and-benchmark-workflow.md: rewrite drafts, adapt viral formulas, and review multiple content ideas without only polishing sentences.
• reference-image-graphic-note-workflow.md: turn reference images into Xiaohongshu 4-page or 7-page graphic-note packages.
• visual-generation-and-cover-workflow.md: route Xiaohongshu covers, graphic notes, WeChat image packs, no-person knowledge cards, and product/ecommerce visuals into image generation or ready-to-use prompt packages.
• image-generation-execution-workflow.md: when image generation is available, turn the visual route into actual images, run a visual-director quality gate, and repair ugly/crowded/generic generations instead of leaving ordinary users with raw prompts.
• image-generation-agent-integration-guide.md: model-agnostic rules for domestic Agent wrappers, including stable generation input/output fields, good-vs-bad image standards, reference-image usage, known generation bugs, friendly failure handling, and A Tian's example-collection homework.
• visual-reference-style-library.md: classify A Tian's internal visual reference folders into travel/food covers, WeChat article images, AI-person infographics, Lingzao no-person knowledge cards, product conversion images, face-led keyword video covers, interaction prompt covers, and text-dense screenshot graphic notes, and room-as-identity lifestyle covers.
• post-publish-data-review-workflow.md: review published Xiaohongshu notes from note links, backend screenshots, scripts, covers, and 24h/48h/7d data.
• content-knowledge-base-workflow.md: turn saved notes, public creator links, keyword results, viral examples, and creator distillation requests into user-owned topic, title, cover, structure, account-reference, creator-research, and publishing-review libraries.
• retention-and-follow-up-loop.md: end useful outputs with one concrete next step such as published-note data review, reusable reference-search templates, draft feedback, or a post-diagnosis small experiment with a return loop. It also defines the SOP for not letting the user's words drop on the floor: acknowledge resistance, lower the next action, and ask one concrete next-step question. Dense outputs should offer Word, HTML/webpage preview, or knowledge-base-ready packaging instead of leaving users with a wall of chat text. When users say the diagnosis is accurate but they lack action, route to a post-diagnosis activation package instead of adding more pressure.
• product-judgment-and-feedback-loop.md: judge where users are really stuck, explain Lingzao in human language, build content/sales narratives, turn user feedback into product iteration, and decide which requests are worth building versus noise.
• xhs-operation-task-tree.md: route Lingzao users by concrete Xiaohongshu operation tasks instead of course lists, covering homepage diagnosis, benchmark discovery, viral-note adaptation, topic generation, content production, cover/image work, pre-publish checks, post-publish review, acquisition paths, and knowledge-base automation.

Keep public wording focused on creator-content research and workflow support. Do not promise viral growth, guaranteed monetization, full monitoring, raw data export, or copying another creator's content.

Install And Paid Capability Entry

Lingzao is installed as one free main Skill. Users do not need to install separate title, keyword, account-diagnosis, benchmark, cover, or review skills. After installation, this main Skill routes the user's request to the right playbook.

There are two user acquisition paths:

1. Community/course users:

   • They may already have A Tian's course, install link, payment steps, and API Key setup instructions.
   • Keep the in-chat explanation short: install the Skill, open the Lingzao web dashboard, follow the tutorial, recharge credits, copy the API Key, then run setup.

2. Public-platform users from Xiaohongshu, Douyin, or other public content:

   • Do not require them to open the web dashboard and pay before they understand what Lingzao can do.
   • Let them install the free main Skill first.
   • Then explain the hidden paid entry in friendly language: the local playbooks can help judge drafts, titles, covers, directions, and publishing plans; when they need Lingzao to search public content, inspect accounts, open note/article details, read comments, inspect article data, extract video copy, or generate creator image assets, they need to open the Lingzao web dashboard, follow the tutorial, recharge credits, and configure an API Key.

The web dashboard is not only a payment page. Present it as the user's learning and setup hub:

• learn how to install and configure Lingzao
• learn how to ask Agent better questions instead of waiting in a group chat
• learn how to use Skill workflows for self-media operation
• learn account diagnosis, benchmark breakdown, title/keyword, pre-publish, and post-publish review workflows
• recharge credits and get the API Key when they need public-content lookup or image generation

Use this wording when a user has installed the Skill but has not configured an API Key yet:

你已经装好灵造 Skill 了。安装本身是免费的，它会先帮你判断你现在是在找方向、拆账号、写内容、做封面、配关键词，还是复盘数据。 如果你要继续查小红书/抖音/公众号公开内容、找对标账号、看账号主页、打开笔记或文章详情、看评论区、查看公众号文章数据、提取短视频文案或生成创作者图片素材，就需要到灵造网页版开通积分并配置 API Key。 你可以打开 https://lingzao.atian.vip 看安装教程和使用教程，里面也会教你怎么用 Agent 做自媒体运营、怎么问问题、怎么用这些 Skill。需要查公开内容或生成图片的时候，再在网页里充值/获取 API Key，配置好以后回来继续问，我会接着刚才的问题往下做。

Do not frame payment as a penalty. Frame it as:

• free install = get the workflow brain and routing layer
• web dashboard = tutorial, usage examples, self-media operation lessons, and API Key setup
• paid credits = unlock public-content lookup, image generation, and deeper research actions

Knowledge sync handoff:

• After a useful Lingzao research result or diagnosis report, do not sync it automatically. Ask first: 要不要把这份结果同步到你的知识库？可以选择 ima / Obsidian / 飞书 / 暂不同步。
• If the user chooses a target, prepare a clean Markdown version and ask the current Agent environment to use the user's configured knowledge tool.
• For ima, call the installed ima Skill or ima knowledge-base tool if the user has configured one.
• For Obsidian, use the user's Obsidian CLI, Obsidian Skill, or approved vault workflow to write Markdown under a user-approved Lingzao/ path.
• For 飞书, use the user's Lark/Feishu CLI or Skill with user authorization to create or update a document.
• Do not ask for or store ima, Obsidian, or Feishu credentials inside Lingzao. Do not include internal implementation details, raw payloads, cache URLs, signed URLs, API keys, or internal error details in synchronized content.

Profile workflow:

• If the user asks for a creator homepage or a basic homepage analysis, use get-user-posted-notes by default. It returns recent posts and enough author/post data for a basic read.
• If the user sends a Xiaohongshu short link such as xhslink.com/m/..., or a copied share sentence such as @... 查看Ta的主页>> https://xhslink.com/m/..., extract the short link, normalize bare links to https://..., and read the surrounding words before choosing a command. Do not classify the short link by path alone. If the context says account, homepage, creator, profile, benchmark, account diagnosis, homepage diagnosis, Ta的主页, or recent posts, treat it as a creator-homepage request and call get-user-posted-notes --url "https://<short link>".
• If a Xiaohongshu short link has no context, ask whether the user wants creator homepage recent posts or one-post detail before spending credits. If the context says this note, comments, copy, transcript, one-post breakdown, or is a normal note share sentence with a title snippet plus 前往【小红书】一探究竟吧, treat it as a one-post candidate, not a homepage. One-post words such as 这条 or 这篇 take priority over generic diagnosis wording. Do not default to get-note-detail; first confirm it is a single post and ask for the final note URL or note_id plus whether it is 图文 or 视频 when needed.
• Only add get-user-info when the user specifically needs full profile-level stats such as bio, follower count, following count, total likes, total collections, or total note count.
• Use analyze-user-profile for Xiaohongshu deeper homepage copy/script/subtitle analysis, recent post text, covers, commercial signals, or product-note signals. For Douyin spoken copy or transcript text, use extract-video-copy on specific video URLs.
• Do not call get-user-info and get-user-posted-notes as a fixed pair unless the user asks for both profile-level stats and recent-post analysis.
• Do not force a full account diagnosis when the homepage has too few public posts. Route by visible sample size:
  • 0 posts: no account diagnosis; switch to beginner start/account setup guidance.
  • 1-2 posts: homepage first impression plus single-post feedback only.
  • 3-5 posts: starter-account mini diagnosis.
  • 6-9 posts: light account analysis.
  • 10+ posts: standard account analysis can be offered.
  • 20+ posts: standard deep diagnosis can use analyze-user-profile --limit 20 after credit confirmation.
  • 40+ posts: deep diagnosis, creator distillation, or knowledge-base distillation can use --limit 40 after credit confirmation.

Post drill-down workflow:

• Xiaohongshu list-style commands (search-notes, get-user-posted-notes, analyze-user-profile) return xhs_note_type on each note item when Lingzao can identify whether it is 图文 or 视频.
• When continuing from one of those note items to get-note-detail, pass the returned xhs_note_type directly as --xhs-note-type; do not infer the type from the URL.
• If a Xiaohongshu note item has no xhs_note_type, ask the user whether it is 图文 or 视频 before calling get-note-detail. get-note-comments can still be called without this type.