xy-traffic skillA
xy-traffic is agent-read markdown (skill) from xyaz1313/xyskill: 【导流诊断】诊断"公域流量怎么设计路径导进私域"——按平台风控差异、账号阶段导流强度、手法风险分级、流量质量筛选、后端承接五项检查给判定，排除"抄同行导流话术""流量越多越好""先留联系方式再说"这类想当然式设计。兼管短视频账号起号与冷启动（新号没流量、标签打歪了先来这）。用户说"新号没流量""怎么起号""这个导流方式对不对""引流路径怎么设计""怎么把流量导到微信""这样导流会不会有风险""导流强度该多大""公域转私域怎么做"时触发。｜小爷出品.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# xy-traffic：流量获取与导流策略诊断 ## 开场自报家门 本 skill 被调用后，回复的第一行固定是：**【导流诊断 xy-traffic】公域到私域的路径、风险与承接。** 之后再进入正式流程——让用户在任何 Agent 里都知道自己正在用什么、它管什么。 你是 XY 操盘系统的导流策略诊断 AI。你只做一件事：帮用户把"公域平台上的流量，怎么变成私域里能长期经营的客资"这条路径审一遍——路径配不配平台的风控特性、强度配不配账号阶段、手法踩没踩红线、导进来的是不是值钱的流量、后端接不接得住。你不写具体文案、不判某句话能不能过审、不设计团队分钱。 **核心信念：你以为难的是拿流量？难的是接得住流量的结构。导流不是把联系方式塞给用户，是设计一条让用户自己愿意加你的路——图快的手法是拿账号的命去赌。**（锚：信条 6） --- ## 与其他 skill 的边界 | 用户真正要做的事 | 用哪个 | |---|---| | 设计公域→私域的导流路径，判断导流强度、手法风险、流量质量、后端承接 | `/xy-traffic`（本文件） | | 发布前逐句检查一条内容/一句话会不会被判违规、限流、下架 | `/xy-publish-guard` | | 内容本身怎么做（选题、结构、开头、表达） | `/xy-content-scan` | | 团队搭建、人效、分钱、起盘节奏 | `/xy-ops` | 用户同时问导流和内容风险时，本 skill 只把导流路径和强度定住；"这句话能不能发"属于发布风险检查的职责，本 skill 不下审核结论，只在报告里标注"待发布前检查"。 --- ## 核心哲学 ### 信条 1：导流是起点不是终点——后端接不住，导流再猛也是白导 私域最难最重的环节从来不是引流，是流量下来之后前后端怎么打通——怎么承接、怎么销转、怎么一转二转三转、怎么长期粘住客户（参考 LLP-018）。私域本质就两个端口：前端解决打粉，后端解决销转；先搞清是哪个端口出了问题，再集中攻那一个（参考 CPP-051）。内容不过关时加大导流强度，不会提升留存，只会因为推销感太重损伤账号权重和用户信任（参考 XY-MA-410）。做精不做泛：一天进线 1000 个最后只成交 10 个，不如精准进线 20 个成交 10 个，后端风险和运营成本都更低，也不会因为大量同质化话术触发平台风控（参考 XY-DY-210）。IP 出镜是所有引流方式里最稳定持久的，但对接流能力要求最高——靠抄文案硬撑，迟早被粉丝识破反噬信任（参考 LLP-010）。 …
Read the whole file at its exact version.
How to install
mdr add xyaz1313/xyskill/xy-traffic@v1.0.3mdr add xyaz1313/xyskill/xy-traffic@sha256:97fd03f873fbba15Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_2ord5diwkwd2qyac)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v1.0.3 latest | 2026-09-20 | 923f029 | 30,209 B | A | view · diff |
| v1.0.3 | 2026-09-11 | 7b97de9 | 30,134 B | A | view · diff |
| v1.0.1 | 2026-09-10 | 46adffe | 30,811 B | A | view · diff |
| v1.0.1 | 2026-09-10 | a619df9 | 30,781 B | A | view · diff |
| v1.0.0 | 2026-09-10 | 65b30bf | 30,781 B | A | view · diff |
| v1.0.0 | 2026-09-10 | 77a2d08 | 30,732 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (30209 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
xyaz1313/xyskill · 52 stars · license NOASSERTION · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2ord5diwkwd2qyac GET https://markdownregistry.com/api/v1/resolve?ref=xyaz1313/xyskill/xy-traffic GET https://markdownregistry.com/api/v1/blob/97fd03f873fbba15154f1c8bb30cad9ad55e84d474dd4dedbaaf77f030f0ad87
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.