[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78YH1C5KH9JTWGCTPXMVJSJ":3,"skill-same:01M78YH1C5KH9JTWGCTPXMVJSJ":58},{"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":35,"commitSha":36,"skillDirectory":37,"forksCount":38,"repositoryHtmlUrl":39,"repositoryHomepageUrl":6,"ownerHtmlUrl":40,"ownerBlogUrl":41,"ownerDescription":42,"updatedAt":43,"install":44,"resources":57},"01M78YH1C5KH9JTWGCTPXMVJSJ","clickhouse-data-handling",null,"Handle data lifecycle in ClickHouse — TTL expiration, data deletion (GDPR),\ncolumn-level encryption, and audit logging with real ClickHouse SQL.\nUse when implementing data retention, GDPR deletion requests,\nor managing sensitive data in ClickHouse.\nTrigger: \"clickhouse data retention\", \"clickhouse TTL\", \"clickhouse GDPR\",\n\"delete data clickhouse\", \"clickhouse data lifecycle\", \"clickhouse PII\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--clickhouse-pack--clickhouse-data-handling\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: clickhouse-data-handling\ndescription: |\n  Handle data lifecycle in ClickHouse — TTL expiration, data deletion (GDPR),\n  column-level encryption, and audit logging with real ClickHouse SQL.\n  Use when implementing data retention, GDPR deletion requests,\n  or managing sensitive data in ClickHouse.\n  Trigger: \"clickhouse data retention\", \"clickhouse TTL\", \"clickhouse GDPR\",\n  \"delete data clickhouse\", \"clickhouse data lifecycle\", \"clickhouse PII\".\nallowed-tools: Read, Write, Edit\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ntags: [saas, database, analytics, clickhouse, olap]\ncompatible-with: claude-code\n---\n\n# ClickHouse Data Handling\n\n## Overview\n\nManage the full data lifecycle in ClickHouse: TTL-based expiration, GDPR\u002FCCPA\ndeletion, data masking, partition management, and audit trails.\n\n## Prerequisites\n\n- ClickHouse tables with data (see `clickhouse-core-workflow-a`)\n- Understanding of your data retention requirements\n\n## Instructions\n\n### Step 1: TTL-Based Data Expiration\n\n```sql\n-- Add TTL to expire data automatically\nCREATE TABLE analytics.events (\n    event_id    UUID DEFAULT generateUUIDv4(),\n    event_type  LowCardinality(String),\n    user_id     UInt64,\n    properties  String CODEC(ZSTD(3)),\n    created_at  DateTime DEFAULT now()\n)\nENGINE = MergeTree()\nORDER BY (event_type, created_at)\nPARTITION BY toYYYYMM(created_at)\nTTL created_at + INTERVAL 90 DAY;    -- Auto-delete after 90 days\n\n-- Add TTL to existing table\nALTER TABLE analytics.events\n    MODIFY TTL created_at + INTERVAL 90 DAY;\n\n-- Tiered storage TTL (hot → cold → delete)\nALTER TABLE analytics.events\n    MODIFY TTL\n        created_at + INTERVAL 7 DAY TO VOLUME 'hot',\n        created_at + INTERVAL 30 DAY TO VOLUME 'cold',\n        created_at + INTERVAL 365 DAY DELETE;\n\n-- Column-level TTL (null out PII after 30 days, keep the row)\nALTER TABLE analytics.events\n    MODIFY COLUMN email String DEFAULT ''\n    TTL created_at + INTERVAL 30 DAY;\n\n-- Force TTL cleanup now (normally runs during merges)\nOPTIMIZE TABLE analytics.events FINAL;\n```\n\n### Step 2: Data Deletion for GDPR\u002FCCPA\n\n```sql\n-- Option A: Lightweight DELETE (ClickHouse 23.3+)\n-- Marks rows as deleted without rewriting parts immediately\nDELETE FROM analytics.events WHERE user_id = 42;\n\n-- Option B: ALTER TABLE DELETE (mutation — rewrites parts in background)\nALTER TABLE analytics.events DELETE WHERE user_id = 42;\n\n-- Check mutation progress\nSELECT\n    database, table, mutation_id, command,\n    is_done, parts_to_do, create_time\nFROM system.mutations\nWHERE NOT is_done\nORDER BY create_time DESC;\n\n-- Option C: Drop entire partitions (fastest for bulk deletion)\n-- First, check what partitions exist\nSELECT partition, count() AS parts, sum(rows) AS rows,\n       min(min_time) AS from_time, max(max_time) AS to_time\nFROM system.parts\nWHERE database = 'analytics' AND table = 'events' AND active\nGROUP BY partition ORDER BY partition;\n\nALTER TABLE analytics.events DROP PARTITION '202401';\n```\n\n**Important notes on ClickHouse deletions:**\n- `DELETE FROM` is lightweight but still creates mutations internally\n- Mutations rewrite data parts in the background — not instant\n- For GDPR compliance, use `ALTER TABLE DELETE` and verify via `system.mutations`\n- Partitioned data is fastest to bulk-delete via `DROP PARTITION`\n\n### Step 3: Data Masking and Anonymization\n\n```sql\n-- Create a view that masks PII for analyst access\nCREATE VIEW analytics.events_masked AS\nSELECT\n    event_id,\n    event_type,\n    sipHash64(user_id) AS user_id_hash,    -- One-way hash\n    JSONExtractString(properties, 'url') AS url,  -- Extract safe fields only\n    -- Mask email: show domain only\n    concat('***@', substringAfter(email, '@')) AS masked_email,\n    created_at\nFROM analytics.events;\n\n-- Row-level masking with dictionaries\nCREATE DICTIONARY analytics.pii_allowlist (\n    user_id UInt64,\n    can_see_pii UInt8\n)\nPRIMARY KEY user_id\nSOURCE(CLICKHOUSE(TABLE 'pii_allowlist'))\nLIFETIME(MIN 300 MAX 600)\nLAYOUT(FLAT());\n```\n\n### Step 4: User Data Export (DSAR)\n\n```typescript\nimport { createClient } from '@clickhouse\u002Fclient';\n\nasync function exportUserData(userId: number): Promise\u003CRecord\u003Cstring, unknown[]>> {\n  const client = createClient({ url: process.env.CLICKHOUSE_HOST! });\n\n  \u002F\u002F Export all user data from all tables\n  const tables = ['events', 'sessions', 'purchases'];\n  const result: Record\u003Cstring, unknown[]> = {};\n\n  for (const table of tables) {\n    const rs = await client.query({\n      query: `SELECT * FROM analytics.${table} WHERE user_id = {uid:UInt64}`,\n      query_params: { uid: userId },\n      format: 'JSONEachRow',\n    });\n    result[table] = await rs.json();\n  }\n\n  return result;\n}\n\n\u002F\u002F GDPR: Delete all user data\nasync function deleteUserData(userId: number): Promise\u003Cvoid> {\n  const client = createClient({ url: process.env.CLICKHOUSE_HOST! });\n  const tables = ['events', 'sessions', 'purchases'];\n\n  for (const table of tables) {\n    await client.command({\n      query: `ALTER TABLE analytics.${table} DELETE WHERE user_id = {uid:UInt64}`,\n      query_params: { uid: userId },\n    });\n  }\n\n  \u002F\u002F Log the deletion for compliance audit trail\n  await client.insert({\n    table: 'analytics.gdpr_audit_log',\n    values: [{\n      user_id: userId,\n      action: 'DELETE_ALL',\n      tables_affected: tables.join(','),\n      requested_at: new Date().toISOString().replace('T', ' ').slice(0, 19),\n    }],\n    format: 'JSONEachRow',\n  });\n}\n```\n\n### Step 5: Audit Trail Table\n\n```sql\n-- Immutable audit log (no deletes, no TTL)\nCREATE TABLE analytics.audit_log (\n    log_id      UUID DEFAULT generateUUIDv4(),\n    action      LowCardinality(String),  -- 'query', 'delete', 'export', 'schema_change'\n    actor       String,                   -- User or service name\n    target      String,                   -- Table or resource\n    details     String CODEC(ZSTD(3)),    -- JSON details\n    ip_address  IPv4,\n    logged_at   DateTime DEFAULT now()\n)\nENGINE = MergeTree()\nORDER BY (action, logged_at)\nPARTITION BY toYYYYMM(logged_at);\n-- No TTL — audit logs must be retained\n\n-- Query audit trail\nSELECT logged_at, actor, action, target, details\nFROM analytics.audit_log\nWHERE action = 'DELETE_ALL'\nORDER BY logged_at DESC\nLIMIT 50;\n```\n\n### Step 6: Retention Monitoring\n\n```sql\n-- Data retention overview\nSELECT\n    database, table,\n    result_ttl_expression AS ttl,\n    formatReadableSize(sum(bytes_on_disk)) AS size,\n    min(p.min_time) AS oldest_data,\n    max(p.max_time) AS newest_data,\n    dateDiff('day', min(p.min_time), max(p.max_time)) AS days_span\nFROM system.tables t\nLEFT JOIN system.parts p ON t.database = p.database AND t.name = p.table AND p.active\nWHERE t.database = 'analytics'\nGROUP BY database, table, result_ttl_expression\nORDER BY sum(bytes_on_disk) DESC;\n\n-- Find tables missing TTL\nSELECT database, name AS table, engine\nFROM system.tables\nWHERE database = 'analytics'\n  AND engine LIKE '%MergeTree%'\n  AND result_ttl_expression = '';\n```\n\n## Data Classification\n\n| Category | Examples | Handling in ClickHouse |\n|----------|----------|------------------------|\n| PII | Email, name, IP | Column-level TTL, masking views, deletion support |\n| Sensitive | API keys, tokens | Never store in ClickHouse — use secret managers |\n| Business | Event counts, metrics | Standard TTL, aggregate for long-term retention |\n| Audit | Access logs | No TTL, immutable, partitioned by month |\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Mutation stuck | Large table rewrite | Check `system.mutations`, cancel if needed |\n| TTL not expiring | No merges running | `OPTIMIZE TABLE ... FINAL` to force |\n| DELETE not working | Old ClickHouse version | Use `ALTER TABLE DELETE` (mutation) |\n| Export timeout | Too much user data | Add LIMIT or export in batches |\n\n## Resources\n\n- [TTL for Data Management](https:\u002F\u002Fclickhouse.com\u002Fdocs\u002Fengines\u002Ftable-engines\u002Fmergetree-family\u002Fmergetree#table_engine-mergetree-ttl)\n- [DELETE Statement](https:\u002F\u002Fclickhouse.com\u002Fdocs\u002Fsql-reference\u002Fstatements\u002Fdelete)\n- [Mutations](https:\u002F\u002Fclickhouse.com\u002Fdocs\u002Fguides\u002Fdeveloper\u002Fmutations)\n\n## Next Steps\n\nFor role-based access control, see `clickhouse-enterprise-rbac`.\n","# ClickHouse Data Handling\n\n## Overview\n\nManage the full data lifecycle in ClickHouse: TTL-based expiration, GDPR\u002FCCPA\ndeletion, data masking, partition management, and audit trails.\n\n## Prerequisites\n\n- ClickHouse tables with data (see `clickhouse-core-workflow-a`)\n- Understanding of your data retention requirements\n\n## Instructions\n\n### Step 1: TTL-Based Data Expiration\n\n```sql\n-- Add TTL to expire data automatically\nCREATE TABLE analytics.events (\n    event_id    UUID DEFAULT generateUUIDv4(),\n    event_type  LowCardinality(String),\n    user_id     UInt64,\n    properties  String CODEC(ZSTD(3)),\n    created_at  DateTime DEFAULT now()\n)\nENGINE = MergeTree()\nORDER BY (event_type, created_at)\nPARTITION BY toYYYYMM(created_at)\nTTL created_at + INTERVAL 90 DAY;    -- Auto-delete after 90 days\n\n-- Add TTL to existing table\nALTER TABLE analytics.events\n    MODIFY TTL created_at + INTERVAL 90 DAY;\n\n-- Tiered storage TTL (hot → cold → delete)\nALTER TABLE analytics.events\n    MODIFY TTL\n        created_at + INTERVAL 7 DAY TO VOLUME 'hot',\n        created_at + INTERVAL 30 DAY TO VOLUME 'cold',\n        created_at + INTERVAL 365 DAY DELETE;\n\n-- Column-level TTL (null out PII after 30 days, keep the row)\nALTER TABLE analytics.events\n    MODIFY COLUMN email String DEFAULT ''\n    TTL created_at + INTERVAL 30 DAY;\n\n-- Force TTL cleanup now (normally runs during merges)\nOPTIMIZE TABLE analytics.events FINAL;\n```\n\n### Step 2: Data Deletion for GDPR\u002FCCPA\n\n```sql\n-- Option A: Lightweight DELETE (ClickHouse 23.3+)\n-- Marks rows as deleted without rewriting parts immediately\nDELETE FROM analytics.events WHERE user_id = 42;\n\n-- Option B: ALTER TABLE DELETE (mutation — rewrites parts in background)\nALTER TABLE analytics.events DELETE WHERE user_id = 42;\n\n-- Check mutation progress\nSELECT\n    database, table, mutation_id, command,\n    is_done, parts_to_do, create_time\nFROM system.mutations\nWHERE NOT is_done\nORDER BY create_time DESC;\n\n-- Option C: Drop entire partitions (fastest for bulk deletion)\n-- First, check what partitions exist\nSELECT partition, count() AS parts, sum(rows) AS rows,\n       min(min_time) AS from_time, max(max_time) AS to_time\nFROM system.parts\nWHERE database = 'analytics' AND table = 'events' AND active\nGROUP BY partition ORDER BY partition;\n\nALTER TABLE analytics.events DROP PARTITION '202401';\n```\n\n**Important notes on ClickHouse deletions:**\n- `DELETE FROM` is lightweight but still creates mutations internally\n- Mutations rewrite data parts in the background — not instant\n- For GDPR compliance, use `ALTER TABLE DELETE` and verify via `system.mutations`\n- Partitioned data is fastest to bulk-delete via `DROP PARTITION`\n\n### Step 3: Data Masking and Anonymization\n\n```sql\n-- Create a view that masks PII for analyst access\nCREATE VIEW analytics.events_masked AS\nSELECT\n    event_id,\n    event_type,\n    sipHash64(user_id) AS user_id_hash,    -- One-way hash\n    JSONExtractString(properties, 'url') AS url,  -- Extract safe fields only\n    -- Mask email: show domain only\n    concat('***@', substringAfter(email, '@')) AS masked_email,\n    created_at\nFROM analytics.events;\n\n-- Row-level masking with dictionaries\nCREATE DICTIONARY analytics.pii_allowlist (\n    user_id UInt64,\n    can_see_pii UInt8\n)\nPRIMARY KEY user_id\nSOURCE(CLICKHOUSE(TABLE 'pii_allowlist'))\nLIFETIME(MIN 300 MAX 600)\nLAYOUT(FLAT());\n```\n\n### Step 4: User Data Export (DSAR)\n\n```typescript\nimport { createClient } from '@clickhouse\u002Fclient';\n\nasync function exportUserData(userId: number): Promise\u003CRecord\u003Cstring, unknown[]>> {\n  const client = createClient({ url: process.env.CLICKHOUSE_HOST! });\n\n  \u002F\u002F Export all user data from all tables\n  const tables = ['events', 'sessions', 'purchases'];\n  const result: Record\u003Cstring, unknown[]> = {};\n\n  for (const table of tables) {\n    const rs = await client.query({\n      query: `SELECT * FROM analytics.${table} WHERE user_id = {uid:UInt64}`,\n      query_params: { uid: userId },\n      format: 'JSONEachRow',\n    });\n    result[table] = await rs.json();\n  }\n\n  return result;\n}\n\n\u002F\u002F GDPR: Delete all user data\nasync function deleteUserData(userId: number): Promise\u003Cvoid> {\n  const client = createClient({ url: process.env.CLICKHOUSE_HOST! });\n  const tables = ['events', 'sessions', 'purchases'];\n\n  for (const table of tables) {\n    await client.command({\n      query: `ALTER TABLE analytics.${table} DELETE WHERE user_id = {uid:UInt64}`,\n      query_params: { uid: userId },\n    });\n  }\n\n  \u002F\u002F Log the deletion for compliance audit trail\n  await client.insert({\n    table: 'analytics.gdpr_audit_log',\n    values: [{\n      user_id: userId,\n      action: 'DELETE_ALL',\n      tables_affected: tables.join(','),\n      requested_at: new Date().toISOString().replace('T', ' ').slice(0, 19),\n    }],\n    format: 'JSONEachRow',\n  });\n}\n```\n\n### Step 5: Audit Trail Table\n\n```sql\n-- Immutable audit log (no deletes, no TTL)\nCREATE TABLE analytics.audit_log (\n    log_id      UUID DEFAULT generateUUIDv4(),\n    action      LowCardinality(String),  -- 'query', 'delete', 'export', 'schema_change'\n    actor       String,                   -- User or service name\n    target      String,                   -- Table or resource\n    details     String CODEC(ZSTD(3)),    -- JSON details\n    ip_address  IPv4,\n    logged_at   DateTime DEFAULT now()\n)\nENGINE = MergeTree()\nORDER BY (action, logged_at)\nPARTITION BY toYYYYMM(logged_at);\n-- No TTL — audit logs must be retained\n\n-- Query audit trail\nSELECT logged_at, actor, action, target, details\nFROM analytics.audit_log\nWHERE action = 'DELETE_ALL'\nORDER BY logged_at DESC\nLIMIT 50;\n```\n\n### Step 6: Retention Monitoring\n\n```sql\n-- Data retention overview\nSELECT\n    database, table,\n    result_ttl_expression AS ttl,\n    formatReadableSize(sum(bytes_on_disk)) AS size,\n    min(p.min_time) AS oldest_data,\n    max(p.max_time) AS newest_data,\n    dateDiff('day', min(p.min_time), max(p.max_time)) AS days_span\nFROM system.tables t\nLEFT JOIN system.parts p ON t.database = p.database AND t.name = p.table AND p.active\nWHERE t.database = 'analytics'\nGROUP BY database, table, result_ttl_expression\nORDER BY sum(bytes_on_disk) DESC;\n\n-- Find tables missing TTL\nSELECT database, name AS table, engine\nFROM system.tables\nWHERE database = 'analytics'\n  AND engine LIKE '%MergeTree%'\n  AND result_ttl_expression = '';\n```\n\n## Data Classification\n\n| Category | Examples | Handling in ClickHouse |\n|----------|----------|------------------------|\n| PII | Email, name, IP | Column-level TTL, masking views, deletion support |\n| Sensitive | API keys, tokens | Never store in ClickHouse — use secret managers |\n| Business | Event counts, metrics | Standard TTL, aggregate for long-term retention |\n| Audit | Access logs | No TTL, immutable, partitioned by month |\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Mutation stuck | Large table rewrite | Check `system.mutations`, cancel if needed |\n| TTL not expiring | No merges running | `OPTIMIZE TABLE ... FINAL` to force |\n| DELETE not working | Old ClickHouse version | Use `ALTER TABLE DELETE` (mutation) |\n| Export timeout | Too much user data | Add LIMIT or export in batches |\n\n## Resources\n\n- [TTL for Data Management](https:\u002F\u002Fclickhouse.com\u002Fdocs\u002Fengines\u002Ftable-engines\u002Fmergetree-family\u002Fmergetree#table_engine-mergetree-ttl)\n- [DELETE Statement](https:\u002F\u002Fclickhouse.com\u002Fdocs\u002Fsql-reference\u002Fstatements\u002Fdelete)\n- [Mutations](https:\u002F\u002Fclickhouse.com\u002Fdocs\u002Fguides\u002Fdeveloper\u002Fmutations)\n\n## Next Steps\n\nFor role-based access control, see `clickhouse-enterprise-rbac`.\n",{"name":5,"tags":24,"author":30,"license":15,"version":31,"description":32,"allowed-tools":33,"compatible-with":34},[25,26,27,28,29],"saas","database","analytics","clickhouse","olap","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Handle data lifecycle in ClickHouse — TTL expiration, data deletion (GDPR),\ncolumn-level encryption, and audit logging with real ClickHouse SQL.\nUse when implementing data retention, GDPR deletion requests,\nor managing sensitive data in ClickHouse.\nTrigger: \"clickhouse data retention\", \"clickhouse TTL\", \"clickhouse GDPR\",\n\"delete data clickhouse\", \"clickhouse data lifecycle\", \"clickhouse PII\".\n","Read, Write, Edit","claude-code","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--clickhouse-pack--clickhouse-data-handling",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":45,"prompt":55,"zipAvailable":56},[46,49,52],{"tool":47,"command":48},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill clickhouse-data-handling",{"tool":50,"command":51},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill clickhouse-data-handling",{"tool":53,"command":54},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill clickhouse-data-handling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--clickhouse-pack--clickhouse-data-handling\u002FSKILL.md",true,[],[59,66,73,80,87,95],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":91,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]