菜单
Use when writing or improving data documentation for warehouse tables, metrics, dashboards, SQL jobs, data products, or handover materials so other people and agents can understand data purpose, grain, fields, logic, ownership, and usage constraints.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Use when writing a concise daily report, daily worklog, standup update, shift handoff, or end-of-day summary for data analysis, data development, BI, governance, or operations work.
Use when analyzing upstream and downstream impact for table changes, metric changes, field deprecation, pipeline migration, dashboard breakage, data governance review, or data asset dependency communication.
Use when planning integration with databases, BI tools, data platforms, APIs, workflow systems, storage services, or third-party tools, including connection requirements, API availability, auth strategy, configuration questions, and validation steps.
Use when planning or writing market research for a specific industry, product category, competitor set, business opportunity, user segment, or go-to-market question with structured evidence and clear assumptions.
Use when diagnosing business metric changes or anomalies such as GMV decline, conversion drop, retention loss, churn increase, revenue change, lead decline, or active user fluctuation with a structured root cause analysis plan.
Use when reviewing whether a BI dashboard, management dashboard, metric board, or data product page can support business decisions with clear metrics, trustworthy definitions, and actionable drill-down paths.
| name | data-doc-writer |
| description | Use when writing or improving data documentation for warehouse tables, metrics, dashboards, SQL jobs, data products, or handover materials so other people and agents can understand data purpose, grain, fields, logic, ownership, and usage constraints. |
把表结构、SQL、指标口径、看板说明或任务逻辑整理成可交接、可维护、可复用的数据文档。
这个 Skill 的重点不是写漂亮文案，而是降低数据资产使用和维护成本。
使用这个 Skill，当用户需要：
不要使用这个 Skill 处理：
table-design-advisorsql-reviewerdata-quality-rule-generatordata-analysis-report-writer最少输入：
推荐输入：
优先使用这些模板准备上下文：
如果文档面向特定业务域，建议补充行业上下文：
上下文不足时，输出可填写的文档骨架，并把缺失信息列为待补充项。
# 数据文档：对象名称
## 1. 基本信息
| 项目 | 内容 |
| --- | --- |
## 2. 业务用途
## 3. 数据粒度与更新策略
## 4. 字段字典 / 指标字典
| 字段/指标 | 类型 | 含义 | 口径/枚举 | 注意事项 |
| --- | --- | --- | --- | --- |
## 5. 生产逻辑
## 6. 上下游关系
## 7. 使用示例
## 8. 质量规则与 SLA
## 9. 常见误用与风险
## 10. 待补充信息
输出必须：
请用 data-doc-writer 为下面这张表写数据文档。
表名：dws_user_activation_1d
用途：统计 SaaS 产品新注册用户在注册后 7 天内的激活情况。
粒度：register_date + channel + user_id。
更新频率：每天 8 点产出上一日数据。
字段：
- register_date string 注册日期
- user_id string 用户 ID
- channel string 注册渠道
- create_workspace_flag int 是否创建工作区
- invite_member_flag int 是否邀请成员
- complete_task_flag int 是否完成核心任务
- activated_flag int 是否激活，任意两个 flag 为 1 即激活
下游：激活率看板、周报、增长实验分析。
请输出可交接的 Markdown 文档，并列出待补充信息。