[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78Y7P2DDVHV3JQTMFNEF3AM":3,"skill-same:01M78Y7P2DDVHV3JQTMFNEF3AM":57},{"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":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M78Y7P2DDVHV3JQTMFNEF3AM","clay-architecture-variants",null,"Choose and implement Clay integration architecture for different scales and use cases.\nUse when designing new Clay integrations, comparing direct vs queue-based vs event-driven,\nor planning architecture for Clay-powered data operations.\nTrigger with phrases like \"clay architecture\", \"clay blueprint\",\n\"how to structure clay\", \"clay integration design\", \"clay event-driven\".","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--clay-pack--clay-architecture-variants\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: clay-architecture-variants\ndescription: |\n  Choose and implement Clay integration architecture for different scales and use cases.\n  Use when designing new Clay integrations, comparing direct vs queue-based vs event-driven,\n  or planning architecture for Clay-powered data operations.\n  Trigger with phrases like \"clay architecture\", \"clay blueprint\",\n  \"how to structure clay\", \"clay integration design\", \"clay event-driven\".\nallowed-tools: Read, Write, Edit, Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, clay, migration, scaling]\n---\n# Clay Architecture Variants\n\n## Overview\n\nThree proven architecture patterns for Clay data enrichment at different scales. Clay is a hosted SaaS -- your architecture decisions focus on how you send data in (webhooks), how you get enriched data out (HTTP API columns, CRM sync, or CSV export), and how you orchestrate the flow.\n\n## Prerequisites\n\n- Clay account with appropriate plan tier\n- Clear understanding of data volume and latency requirements\n- Infrastructure for chosen architecture tier (if queue-based or event-driven)\n\n## Instructions\n\n### Architecture 1: Direct Integration (Simple)\n\n**Best for:** Small teams, \u003C 1K enrichments\u002Fday, ad-hoc usage.\n\n```\n┌──────────────┐     webhook     ┌───────────┐\n│ Your App     │───────POST─────>│ Clay Table │\n│ (or CSV)     │                 │ (enriches) │\n└──────────────┘                 └─────┬─────┘\n                                       │\n                                  CRM action\n                                  or CSV export\n                                       │\n                                       v\n                                 ┌───────────┐\n                                 │ CRM \u002F DB  │\n                                 └───────────┘\n```\n\n```typescript\n\u002F\u002F Direct: send leads synchronously, export results manually\nasync function directEnrich(leads: Lead[]): Promise\u003Cvoid> {\n  for (const lead of leads) {\n    await fetch(process.env.CLAY_WEBHOOK_URL!, {\n      method: 'POST',\n      headers: { 'Content-Type': 'application\u002Fjson' },\n      body: JSON.stringify(lead),\n    });\n    await new Promise(r => setTimeout(r, 250)); \u002F\u002F Rate limit\n  }\n  console.log(`Sent ${leads.length} leads. Check Clay table for enriched data.`);\n  \u002F\u002F Enriched data reaches CRM via Clay's native CRM action column\n}\n```\n\n**Pros:** Zero infrastructure, 5-minute setup, works on all Clay plans.\n**Cons:** No retry logic, no programmatic access to enriched data, manual export only.\n\n---\n\n### Architecture 2: Webhook-in, HTTP API-out (Standard)\n\n**Best for:** Growing teams, 1K-10K enrichments\u002Fday, CRM integration.\n\n```\n┌──────────────┐     webhook     ┌───────────┐   HTTP API col   ┌──────────────┐\n│ Your App     │───────POST─────>│ Clay Table │──────POST──────>│ Your Webhook │\n│              │                 │ (enriches) │                 │ Handler      │\n└──────────────┘                 └───────────┘                 └──────┬───────┘\n                                                                      │\n                                                                 Process +\n                                                                 Route\n                                                                      │\n                                                          ┌───────────┼───────────┐\n                                                          │           │           │\n                                                          v           v           v\n                                                       ┌─────┐   ┌───────┐   ┌──────┐\n                                                       │ CRM │   │Outreach│  │ DB   │\n                                                       └─────┘   └───────┘   └──────┘\n```\n\n```typescript\n\u002F\u002F Standard: send leads via webhook, receive enriched data via HTTP API column\n\u002F\u002F Inbound: Your app -> Clay\nasync function sendLeads(leads: Lead[]): Promise\u003Cvoid> {\n  const batchResult = await clayClient.sendBatch(leads, 200);\n  console.log(`Sent: ${batchResult.sent}, Failed: ${batchResult.failed}`);\n}\n\n\u002F\u002F Outbound: Clay HTTP API column -> Your webhook handler\napp.post('\u002Fapi\u002Fclay\u002Fenriched', async (req, res) => {\n  res.json({ ok: true }); \u002F\u002F Respond fast\n\n  const lead = req.body;\n  if (lead.icp_score >= 80 && lead.work_email) {\n    await pushToCRM(lead);\n    await addToOutreachSequence(lead);\n  } else if (lead.icp_score >= 50) {\n    await addToNurtureCampaign(lead);\n  }\n});\n```\n\n**Pros:** Full automation, programmatic access to enriched data, flexible routing.\n**Cons:** Requires Growth plan (HTTP API columns), needs public HTTPS endpoint.\n\n---\n\n### Architecture 3: Queue-Based Pipeline (Scale)\n\n**Best for:** Enterprise, 10K+ enrichments\u002Fday, multiple data sources.\n\n```\n┌───────────┐\n│ Web Forms │──┐\n└───────────┘  │     ┌───────────┐     webhook     ┌───────────┐\n               ├────>│ Job Queue │───────POST─────>│ Clay Table │\n┌───────────┐  │     │ (BullMQ)  │                 │ (enriches) │\n│ CRM Events│──┘     └───────────┘                 └─────┬─────┘\n└───────────┘              │                              │\n                      DLQ on fail                   HTTP API col\n┌───────────┐              │                              │\n│ CSV Import│──────────────┘                              v\n└───────────┘                                   ┌──────────────┐\n                                                │ Your Handler │\n                                                │ (w\u002F circuit  │\n                                                │  breaker)    │\n                                                └──────┬───────┘\n                                                       │\n                                            ┌──────────┼──────────┐\n                                            │          │          │\n                                            v          v          v\n                                         ┌─────┐  ┌───────┐  ┌──────┐\n                                         │ CRM │  │Outreach│  │ DWH  │\n                                         └─────┘  └───────┘  └──────┘\n```\n\n```typescript\n\u002F\u002F Scale: queue-based with DLQ, circuit breaker, and multi-source intake\nimport { Queue, Worker } from 'bullmq';\n\nconst enrichQueue = new Queue('clay-enrichment');\n\n\u002F\u002F Multiple sources feed the queue\nasync function onWebFormSubmit(lead: Lead) {\n  await enrichQueue.add('web-form', { ...lead, source: 'web-form' });\n}\n\nasync function onCRMEvent(lead: Lead) {\n  await enrichQueue.add('crm-event', { ...lead, source: 'crm-event' });\n}\n\nasync function onCSVImport(leads: Lead[]) {\n  for (const lead of leads) {\n    await enrichQueue.add('csv-import', { ...lead, source: 'csv-import' });\n  }\n}\n\n\u002F\u002F Worker sends to Clay with rate limiting and circuit breaker\nconst worker = new Worker('clay-enrichment', async (job) => {\n  const { allowed, reason } = circuitBreaker.canProcess(6);\n  if (!allowed) throw new Error(`Circuit open: ${reason}`);\n\n  const res = await fetch(process.env.CLAY_WEBHOOK_URL!, {\n    method: 'POST',\n    headers: { 'Content-Type': 'application\u002Fjson' },\n    body: JSON.stringify(job.data),\n  });\n\n  if (!res.ok) throw new Error(`Clay webhook failed: ${res.status}`);\n  circuitBreaker.recordSuccess(6);\n}, {\n  concurrency: 1,\n  limiter: { max: 5, duration: 1000 }, \u002F\u002F 5 per second max\n});\n```\n\n**Pros:** Handles any volume, automatic retries, DLQ for failures, multi-source.\n**Cons:** Requires queue infrastructure (Redis), more complex to operate.\n\n## Decision Matrix\n\n| Factor | Direct | Webhook + HTTP API | Queue-Based |\n|--------|--------|-------------------|-------------|\n| Volume | \u003C 1K\u002Fday | 1K-10K\u002Fday | 10K+\u002Fday |\n| Plan required | Any | Growth+ | Growth+ |\n| Infrastructure | None | HTTPS endpoint | Redis + HTTPS endpoint |\n| Retry logic | Manual | In-app | Automatic (BullMQ) |\n| Data access | CSV export only | Real-time callback | Real-time callback |\n| CRM sync | Clay native action | HTTP API column | HTTP API column |\n| Complexity | Low | Medium | High |\n| Time to implement | Hours | Days | 1-2 weeks |\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Need real-time enriched data | Using Direct (CSV only) | Upgrade to Webhook + HTTP API |\n| Queue backing up | Webhook rate limiting | Reduce concurrency, add delay |\n| HTTP API column timeout | Callback endpoint slow | Respond 200 immediately, process async |\n| Credits exhausted mid-pipeline | No budget control | Add circuit breaker with credit limit |\n\n## Resources\n\n- [Clay University -- HTTP API Integration](https:\u002F\u002Funiversity.clay.com\u002Fdocs\u002Fhttp-api-integration-overview)\n- [Clay University -- Using Clay as an API](https:\u002F\u002Fwww.clay.com\u002Funiversity\u002Fguide\u002Fusing-clay-as-an-api)\n- [BullMQ Documentation](https:\u002F\u002Fdocs.bullmq.io\u002F)\n\n## Next Steps\n\nFor common pitfalls to avoid, see `clay-known-pitfalls`.\n","# Clay Architecture Variants\n\n## Overview\n\nThree proven architecture patterns for Clay data enrichment at different scales. Clay is a hosted SaaS -- your architecture decisions focus on how you send data in (webhooks), how you get enriched data out (HTTP API columns, CRM sync, or CSV export), and how you orchestrate the flow.\n\n## Prerequisites\n\n- Clay account with appropriate plan tier\n- Clear understanding of data volume and latency requirements\n- Infrastructure for chosen architecture tier (if queue-based or event-driven)\n\n## Instructions\n\n### Architecture 1: Direct Integration (Simple)\n\n**Best for:** Small teams, \u003C 1K enrichments\u002Fday, ad-hoc usage.\n\n```\n┌──────────────┐     webhook     ┌───────────┐\n│ Your App     │───────POST─────>│ Clay Table │\n│ (or CSV)     │                 │ (enriches) │\n└──────────────┘                 └─────┬─────┘\n                                       │\n                                  CRM action\n                                  or CSV export\n                                       │\n                                       v\n                                 ┌───────────┐\n                                 │ CRM \u002F DB  │\n                                 └───────────┘\n```\n\n```typescript\n\u002F\u002F Direct: send leads synchronously, export results manually\nasync function directEnrich(leads: Lead[]): Promise\u003Cvoid> {\n  for (const lead of leads) {\n    await fetch(process.env.CLAY_WEBHOOK_URL!, {\n      method: 'POST',\n      headers: { 'Content-Type': 'application\u002Fjson' },\n      body: JSON.stringify(lead),\n    });\n    await new Promise(r => setTimeout(r, 250)); \u002F\u002F Rate limit\n  }\n  console.log(`Sent ${leads.length} leads. Check Clay table for enriched data.`);\n  \u002F\u002F Enriched data reaches CRM via Clay's native CRM action column\n}\n```\n\n**Pros:** Zero infrastructure, 5-minute setup, works on all Clay plans.\n**Cons:** No retry logic, no programmatic access to enriched data, manual export only.\n\n---\n\n### Architecture 2: Webhook-in, HTTP API-out (Standard)\n\n**Best for:** Growing teams, 1K-10K enrichments\u002Fday, CRM integration.\n\n```\n┌──────────────┐     webhook     ┌───────────┐   HTTP API col   ┌──────────────┐\n│ Your App     │───────POST─────>│ Clay Table │──────POST──────>│ Your Webhook │\n│              │                 │ (enriches) │                 │ Handler      │\n└──────────────┘                 └───────────┘                 └──────┬───────┘\n                                                                      │\n                                                                 Process +\n                                                                 Route\n                                                                      │\n                                                          ┌───────────┼───────────┐\n                                                          │           │           │\n                                                          v           v           v\n                                                       ┌─────┐   ┌───────┐   ┌──────┐\n                                                       │ CRM │   │Outreach│  │ DB   │\n                                                       └─────┘   └───────┘   └──────┘\n```\n\n```typescript\n\u002F\u002F Standard: send leads via webhook, receive enriched data via HTTP API column\n\u002F\u002F Inbound: Your app -> Clay\nasync function sendLeads(leads: Lead[]): Promise\u003Cvoid> {\n  const batchResult = await clayClient.sendBatch(leads, 200);\n  console.log(`Sent: ${batchResult.sent}, Failed: ${batchResult.failed}`);\n}\n\n\u002F\u002F Outbound: Clay HTTP API column -> Your webhook handler\napp.post('\u002Fapi\u002Fclay\u002Fenriched', async (req, res) => {\n  res.json({ ok: true }); \u002F\u002F Respond fast\n\n  const lead = req.body;\n  if (lead.icp_score >= 80 && lead.work_email) {\n    await pushToCRM(lead);\n    await addToOutreachSequence(lead);\n  } else if (lead.icp_score >= 50) {\n    await addToNurtureCampaign(lead);\n  }\n});\n```\n\n**Pros:** Full automation, programmatic access to enriched data, flexible routing.\n**Cons:** Requires Growth plan (HTTP API columns), needs public HTTPS endpoint.\n\n---\n\n### Architecture 3: Queue-Based Pipeline (Scale)\n\n**Best for:** Enterprise, 10K+ enrichments\u002Fday, multiple data sources.\n\n```\n┌───────────┐\n│ Web Forms │──┐\n└───────────┘  │     ┌───────────┐     webhook     ┌───────────┐\n               ├────>│ Job Queue │───────POST─────>│ Clay Table │\n┌───────────┐  │     │ (BullMQ)  │                 │ (enriches) │\n│ CRM Events│──┘     └───────────┘                 └─────┬─────┘\n└───────────┘              │                              │\n                      DLQ on fail                   HTTP API col\n┌───────────┐              │                              │\n│ CSV Import│──────────────┘                              v\n└───────────┘                                   ┌──────────────┐\n                                                │ Your Handler │\n                                                │ (w\u002F circuit  │\n                                                │  breaker)    │\n                                                └──────┬───────┘\n                                                       │\n                                            ┌──────────┼──────────┐\n                                            │          │          │\n                                            v          v          v\n                                         ┌─────┐  ┌───────┐  ┌──────┐\n                                         │ CRM │  │Outreach│  │ DWH  │\n                                         └─────┘  └───────┘  └──────┘\n```\n\n```typescript\n\u002F\u002F Scale: queue-based with DLQ, circuit breaker, and multi-source intake\nimport { Queue, Worker } from 'bullmq';\n\nconst enrichQueue = new Queue('clay-enrichment');\n\n\u002F\u002F Multiple sources feed the queue\nasync function onWebFormSubmit(lead: Lead) {\n  await enrichQueue.add('web-form', { ...lead, source: 'web-form' });\n}\n\nasync function onCRMEvent(lead: Lead) {\n  await enrichQueue.add('crm-event', { ...lead, source: 'crm-event' });\n}\n\nasync function onCSVImport(leads: Lead[]) {\n  for (const lead of leads) {\n    await enrichQueue.add('csv-import', { ...lead, source: 'csv-import' });\n  }\n}\n\n\u002F\u002F Worker sends to Clay with rate limiting and circuit breaker\nconst worker = new Worker('clay-enrichment', async (job) => {\n  const { allowed, reason } = circuitBreaker.canProcess(6);\n  if (!allowed) throw new Error(`Circuit open: ${reason}`);\n\n  const res = await fetch(process.env.CLAY_WEBHOOK_URL!, {\n    method: 'POST',\n    headers: { 'Content-Type': 'application\u002Fjson' },\n    body: JSON.stringify(job.data),\n  });\n\n  if (!res.ok) throw new Error(`Clay webhook failed: ${res.status}`);\n  circuitBreaker.recordSuccess(6);\n}, {\n  concurrency: 1,\n  limiter: { max: 5, duration: 1000 }, \u002F\u002F 5 per second max\n});\n```\n\n**Pros:** Handles any volume, automatic retries, DLQ for failures, multi-source.\n**Cons:** Requires queue infrastructure (Redis), more complex to operate.\n\n## Decision Matrix\n\n| Factor | Direct | Webhook + HTTP API | Queue-Based |\n|--------|--------|-------------------|-------------|\n| Volume | \u003C 1K\u002Fday | 1K-10K\u002Fday | 10K+\u002Fday |\n| Plan required | Any | Growth+ | Growth+ |\n| Infrastructure | None | HTTPS endpoint | Redis + HTTPS endpoint |\n| Retry logic | Manual | In-app | Automatic (BullMQ) |\n| Data access | CSV export only | Real-time callback | Real-time callback |\n| CRM sync | Clay native action | HTTP API column | HTTP API column |\n| Complexity | Low | Medium | High |\n| Time to implement | Hours | Days | 1-2 weeks |\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Need real-time enriched data | Using Direct (CSV only) | Upgrade to Webhook + HTTP API |\n| Queue backing up | Webhook rate limiting | Reduce concurrency, add delay |\n| HTTP API column timeout | Callback endpoint slow | Respond 200 immediately, process async |\n| Credits exhausted mid-pipeline | No budget control | Add circuit breaker with credit limit |\n\n## Resources\n\n- [Clay University -- HTTP API Integration](https:\u002F\u002Funiversity.clay.com\u002Fdocs\u002Fhttp-api-integration-overview)\n- [Clay University -- Using Clay as an API](https:\u002F\u002Fwww.clay.com\u002Funiversity\u002Fguide\u002Fusing-clay-as-an-api)\n- [BullMQ Documentation](https:\u002F\u002Fdocs.bullmq.io\u002F)\n\n## Next Steps\n\nFor common pitfalls to avoid, see `clay-known-pitfalls`.\n",{"name":5,"tags":24,"author":29,"license":15,"version":30,"description":31,"allowed-tools":32,"compatible-with":33},[25,26,27,28],"saas","clay","migration","scaling","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Choose and implement Clay integration architecture for different scales and use cases.\nUse when designing new Clay integrations, comparing direct vs queue-based vs event-driven,\nor planning architecture for Clay-powered data operations.\nTrigger with phrases like \"clay architecture\", \"clay blueprint\",\n\"how to structure clay\", \"clay integration design\", \"clay event-driven\".\n","Read, Write, Edit, Grep","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--clay-pack--clay-architecture-variants",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":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill clay-architecture-variants",{"tool":49,"command":50},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill clay-architecture-variants",{"tool":52,"command":53},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill clay-architecture-variants","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--clay-pack--clay-architecture-variants\u002FSKILL.md",true,[],[58,65,72,79,86,94],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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",[],[]]