[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7970GPHDD2T8PBZP71GQ2BJ":3,"skill-same:01M7970GPHDD2T8PBZP71GQ2BJ":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},"01M7970GPHDD2T8PBZP71GQ2BJ","vercel-data-handling",null,"Implement data handling, PII protection, and GDPR\u002FCCPA compliance for Vercel deployments.\nUse when handling sensitive data in serverless functions, implementing data redaction,\nor ensuring privacy compliance on Vercel.\nTrigger with phrases like \"vercel data\", \"vercel PII\",\n\"vercel GDPR\", \"vercel data retention\", \"vercel privacy\", \"vercel compliance\".","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--vercel-pack--vercel-data-handling\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vercel-data-handling\ndescription: |\n  Implement data handling, PII protection, and GDPR\u002FCCPA compliance for Vercel deployments.\n  Use when handling sensitive data in serverless functions, implementing data redaction,\n  or ensuring privacy compliance on Vercel.\n  Trigger with phrases like \"vercel data\", \"vercel PII\",\n  \"vercel GDPR\", \"vercel data retention\", \"vercel privacy\", \"vercel compliance\".\nallowed-tools: Read, Write, Edit\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, vercel, compliance, privacy, security]\n---\n# Vercel Data Handling\n\n## Overview\nHandle sensitive data correctly on Vercel: PII redaction in logs, GDPR-compliant data processing in serverless functions, secure cookie management, and data residency configuration. Covers both what Vercel stores and what your application should protect.\n\n## Prerequisites\n- Understanding of GDPR\u002FCCPA requirements\n- Vercel Pro or Enterprise (for data residency options)\n- Logging infrastructure with PII awareness\n\n## Instructions\n\n### Step 1: Understand What Vercel Stores\n\n| Data Type | Where | Retention | Control |\n|-----------|-------|-----------|---------|\n| Runtime logs | Vercel servers | 1hr (free), 30d (Plus) | Log drains |\n| Build logs | Vercel servers | 30 days | Automatic |\n| Analytics data | Vercel | Aggregated, no PII | Disable in dashboard |\n| Deployment source | Vercel | Until deleted | Manual deletion |\n| Environment variables | Vercel (encrypted) | Until deleted | Scoped access |\n\n### Step 2: PII Redaction in Logs\n```typescript\n\u002F\u002F lib\u002Fredact.ts — redact PII before logging\nconst PII_PATTERNS: [RegExp, string][] = [\n  [\u002F\\b[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\\.[A-Za-z]{2,}\\b\u002Fg, '[EMAIL]'],\n  [\u002F\\b\\d{3}[-.]?\\d{3}[-.]?\\d{4}\\b\u002Fg, '[PHONE]'],\n  [\u002F\\b\\d{3}-\\d{2}-\\d{4}\\b\u002Fg, '[SSN]'],\n  [\u002F\\b\\d{4}[\\s-]?\\d{4}[\\s-]?\\d{4}[\\s-]?\\d{4}\\b\u002Fg, '[CARD]'],\n  [\u002F\\b(?:Bearer|token|key|secret|password)\\s*[:=]\\s*\\S+\u002Fgi, '[CREDENTIAL]'],\n];\n\nexport function redact(text: string): string {\n  let result = text;\n  for (const [pattern, replacement] of PII_PATTERNS) {\n    result = result.replace(pattern, replacement);\n  }\n  return result;\n}\n\n\u002F\u002F Usage — always redact before console.log\nimport { redact } from '@\u002Flib\u002Fredact';\n\nexport async function POST(request: Request) {\n  const body = await request.json();\n  console.log('Request received:', redact(JSON.stringify(body)));\n  \u002F\u002F Process safely...\n}\n```\n\n### Step 3: GDPR-Compliant API Routes\n```typescript\n\u002F\u002F api\u002Fusers\u002F[id]\u002Froute.ts — data subject request handlers\nimport { NextRequest, NextResponse } from 'next\u002Fserver';\nimport { db } from '@\u002Flib\u002Fdb';\n\n\u002F\u002F Right to Access (GDPR Art. 15)\nexport async function GET(\n  request: NextRequest,\n  { params }: { params: { id: string } }\n) {\n  const user = await db.user.findUnique({\n    where: { id: params.id },\n    include: { posts: true, preferences: true },\n  });\n\n  if (!user) return NextResponse.json({ error: 'Not found' }, { status: 404 });\n\n  return NextResponse.json({\n    personalData: {\n      name: user.name,\n      email: user.email,\n      createdAt: user.createdAt,\n      posts: user.posts,\n      preferences: user.preferences,\n    },\n    exportedAt: new Date().toISOString(),\n  });\n}\n\n\u002F\u002F Right to Erasure (GDPR Art. 17)\nexport async function DELETE(\n  request: NextRequest,\n  { params }: { params: { id: string } }\n) {\n  \u002F\u002F Soft delete — anonymize instead of hard delete for audit trail\n  await db.user.update({\n    where: { id: params.id },\n    data: {\n      email: `deleted-${params.id}@redacted.local`,\n      name: '[DELETED]',\n      deletedAt: new Date(),\n    },\n  });\n\n  \u002F\u002F Also delete from log drain provider if applicable\n  console.log(`GDPR deletion completed for user ${params.id}`);\n  return NextResponse.json({ deleted: true });\n}\n```\n\n### Step 4: Secure Cookie Management\n```typescript\n\u002F\u002F lib\u002Fcookies.ts — GDPR-aware cookie handling\nimport { cookies } from 'next\u002Fheaders';\n\nexport function setSessionCookie(token: string): void {\n  cookies().set('session', token, {\n    httpOnly: true,       \u002F\u002F Not accessible via JavaScript\n    secure: true,         \u002F\u002F HTTPS only\n    sameSite: 'lax',      \u002F\u002F CSRF protection\n    maxAge: 60 * 60 * 24, \u002F\u002F 24 hours\n    path: '\u002F',\n  });\n}\n\nexport function setConsentCookie(consent: Record\u003Cstring, boolean>): void {\n  cookies().set('consent', JSON.stringify(consent), {\n    httpOnly: false,  \u002F\u002F Needs client-side access\n    secure: true,\n    sameSite: 'lax',\n    maxAge: 60 * 60 * 24 * 365, \u002F\u002F 1 year\n    path: '\u002F',\n  });\n}\n\n\u002F\u002F Middleware — block analytics if consent not given\nexport function middleware(request: Request) {\n  const consent = request.headers.get('cookie')?.includes('consent');\n  if (!consent) {\n    \u002F\u002F Strip analytics query params, skip tracking middleware\n  }\n}\n```\n\n### Step 5: Data Residency Configuration\nVercel allows configuring where your serverless functions execute:\n\n```json\n\u002F\u002F vercel.json — restrict function execution to EU regions\n{\n  \"regions\": [\"cdg1\", \"lhr1\"],\n  \"functions\": {\n    \"api\u002F**\u002F*.ts\": {\n      \"regions\": [\"cdg1\"]\n    }\n  }\n}\n```\n\nEU regions for GDPR data residency:\n| Region | Location | Code |\n|--------|----------|------|\n| Paris | France | `cdg1` |\n| London | UK | `lhr1` |\n| Frankfurt | Germany | `fra1` |\n\n### Step 6: Audit Logging\n```typescript\n\u002F\u002F lib\u002Faudit-log.ts — track data access for compliance\ninterface AuditEntry {\n  action: 'read' | 'create' | 'update' | 'delete' | 'export';\n  resource: string;\n  resourceId: string;\n  userId: string;\n  ip: string;\n  timestamp: string;\n}\n\nexport async function auditLog(entry: Omit\u003CAuditEntry, 'timestamp'>): Promise\u003Cvoid> {\n  const record: AuditEntry = {\n    ...entry,\n    timestamp: new Date().toISOString(),\n  };\n\n  \u002F\u002F Write to database audit table\n  await db.auditLog.create({ data: record });\n\n  \u002F\u002F Also log for log drain capture (structured JSON)\n  console.log(JSON.stringify({ type: 'audit', ...record }));\n}\n\n\u002F\u002F Usage in API route:\nexport async function GET(request: NextRequest) {\n  await auditLog({\n    action: 'read',\n    resource: 'user',\n    resourceId: params.id,\n    userId: session.userId,\n    ip: request.headers.get('x-forwarded-for') ?? 'unknown',\n  });\n}\n```\n\n## Data Classification Guide\n\n| Category | Examples | Handling on Vercel |\n|----------|----------|-------------------|\n| PII | Email, name, phone, IP | Redact from logs, encrypt at rest |\n| Secrets | API keys, tokens, passwords | Use `type: sensitive` env vars, never log |\n| Financial | Card numbers, bank info | Never process in functions — use Stripe\u002Fpayment provider |\n| Health | Medical records | Requires BAA — contact Vercel Enterprise |\n| Business | Metrics, usage stats | Aggregate before logging |\n\n## Output\n- PII redaction applied to all log output\n- GDPR data subject request endpoints implemented\n- Secure cookie handling with consent management\n- Data residency configured via function regions\n- Audit logging for compliance trail\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| PII in Vercel logs | Not redacting before console.log | Use `redact()` wrapper on all log calls |\n| GDPR data request timeout | Large data export in function | Paginate or use background processing |\n| Cookies not secure | Missing `secure: true` flag | Always set httpOnly and secure flags |\n| Function running in wrong region | Region not set in vercel.json | Specify `regions` per function |\n\n## Resources\n- [Vercel Privacy Policy](https:\u002F\u002Fvercel.com\u002Flegal\u002Fprivacy-policy)\n- [Vercel Data Processing Agreement](https:\u002F\u002Fvercel.com\u002Flegal\u002Fdpa)\n- [GDPR Overview](https:\u002F\u002Fgdpr.eu\u002F)\n- [Vercel Function Regions](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Fconfiguring-functions)\n- [Vercel Security](https:\u002F\u002Fvercel.com\u002Fsecurity)\n\n## Next Steps\nFor enterprise RBAC, see `vercel-enterprise-rbac`.\n","# Vercel Data Handling\n\n## Overview\nHandle sensitive data correctly on Vercel: PII redaction in logs, GDPR-compliant data processing in serverless functions, secure cookie management, and data residency configuration. Covers both what Vercel stores and what your application should protect.\n\n## Prerequisites\n- Understanding of GDPR\u002FCCPA requirements\n- Vercel Pro or Enterprise (for data residency options)\n- Logging infrastructure with PII awareness\n\n## Instructions\n\n### Step 1: Understand What Vercel Stores\n\n| Data Type | Where | Retention | Control |\n|-----------|-------|-----------|---------|\n| Runtime logs | Vercel servers | 1hr (free), 30d (Plus) | Log drains |\n| Build logs | Vercel servers | 30 days | Automatic |\n| Analytics data | Vercel | Aggregated, no PII | Disable in dashboard |\n| Deployment source | Vercel | Until deleted | Manual deletion |\n| Environment variables | Vercel (encrypted) | Until deleted | Scoped access |\n\n### Step 2: PII Redaction in Logs\n```typescript\n\u002F\u002F lib\u002Fredact.ts — redact PII before logging\nconst PII_PATTERNS: [RegExp, string][] = [\n  [\u002F\\b[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\\.[A-Za-z]{2,}\\b\u002Fg, '[EMAIL]'],\n  [\u002F\\b\\d{3}[-.]?\\d{3}[-.]?\\d{4}\\b\u002Fg, '[PHONE]'],\n  [\u002F\\b\\d{3}-\\d{2}-\\d{4}\\b\u002Fg, '[SSN]'],\n  [\u002F\\b\\d{4}[\\s-]?\\d{4}[\\s-]?\\d{4}[\\s-]?\\d{4}\\b\u002Fg, '[CARD]'],\n  [\u002F\\b(?:Bearer|token|key|secret|password)\\s*[:=]\\s*\\S+\u002Fgi, '[CREDENTIAL]'],\n];\n\nexport function redact(text: string): string {\n  let result = text;\n  for (const [pattern, replacement] of PII_PATTERNS) {\n    result = result.replace(pattern, replacement);\n  }\n  return result;\n}\n\n\u002F\u002F Usage — always redact before console.log\nimport { redact } from '@\u002Flib\u002Fredact';\n\nexport async function POST(request: Request) {\n  const body = await request.json();\n  console.log('Request received:', redact(JSON.stringify(body)));\n  \u002F\u002F Process safely...\n}\n```\n\n### Step 3: GDPR-Compliant API Routes\n```typescript\n\u002F\u002F api\u002Fusers\u002F[id]\u002Froute.ts — data subject request handlers\nimport { NextRequest, NextResponse } from 'next\u002Fserver';\nimport { db } from '@\u002Flib\u002Fdb';\n\n\u002F\u002F Right to Access (GDPR Art. 15)\nexport async function GET(\n  request: NextRequest,\n  { params }: { params: { id: string } }\n) {\n  const user = await db.user.findUnique({\n    where: { id: params.id },\n    include: { posts: true, preferences: true },\n  });\n\n  if (!user) return NextResponse.json({ error: 'Not found' }, { status: 404 });\n\n  return NextResponse.json({\n    personalData: {\n      name: user.name,\n      email: user.email,\n      createdAt: user.createdAt,\n      posts: user.posts,\n      preferences: user.preferences,\n    },\n    exportedAt: new Date().toISOString(),\n  });\n}\n\n\u002F\u002F Right to Erasure (GDPR Art. 17)\nexport async function DELETE(\n  request: NextRequest,\n  { params }: { params: { id: string } }\n) {\n  \u002F\u002F Soft delete — anonymize instead of hard delete for audit trail\n  await db.user.update({\n    where: { id: params.id },\n    data: {\n      email: `deleted-${params.id}@redacted.local`,\n      name: '[DELETED]',\n      deletedAt: new Date(),\n    },\n  });\n\n  \u002F\u002F Also delete from log drain provider if applicable\n  console.log(`GDPR deletion completed for user ${params.id}`);\n  return NextResponse.json({ deleted: true });\n}\n```\n\n### Step 4: Secure Cookie Management\n```typescript\n\u002F\u002F lib\u002Fcookies.ts — GDPR-aware cookie handling\nimport { cookies } from 'next\u002Fheaders';\n\nexport function setSessionCookie(token: string): void {\n  cookies().set('session', token, {\n    httpOnly: true,       \u002F\u002F Not accessible via JavaScript\n    secure: true,         \u002F\u002F HTTPS only\n    sameSite: 'lax',      \u002F\u002F CSRF protection\n    maxAge: 60 * 60 * 24, \u002F\u002F 24 hours\n    path: '\u002F',\n  });\n}\n\nexport function setConsentCookie(consent: Record\u003Cstring, boolean>): void {\n  cookies().set('consent', JSON.stringify(consent), {\n    httpOnly: false,  \u002F\u002F Needs client-side access\n    secure: true,\n    sameSite: 'lax',\n    maxAge: 60 * 60 * 24 * 365, \u002F\u002F 1 year\n    path: '\u002F',\n  });\n}\n\n\u002F\u002F Middleware — block analytics if consent not given\nexport function middleware(request: Request) {\n  const consent = request.headers.get('cookie')?.includes('consent');\n  if (!consent) {\n    \u002F\u002F Strip analytics query params, skip tracking middleware\n  }\n}\n```\n\n### Step 5: Data Residency Configuration\nVercel allows configuring where your serverless functions execute:\n\n```json\n\u002F\u002F vercel.json — restrict function execution to EU regions\n{\n  \"regions\": [\"cdg1\", \"lhr1\"],\n  \"functions\": {\n    \"api\u002F**\u002F*.ts\": {\n      \"regions\": [\"cdg1\"]\n    }\n  }\n}\n```\n\nEU regions for GDPR data residency:\n| Region | Location | Code |\n|--------|----------|------|\n| Paris | France | `cdg1` |\n| London | UK | `lhr1` |\n| Frankfurt | Germany | `fra1` |\n\n### Step 6: Audit Logging\n```typescript\n\u002F\u002F lib\u002Faudit-log.ts — track data access for compliance\ninterface AuditEntry {\n  action: 'read' | 'create' | 'update' | 'delete' | 'export';\n  resource: string;\n  resourceId: string;\n  userId: string;\n  ip: string;\n  timestamp: string;\n}\n\nexport async function auditLog(entry: Omit\u003CAuditEntry, 'timestamp'>): Promise\u003Cvoid> {\n  const record: AuditEntry = {\n    ...entry,\n    timestamp: new Date().toISOString(),\n  };\n\n  \u002F\u002F Write to database audit table\n  await db.auditLog.create({ data: record });\n\n  \u002F\u002F Also log for log drain capture (structured JSON)\n  console.log(JSON.stringify({ type: 'audit', ...record }));\n}\n\n\u002F\u002F Usage in API route:\nexport async function GET(request: NextRequest) {\n  await auditLog({\n    action: 'read',\n    resource: 'user',\n    resourceId: params.id,\n    userId: session.userId,\n    ip: request.headers.get('x-forwarded-for') ?? 'unknown',\n  });\n}\n```\n\n## Data Classification Guide\n\n| Category | Examples | Handling on Vercel |\n|----------|----------|-------------------|\n| PII | Email, name, phone, IP | Redact from logs, encrypt at rest |\n| Secrets | API keys, tokens, passwords | Use `type: sensitive` env vars, never log |\n| Financial | Card numbers, bank info | Never process in functions — use Stripe\u002Fpayment provider |\n| Health | Medical records | Requires BAA — contact Vercel Enterprise |\n| Business | Metrics, usage stats | Aggregate before logging |\n\n## Output\n- PII redaction applied to all log output\n- GDPR data subject request endpoints implemented\n- Secure cookie handling with consent management\n- Data residency configured via function regions\n- Audit logging for compliance trail\n\n## Error Handling\n| Error | Cause | Solution |\n|-------|-------|----------|\n| PII in Vercel logs | Not redacting before console.log | Use `redact()` wrapper on all log calls |\n| GDPR data request timeout | Large data export in function | Paginate or use background processing |\n| Cookies not secure | Missing `secure: true` flag | Always set httpOnly and secure flags |\n| Function running in wrong region | Region not set in vercel.json | Specify `regions` per function |\n\n## Resources\n- [Vercel Privacy Policy](https:\u002F\u002Fvercel.com\u002Flegal\u002Fprivacy-policy)\n- [Vercel Data Processing Agreement](https:\u002F\u002Fvercel.com\u002Flegal\u002Fdpa)\n- [GDPR Overview](https:\u002F\u002Fgdpr.eu\u002F)\n- [Vercel Function Regions](https:\u002F\u002Fvercel.com\u002Fdocs\u002Ffunctions\u002Fconfiguring-functions)\n- [Vercel Security](https:\u002F\u002Fvercel.com\u002Fsecurity)\n\n## Next Steps\nFor enterprise RBAC, see `vercel-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","vercel","compliance","privacy","security","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Implement data handling, PII protection, and GDPR\u002FCCPA compliance for Vercel deployments.\nUse when handling sensitive data in serverless functions, implementing data redaction,\nor ensuring privacy compliance on Vercel.\nTrigger with phrases like \"vercel data\", \"vercel PII\",\n\"vercel GDPR\", \"vercel data retention\", \"vercel privacy\", \"vercel compliance\".\n","Read, Write, Edit","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--vercel-pack--vercel-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 vercel-data-handling",{"tool":50,"command":51},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill vercel-data-handling",{"tool":53,"command":54},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill vercel-data-handling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--vercel-pack--vercel-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",[],[]]