[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77AAWEFAEZECDCM5PR5S8K3":3,"skill-same:01M77AAWEFAEZECDCM5PR5S8K3":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M77AAWEFAEZECDCM5PR5S8K3","data-classification",null,"用于数据分类、数据分级、数据分类分级任务。用户要求对单一数据字段名、字段列表、数据库表 SQL\u002FDDL 文件进行数据分类、数据分级或数据分类分级时使用；支持普通数据分类分级、GB\u002FT 43697-2024 通用数据分类分级、金融数据分类分级、JR\u002FT 0197-2020 金融数据安全级别，以及“通用数据标签 + 金融数据标签”的金融双标签体系。","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fd\u002Fdata-classification\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: data-classification\ndescription: 用于数据分类、数据分级、数据分类分级任务。用户要求对单一数据字段名、字段列表、数据库表 SQL\u002FDDL 文件进行数据分类、数据分级或数据分类分级时使用；支持普通数据分类分级、GB\u002FT 43697-2024 通用数据分类分级、金融数据分类分级、JR\u002FT 0197-2020 金融数据安全级别，以及“通用数据标签 + 金融数据标签”的金融双标签体系。\n---\n\n# Data Classification\n\n## Purpose\n\nClassify user-provided field names or SQL DDL into:\n\n1. **普通\u002F通用数据分类分级**: GB\u002FT 43697-2024 style category + level (`一般数据 \u002F 重要数据 \u002F 核心数据`).\n2. **金融数据双标签体系**: general label + JR\u002FT 0197-2020 financial label (`一级\u002F二级\u002F三级\u002F四级子类` + `最低安全级别1-5`).\n\nThis skill produces **classification suggestions**, not final regulatory determinations. Mark uncertain items for business-owner review.\n\n## Quick workflow\n\n1. Identify input type:\n   - Single field name: classify directly.\n   - SQL\u002FDDL file: extract table names, column names, types, and comments.\n2. Run the helper when useful:\n   ```bash\n   python3 skills\u002Fdata-classification\u002Fscripts\u002Fclassify_data.py --field \"customer_id\" --mode finance\n   python3 skills\u002Fdata-classification\u002Fscripts\u002Fclassify_data.py --sql path\u002Fto\u002Fschema.sql --mode finance --format markdown\n   ```\n3. Review financial rows against JR\u002FT 0197-2020 Appendix A before falling back to heuristics:\n   - `references\u002Fjrt0197-appendix-a-full.csv` is the machine-readable full Appendix A table.\n   - `references\u002Fjrt0197-appendix-a-compact.md` is the human-readable compact Appendix A table.\n   - `references\u002Ffinancial-dual-label.md` contains dual-label workflow and fallback heuristics.\n   - `references\u002Fgeneral-rules.md` contains GB\u002FT 43697-2024 logic.\n4. Return a field-level result that covers **every input field**. Do not replace the full field list with a summary.\n5. Choose output delivery by field count internally, but do not explain this threshold policy to the user:\n   - **≤20 fields**: output the complete field-level table inline in chat; do not create\u002Fattach files unless the user explicitly asks for an export\u002Ffile.\n   - **>20 fields**: save the complete field-level result as a CSV file, attach it with a `MEDIA:` line using the CSV file's absolute filesystem path, show the first 20 classified fields inline, and include a coverage statement in the message. Do not inline rows after the first 20. Never provide only a plain local path as the download method. Do not write the coverage statement into the CSV file itself.\n6. Run a coverage check before finalizing: compare parsed\u002Finput field count with classified output row count. If any field is missing, fix the output or explicitly mark the field as `[blocked: 未解析\u002F缺少字段信息]`.\n7. Ask for business context only if the field name\u002Fcomment is too ambiguous.\n\n## Output requirements\n\nFor a **single field**, include:\n\n- 字段名\n- 通用分类：行业领域、描述对象\u002F数据主体、内容类别\n- 通用分级：一般\u002F重要\u002F核心 + 理由\n- 置信度与需确认点\n- 金融标签（仅金融场景输出）：推荐的一级\u002F二级\u002F三级\u002F四级子类 + 最低安全级别\n- 候选金融标签（仅金融场景输出）：当字段可落入多个 JR\u002FT 分类时，一并列出候选项并说明推荐依据\n- 双标签结果（仅金融场景输出）：`通用标签 + 金融标签`\n\nFor a **SQL file\u002Ftable**, classify **all parsed columns from all tables**. Choose the delivery format internally and do not tell the user the threshold\u002Frouting rule.\n\n- **≤20 fields**: the complete field-level table inline. Do **not** create\u002Fattach files unless the user explicitly asks for an export\u002Ffile.\n- **>20 fields**: create a complete CSV result file. Return a concise completion note, attach the CSV with `MEDIA:\u003Cabsolute-csv-path>` on its own line so the UI can render a downloadable link, include the first 20 field-level rows inline, and include the coverage statement in the message. Do not inline rows after the first 20. Do not rely on a bare local path as the user's download link. Do not include the coverage statement as a row in the CSV file.\n\nDo not provide only a subset such as “core fields”, “sample rows”, or “summary table” unless the user explicitly asks for a summary.\n\nThe following output columns are **mandatory for every field and must be non-empty in all scenarios**:\n\n1. 字段名\n2. 通用分类\n3. 通用分级\n4. 置信度\n\nFor **financial data\u002Fscenarios only**, also include these mandatory non-empty columns:\n\n5. 推荐金融分类标签\n6. JR\u002FT最低级别\n7. 候选金融标签\n\nFor financial fields, match against `references\u002Fjrt0197-appendix-a-full.csv` or `references\u002Fjrt0197-appendix-a-compact.md` first. Use `financial-dual-label.md` heuristics only when Appendix A has no clear match or when field\u002Ftable context creates multiple reasonable candidates.\n\nFor **non-financial data**, do **not** output `推荐金融分类标签`、`JR\u002FT最低级别`、`候选金融标签`.\n\nRecommended non-financial table shape:\n\n| 表名 | 字段名 | 类型\u002F注释 | 通用分类 | 通用分级 | 置信度 | 依据\u002F备注 |\n|---|---|---|---|---|---:|---|\n\nRecommended financial table shape:\n\n| 表名 | 字段名 | 类型\u002F注释 | 通用分类 | 通用分级 | 推荐金融分类标签 | JR\u002FT最低级别 | 候选金融标签 | 双标签 | 置信度 | 依据\u002F备注 |\n|---|---|---|---|---|---|---:|---|---|---:|---|\n\nAfter the table, include a coverage line:\n\n`覆盖校验：输入\u002F解析字段 N 个，已分类 N 个，遗漏 0 个。`\n\nIf output is saved to a file, still include the coverage line in the message and an attachment. For CSV outputs, include `MEDIA:\u003Cabsolute-csv-path>` on its own line so the user can click\u002Fdownload directly; use the absolute path returned by the file-writing step, not a relative workspace path. File output is allowed for >20 fields as CSV, or whenever the user explicitly requests a file\u002Fexport. Do not write the coverage line into the CSV file. Do not explain that files are chosen because of the field-count threshold unless the user asks why.\n\n## Classification principles\n\n- Coverage is mandatory: every user-provided field\u002Fparsed SQL column must receive a classification row.\n- Use **就高从严**: if multiple rules match, choose the stricter level as the recommendation, list reasonable candidate labels, and explain why.\n- Treat field names alone as weak evidence; comments and table names improve confidence.\n- Do not infer `核心数据` from a field name alone unless the field clearly describes large-scale national\u002Fsecurity\u002Fcritical-infrastructure data. Usually mark as `需人工确认`.\n- `重要数据` usually requires scale, coverage, precision, or public\u002Fnational impact context. For isolated personal or organization fields, default to `一般数据` unless a law\u002Findustry rule says otherwise.\n- For financial data, Appendix A match takes precedence over broad keyword heuristics. JR\u002FT 0197 level is the **minimum security level**; business context may raise it.\n- For personal financial information, authentication credentials, biometric identifiers, account\u002Fpayment\u002Ftransaction data, and credit data should be handled conservatively.\n\n## Helper script notes\n\n`classify_data.py` is deterministic and heuristic. It is designed for first-pass tagging:\n\n- Inputs: `--field`, `--fields`, or `--sql`.\n- Modes: `general`, `finance`.\n- Formats: `markdown`, `json`, `csv`.\n- It parses common `CREATE TABLE` DDL and column comments.\n- Low confidence means the assistant should inspect context and possibly ask one focused follow-up.\n\n## References\n\n- `references\u002Fgeneral-rules.md`: compact GB\u002FT 43697-2024 classification\u002Fgrading rules.\n- `references\u002Ffinancial-dual-label.md`: financial dual-label workflow and fallback heuristics.\n- `references\u002Fjrt0197-appendix-a-compact.md`: compact human-readable JR\u002FT 0197-2020 Appendix A typical data grading table.\n- `references\u002Fjrt0197-appendix-a-full.csv`: full machine-readable JR\u002FT 0197-2020 Appendix A typical data grading table.\n","# Data Classification\n\n## Purpose\n\nClassify user-provided field names or SQL DDL into:\n\n1. **普通\u002F通用数据分类分级**: GB\u002FT 43697-2024 style category + level (`一般数据 \u002F 重要数据 \u002F 核心数据`).\n2. **金融数据双标签体系**: general label + JR\u002FT 0197-2020 financial label (`一级\u002F二级\u002F三级\u002F四级子类` + `最低安全级别1-5`).\n\nThis skill produces **classification suggestions**, not final regulatory determinations. Mark uncertain items for business-owner review.\n\n## Quick workflow\n\n1. Identify input type:\n   - Single field name: classify directly.\n   - SQL\u002FDDL file: extract table names, column names, types, and comments.\n2. Run the helper when useful:\n   ```bash\n   python3 skills\u002Fdata-classification\u002Fscripts\u002Fclassify_data.py --field \"customer_id\" --mode finance\n   python3 skills\u002Fdata-classification\u002Fscripts\u002Fclassify_data.py --sql path\u002Fto\u002Fschema.sql --mode finance --format markdown\n   ```\n3. Review financial rows against JR\u002FT 0197-2020 Appendix A before falling back to heuristics:\n   - `references\u002Fjrt0197-appendix-a-full.csv` is the machine-readable full Appendix A table.\n   - `references\u002Fjrt0197-appendix-a-compact.md` is the human-readable compact Appendix A table.\n   - `references\u002Ffinancial-dual-label.md` contains dual-label workflow and fallback heuristics.\n   - `references\u002Fgeneral-rules.md` contains GB\u002FT 43697-2024 logic.\n4. Return a field-level result that covers **every input field**. Do not replace the full field list with a summary.\n5. Choose output delivery by field count internally, but do not explain this threshold policy to the user:\n   - **≤20 fields**: output the complete field-level table inline in chat; do not create\u002Fattach files unless the user explicitly asks for an export\u002Ffile.\n   - **>20 fields**: save the complete field-level result as a CSV file, attach it with a `MEDIA:` line using the CSV file's absolute filesystem path, show the first 20 classified fields inline, and include a coverage statement in the message. Do not inline rows after the first 20. Never provide only a plain local path as the download method. Do not write the coverage statement into the CSV file itself.\n6. Run a coverage check before finalizing: compare parsed\u002Finput field count with classified output row count. If any field is missing, fix the output or explicitly mark the field as `[blocked: 未解析\u002F缺少字段信息]`.\n7. Ask for business context only if the field name\u002Fcomment is too ambiguous.\n\n## Output requirements\n\nFor a **single field**, include:\n\n- 字段名\n- 通用分类：行业领域、描述对象\u002F数据主体、内容类别\n- 通用分级：一般\u002F重要\u002F核心 + 理由\n- 置信度与需确认点\n- 金融标签（仅金融场景输出）：推荐的一级\u002F二级\u002F三级\u002F四级子类 + 最低安全级别\n- 候选金融标签（仅金融场景输出）：当字段可落入多个 JR\u002FT 分类时，一并列出候选项并说明推荐依据\n- 双标签结果（仅金融场景输出）：`通用标签 + 金融标签`\n\nFor a **SQL file\u002Ftable**, classify **all parsed columns from all tables**. Choose the delivery format internally and do not tell the user the threshold\u002Frouting rule.\n\n- **≤20 fields**: the complete field-level table inline. Do **not** create\u002Fattach files unless the user explicitly asks for an export\u002Ffile.\n- **>20 fields**: create a complete CSV result file. Return a concise completion note, attach the CSV with `MEDIA:\u003Cabsolute-csv-path>` on its own line so the UI can render a downloadable link, include the first 20 field-level rows inline, and include the coverage statement in the message. Do not inline rows after the first 20. Do not rely on a bare local path as the user's download link. Do not include the coverage statement as a row in the CSV file.\n\nDo not provide only a subset such as “core fields”, “sample rows”, or “summary table” unless the user explicitly asks for a summary.\n\nThe following output columns are **mandatory for every field and must be non-empty in all scenarios**:\n\n1. 字段名\n2. 通用分类\n3. 通用分级\n4. 置信度\n\nFor **financial data\u002Fscenarios only**, also include these mandatory non-empty columns:\n\n5. 推荐金融分类标签\n6. JR\u002FT最低级别\n7. 候选金融标签\n\nFor financial fields, match against `references\u002Fjrt0197-appendix-a-full.csv` or `references\u002Fjrt0197-appendix-a-compact.md` first. Use `financial-dual-label.md` heuristics only when Appendix A has no clear match or when field\u002Ftable context creates multiple reasonable candidates.\n\nFor **non-financial data**, do **not** output `推荐金融分类标签`、`JR\u002FT最低级别`、`候选金融标签`.\n\nRecommended non-financial table shape:\n\n| 表名 | 字段名 | 类型\u002F注释 | 通用分类 | 通用分级 | 置信度 | 依据\u002F备注 |\n|---|---|---|---|---|---:|---|\n\nRecommended financial table shape:\n\n| 表名 | 字段名 | 类型\u002F注释 | 通用分类 | 通用分级 | 推荐金融分类标签 | JR\u002FT最低级别 | 候选金融标签 | 双标签 | 置信度 | 依据\u002F备注 |\n|---|---|---|---|---|---|---:|---|---|---:|---|\n\nAfter the table, include a coverage line:\n\n`覆盖校验：输入\u002F解析字段 N 个，已分类 N 个，遗漏 0 个。`\n\nIf output is saved to a file, still include the coverage line in the message and an attachment. For CSV outputs, include `MEDIA:\u003Cabsolute-csv-path>` on its own line so the user can click\u002Fdownload directly; use the absolute path returned by the file-writing step, not a relative workspace path. File output is allowed for >20 fields as CSV, or whenever the user explicitly requests a file\u002Fexport. Do not write the coverage line into the CSV file. Do not explain that files are chosen because of the field-count threshold unless the user asks why.\n\n## Classification principles\n\n- Coverage is mandatory: every user-provided field\u002Fparsed SQL column must receive a classification row.\n- Use **就高从严**: if multiple rules match, choose the stricter level as the recommendation, list reasonable candidate labels, and explain why.\n- Treat field names alone as weak evidence; comments and table names improve confidence.\n- Do not infer `核心数据` from a field name alone unless the field clearly describes large-scale national\u002Fsecurity\u002Fcritical-infrastructure data. Usually mark as `需人工确认`.\n- `重要数据` usually requires scale, coverage, precision, or public\u002Fnational impact context. For isolated personal or organization fields, default to `一般数据` unless a law\u002Findustry rule says otherwise.\n- For financial data, Appendix A match takes precedence over broad keyword heuristics. JR\u002FT 0197 level is the **minimum security level**; business context may raise it.\n- For personal financial information, authentication credentials, biometric identifiers, account\u002Fpayment\u002Ftransaction data, and credit data should be handled conservatively.\n\n## Helper script notes\n\n`classify_data.py` is deterministic and heuristic. It is designed for first-pass tagging:\n\n- Inputs: `--field`, `--fields`, or `--sql`.\n- Modes: `general`, `finance`.\n- Formats: `markdown`, `json`, `csv`.\n- It parses common `CREATE TABLE` DDL and column comments.\n- Low confidence means the assistant should inspect context and possibly ask one focused follow-up.\n\n## References\n\n- `references\u002Fgeneral-rules.md`: compact GB\u002FT 43697-2024 classification\u002Fgrading rules.\n- `references\u002Ffinancial-dual-label.md`: financial dual-label workflow and fallback heuristics.\n- `references\u002Fjrt0197-appendix-a-compact.md`: compact human-readable JR\u002FT 0197-2020 Appendix A typical data grading table.\n- `references\u002Fjrt0197-appendix-a-full.csv`: full machine-readable JR\u002FT 0197-2020 Appendix A typical data grading table.\n",{"name":5,"description":7},"master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fd\u002Fdata-classification",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill data-classification",{"tool":39,"command":40},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill data-classification",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill data-classification","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fd\u002Fdata-classification\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]