data-element-market-expert
扫描数据要素市场动态与竞争格局,研究落地案例,判断趋势与成熟度阶段,输出机会清单与规模测算。当用户需要数据要素市场专家相关的诊断、方案设计、SOP 执行或交付物产出时使用。
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- name
- data-element-market-expert
- tags
- [ "数据要素市场", "市场趋势", "竞争格局", "模式验证" ]
- author
- 图灵数盟
- license
- MIT
- homepage
- https://www.turingtech.net.cn
- description
- 扫描数据要素市场动态与竞争格局,研究落地案例,判断趋势与成熟度阶段,输出机会清单与规模测算。当用户需要数据要素市场专家相关的诊断、方案设计、SOP 执行或交付物产出时使用。
02 资源文件 3
- 参考文档profile.md2.0 KB
- 参考文档README.md2.7 KB
- 参考文档skill-report.json19.4 KB
03 SKILL.md 正文
数据要素市场专家 · Data Element Market Expert
作者:图灵数盟(图灵数盟(深圳)数字产业有限公司)|官网|联系邮箱:public@turingtech.net.cn 类型:单专家 Agent|分组:数据专家|编号:40 职业头衔:数据要素市场分析师
核心使命:看懂数据要素市场的大盘与趋势,为战略决策与客户沟通提供市场层面的判断依据
简介:扫描数据要素市场动态与竞争格局,研究落地案例,判断趋势与成熟度阶段,输出机会清单与规模测算。
完整知识底座见
references/knowledge-base.md。
数据要素市场专家 Playbook(知识底座)
适用主体:图灵数盟(深圳)数字产业有限公司 资料来源:
图灵数盟内部资料库整理基准日:2026-09-22 文档性质:岗位知识底座 + 可执行技能清单。
使用方式
需要具体市场数据、成熟度阶段判断、趋势结论、测算方法、SOP 步骤、交付物清单、质量校验项、协作接口、话术与风险提示时,
读取 references/knowledge-base.md(该文件为源资料逐字拷贝,权威版本)。
内容索引
- 1.1 一句话定位 —— 市场分析师角色;为战略提供外部视角
- 1.2 政策与标准依据 —— 数据要素市场 78 份、行业白皮书 27 份、案例与样例 8 份、国数政策〔2026〕6号、国数政策〔2023〕11号、可信数据空间行动计划、128 个入表案例样本
- 1.3 核心模型一 —— 数据要素市场四层结构(应用层/服务层/流通层/要素层 + 基础设施)与各层成熟度竞争机会
- 1.4 核心模型二 —— 十类市场主体及其角色与商业模式
- 1.5 核心模型三 —— 市场成熟度四阶段与 2026 年所处位置(模式探索期向规模化期过渡)
- 1.6 核心模型四 —— 市场趋势五个判断及对业务的启示
- 1.7 常见问题与标准答复 —— Q1~Q5(泡沫、入场时机、最大机会、模式跑通判断、市场数据来源)
- 1.8 源材料索引 —— 数据要素市场 78 份等 11 类源材料
- 2.1 能力清单 —— C1~C10 能力与输出物
- 2.2 标准作业流程 SOP —— S0 市场情报库建设(持续)至 S8 客户沟通支持
- 2.3 交付物清单 —— 10 项交付物
- 2.4 质量校验清单 —— 10 项交付前必查
- 2.5 协作接口 —— 上游 / 下游 / 平行共 9 个接口
- 2.6 关键话术与风险提示 —— 内部 3 条 + 对客户 2 条话术 + 6 条风险提示
三条输出纪律
- 无证据不下结论,金额只给参考区间并注明口径。
- 合规与权属是闸门,过不了闸门不谈后续。
- 不越界代替持牌机构与监管机关出具意见。
04 同仓库更多 Skills
serpmaven
Scrape Google search results (SERP) to JSON with SERP Maven (serpmaven) - a real Chrome browser on a residential proxy with sticky sessions. Run it as a CLI, a Python library, a local HTTP search API (`serve`), an MCP server or a Docker image; set the proxy login, workers, pages and cost tracking. Use when the user wants Google results, rank tracking, a self-hosted SERP API, or live Google search for an AI agent.
revnu-landing-page-audit
Find out why a landing page isn't turning visitors into signups, demos or sales. Audits one page against what the ad, post or search that sends people there promised, then checks the first screen, proof, call to action, friction and mobile. Returns at most 7 prioritized fixes, plus what is fine and what could not be checked; rewrites specific lines and fixes the page in the repo when asked. Never promises a conversion lift. Works without a Revnu account. Use when the user says or asks: "audit my landing page", "why isn't this page converting", "review my homepage", "my ads get clicks but no signups", "people bounce from the pricing page", "CRO review", "improve conversion rate", "is my hero section clear", "roast my landing page", "rewrite my headline", "what's wrong with this page", "landing page feedback", "make the signup page convert better". Not for SEO or AI-search audits, page speed engineering on its own, or building a new page from scratch.
revnu-growth-context
Write down once who buys, what they're stuck on, what it costs, what proof you have and what you've already tried, so every growth task starts from facts instead of a questionnaire. Creates or updates .agents/revnu-growth.md from the repo, the live site and the user, and imports an existing product-marketing.md. Use when the user says "set up our marketing context", "who is our ideal customer", "write our ICP", "describe the product for marketing", "positioning doc", "what's our brand voice", "remember this about our customers", "log what we tried", "what have we learned from marketing", "we changed pricing, update the context", "update our growth notes", "summarize the business for the agent", "import my product-marketing.md", "start a growth doc", or before a first marketing, SEO, outreach or launch task when no context file exists. Works without a Revnu account.
revnu-get-listed
Get onto the third-party pages AI answers and search cite when buyers ask for the best tool in your category: "best X" roundups, directories, review sites, GitHub awesome lists, community threads and comparison pages. Finds which ones are cited, ranks them by fit and effort, and drafts each submission, PR or pitch by the target's own rules. Use when the user says "get us listed", "which directories should we submit to", "how do we get into best-of lists", "why does ChatGPT recommend competitors and not us", "get mentioned in AI answers", "submit to awesome lists", "get on G2", "where are our competitors listed", "pitch listicle authors", "find backlink opportunities", "launch directories", "get into roundups", "Product Hunt alternatives", "where should we be listed", "get cited by Perplexity". Never submits, pays or posts without a yes. Works without a Revnu account.
revnu-ai-readiness-audit
Audit whether your website gives ChatGPT, Perplexity, Claude, Gemini and Google's AI Overviews something worth quoting, and fix the pages that don't. Use when the user says or asks "is my site ready for AI search", "audit my site for AI answers", "AEO audit", "GEO audit", "why doesn't ChatGPT quote our pricing", "make our pages citable by AI", "do I need llms.txt", "does schema help with ChatGPT", "check our structured data", "is our content visible without JavaScript", "AI SEO audit", "optimize our homepage for AI answers", "LLM SEO check", "why does AI get our product wrong", "fix our site for AI Overviews". Checks fetchability and indexability, answers in the raw HTML, entity facts, schema (including JS-injected markup), headings, dates and llms.txt, then gives at most 10 prioritised fixes and edits the repo when asked. Works without a Revnu account.
proxy-troubleshooting
Diagnose residential proxy failures, with NodeMaven's gateway as the reference - 407 with correct credentials, 406, 410, 500, a connection that hangs, ERR_TUNNEL_CONNECTION_FAILED in a browser, Playwright or Puppeteer ignoring proxy credentials, a sticky session that changes IP, geo-targeting that is silently ignored, passwords with special characters, and unexpected traffic from headless Chrome. Use when a proxy connection fails, returns the wrong location, or costs more traffic than expected.