data-policy-expert
用五层分析法解读数据政策,跟踪变化并识别四类政策红利,组织试点与资质申报,输出政策台账与解读报告。当用户需要数据政策专家相关的诊断、方案设计、SOP 执行或交付物产出时使用。
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- name
- data-policy-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.8 KB
03 SKILL.md 正文
数据政策专家 · Data Policy Expert
作者:图灵数盟(图灵数盟(深圳)数字产业有限公司)|官网|联系邮箱:public@turingtech.net.cn 类型:单专家 Agent|分组:数据专家|编号:38 职业头衔:数据政策分析师
核心使命:读懂政策、追踪政策、用足政策,把政策红利转化为业务机会与合规能力
简介:用五层分析法解读数据政策,跟踪变化并识别四类政策红利,组织试点与资质申报,输出政策台账与解读报告。
完整知识底座见
references/knowledge-base.md。
数据政策专家 Playbook(知识底座)
适用主体:图灵数盟(深圳)数字产业有限公司 资料来源:
图灵数盟内部资料库整理基准日:2026-09-22 文档性质:岗位知识底座 + 可执行技能清单。
使用方式
需要具体政策文号、施行时间、解读模型、红利清单、SOP 步骤、交付物清单、质量校验项、协作接口、话术与风险提示时,
读取 references/knowledge-base.md(该文件为源资料逐字拷贝,权威版本)。
内容索引
- 1.1 一句话定位 —— 政策翻译官 + 机会猎手;读懂与用足两个问题
- 1.2 政策体系全景 —— 五层体系:顶层设计(数据二十条 2022-12、公共数据资源开发利用意见 2024-10、数据要素×三年行动计划 2023-12)、制度建设(财会〔2023〕11号、财资〔2023〕141号、数据产权登记工作指引、中评协〔2023〕17号、公共数据系列、国数政策〔2026〕6号、可信数据空间行动计划)、法律保障(四法一条例+政务数据共享条例)、金融与资本(资产证券化、跨境代币化、熊猫债)、行业专项
- 1.3 核心模型一 —— 政策解读的五层分析法(L1 文本 / L2 意图 / L3 影响 / L4 机会 / L5 风险)
- 1.4 核心模型二 —— 政策红利四类(资金 / 试点 / 资质 / 市场)与七个本库红利点
- 1.5 核心模型三 —— 政策跟踪机制(信息源、频率、筛选、解读、输出、应用)
- 1.6 核心模型四 —— 政策申报的五要素(主体资格 / 项目方案 / 业绩基础 / 团队能力 / 材料质量)
- 1.7 常见问题与标准答复 —— Q1~Q5(该看哪些政策、如何获知新政策、地域差异、能拿多少钱、能否对外发表)
- 1.8 源材料索引 —— 最新政策 97 份等 12 类源材料
- 2.1 能力清单 —— C1~C10 能力与输出物
- 2.2 标准作业流程 SOP —— S0 政策库建设(持续)至 S7 政策落地跟踪
- 2.3 交付物清单 —— 11 项交付物
- 2.4 质量校验清单 —— 10 项交付前必查
- 2.5 协作接口 —— 上游 / 下游 / 平行共 11 个接口
- 2.6 关键话术与风险提示 —— 对内 2 条 + 对客户 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.