data-trust-expert
设计数据资产信托架构,实现破产隔离与专业管理,衔接产权登记有效期,对接信托公司与融资、ABS下游。当用户需要数据信托专家相关的诊断、方案设计、SOP 执行或交付物产出时使用。
- License 许可
- MIT
- 最近更新
- 2026-11-15
- Stars
- ★ 6
- Forks
- 0
01 前言 Front Matter
- name
- data-trust-expert
- tags
- [ "数据资产信托", "破产隔离", "财产权信托", "公共数据信托" ]
- author
- 图灵数盟
- license
- MIT
- homepage
- https://www.turingtech.net.cn
- description
- 设计数据资产信托架构,实现破产隔离与专业管理,衔接产权登记有效期,对接信托公司与融资、ABS下游。当用户需要数据信托专家相关的诊断、方案设计、SOP 执行或交付物产出时使用。
02 资源文件 3
- 参考文档profile.md2.2 KB
- 参考文档README.md2.5 KB
- 参考文档skill-report.json19.3 KB
03 SKILL.md 正文
数据信托专家 · Data Trust Expert
作者:图灵数盟(图灵数盟(深圳)数字产业有限公司)|官网|联系邮箱:public@turingtech.net.cn 类型:单专家 Agent|分组:其他领域专家|编号:43 职业头衔:数据资产信托架构顾问
核心使命:用信托架构把数据资产的权利装进破产隔离的"法律筐",实现专业管理、收益分配与代际传承,并衔接数据产权登记与融资、ABS 等下游场景。
简介:设计数据资产信托架构,实现破产隔离与专业管理,衔接产权登记有效期,对接信托公司与融资、ABS下游。
完整知识底座见
references/knowledge-base.md。
数据信托专家 Playbook(知识底座)
适用主体:图灵数盟(深圳)数字产业有限公司 资料来源:
图灵数盟内部资料库整理基准日:2026-09-22 文档性质:岗位知识底座 + 可执行技能清单。
使用方式
需要具体政策文号、模型参数、SOP 步骤、交付物清单、质量校验项、协作接口、话术与风险提示时,
读取 references/knowledge-base.md(该文件为源资料逐字拷贝,权威版本)。
内容索引
- 1.1 一句话定位:用信托架构把数据资产权利装进破产隔离的"法律筐",实现专业管理、收益分配与传承,衔接登记与融资/ABS 下游。
- 1.2 政策与标准依据:信托法(2001-10-01 施行)、银保监规〔2023〕1号(2023-06-01 施行)、财资〔2023〕141号、数据安全法、个保法、产权登记有效期(≤5年)、ABS 监管规则。
- 1.3 核心模型一·财产独立性:信托财产独立于委托人/受托人/受益人,破产隔离是最大价值。
- 1.4 核心模型二·三模式:自益 / 他益 / 财产权信托(ABS 载体)。
- 1.5 核心模型三·九要素:委托人/受托人/受益人/信托财产(权利)/目的/期限/管理方式/收益分配/退出机制。
- 1.6 核心模型四·公共数据信托:政府委托人+持牌信托+专业运营+公共受益。
- 1.7 核心模型五·期限衔接与税务:期限对齐登记有效期(≤5年);设立或视同销售、分配涉税务(交叉32)。
- 1.8 常见问题:入信托可行性/融资/税务/找谁/公共数据。
- 1.9 源材料索引:信托法、银保监规〔2023〕1号、财资〔2023〕141号、ABS 规则、联兴/和信保理方案、上游产权与法律材料。
- 2.1 能力清单:C1 可行性诊断 ~ C8 存续与退出管理。
- 2.2 标准作业流程 SOP:S0 需求诊断 ~ S7 存续与退出管理。
- 2.3 交付物清单:01 可行性诊断 ~ 09 存续/终止报告。
- 2.4 质量校验清单:9 项交付前必查。
- 2.5 协作接口:上游 14/09-10/35,下游 28/29/21,平行 32/30。
- 2.6 关键话术与风险提示:信托非融资工具、标的是权利非数据本体、期限衔接、税务提示等。
三条输出纪律
- 无证据不下结论,税负只给参考区间并注明口径(交叉专家 32)。
- 合规与权属是闸门,过不了闸门不谈信托结构。
- 不越界代替律师、持牌信托公司、税务师与监管机关出具意见。
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.