[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H5JPJ0FF11CPPRD5RWT38F":3,"skill-same:01M6H5JPJ0FF11CPPRD5RWT38F":79},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6H5JPJ0FF11CPPRD5RWT38F","clay-reference-architecture",null,"Implement Clay reference architecture with best-practice project layout.\nUse when designing new Clay integrations, reviewing project structure,\nor establishing architecture standards for Clay applications.\nTrigger with phrases like \"clay architecture\", \"clay best practices\",\n\"clay project structure\", \"how to organize clay\", \"clay layout\".","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fclay-pack\u002Fskills\u002Fclay-reference-architecture\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"architecture","reference","clay reference architecture","clay","for","openclaw","how to","trigger","io","layout","project","structure","organize","standards","read","integrations","how","applications","code","project structure","2026-11-10 10:12:30",false,"---\nname: clay-reference-architecture\ndescription: |\n  Implement Clay reference architecture with best-practice project layout.\n  Use when designing new Clay integrations, reviewing project structure,\n  or establishing architecture standards for Clay applications.\n  Trigger with phrases like \"clay architecture\", \"clay best practices\",\n  \"clay project structure\", \"how to organize clay\", \"clay layout\".\nallowed-tools: Read, Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# Clay Reference Architecture\n\n## Overview\n\nProduction architecture for Clay-based lead enrichment and data operations. Covers table design, enrichment pipeline patterns, webhook integration, and CRM synchronization flows.\n\n## Prerequisites\n\n- Clay account with API access\n- Understanding of Clay tables and enrichment columns\n- CRM integration configured (HubSpot, Salesforce)\n- Webhook endpoint for automation triggers\n\n## Instructions\n\n### Step 1: Design Table Schema\n\nDefine input columns (company name, domain, contact, LinkedIn URL), enrichment columns (company size, industry, email, phone, technologies), formula columns (ICP score, lead tier), and AI columns (personalized intro, pain points).\n\n### Step 2: Configure Enrichment Waterfall\n\nOrder providers by cost: Apollo (1 credit) -> Hunter (1) -> Dropcontact (2) -> Findymail (3). Enable \"stop on first result\" to minimize credit usage.\n\n### Step 3: Set Up Webhook Integration\n\nOn enrichment completion, check ICP score. Push high-value leads (score >= 80 with valid email) to CRM immediately. Add tier-A leads to outreach sequences.\n\n### Step 4: Implement ICP Scoring Formula\n\nWeight company size (up to 50 pts), target industry match (30 pts), and technology stack matches (10 pts each, max 100 total).\n\nFor architecture diagrams, TypeScript implementations, and ICP scoring code, load the reference guide:\n`Read(${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation-guide.md)`\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Enrichment credits exhausted | Too many lookups | Use waterfall pattern, set daily limits |\n| Duplicate records | Re-importing same list | Deduplicate on domain + contact name |\n| Webhook timeout | Processing too slow | Acknowledge immediately, process async |\n| Low email find rate | Bad input data | Validate domains before enrichment |\n\n## Resources\n\n- [Clay API Documentation](https:\u002F\u002Fdocs.clay.com\u002Fapi)\n- [Clay Enrichment Providers](https:\u002F\u002Fdocs.clay.com\u002Fenrichments)\n- [Clay Formulas Guide](https:\u002F\u002Fdocs.clay.com\u002Fformulas)\n\n## Output\n\n- Configuration files or code changes applied to the project\n- Validation report confirming correct implementation\n- Summary of changes made and their rationale\n\nSee [design implementation details](${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md) for output format specifications.\n\n## Examples\n\n**Basic usage**: Apply clay reference architecture to a standard project setup with default configuration options.\n\n**Advanced scenario**: Customize clay reference architecture for production environments with multiple constraints and team-specific requirements.","# Clay Reference Architecture\n\n## Overview\n\nProduction architecture for Clay-based lead enrichment and data operations. Covers table design, enrichment pipeline patterns, webhook integration, and CRM synchronization flows.\n\n## Prerequisites\n\n- Clay account with API access\n- Understanding of Clay tables and enrichment columns\n- CRM integration configured (HubSpot, Salesforce)\n- Webhook endpoint for automation triggers\n\n## Instructions\n\n### Step 1: Design Table Schema\n\nDefine input columns (company name, domain, contact, LinkedIn URL), enrichment columns (company size, industry, email, phone, technologies), formula columns (ICP score, lead tier), and AI columns (personalized intro, pain points).\n\n### Step 2: Configure Enrichment Waterfall\n\nOrder providers by cost: Apollo (1 credit) -> Hunter (1) -> Dropcontact (2) -> Findymail (3). Enable \"stop on first result\" to minimize credit usage.\n\n### Step 3: Set Up Webhook Integration\n\nOn enrichment completion, check ICP score. Push high-value leads (score >= 80 with valid email) to CRM immediately. Add tier-A leads to outreach sequences.\n\n### Step 4: Implement ICP Scoring Formula\n\nWeight company size (up to 50 pts), target industry match (30 pts), and technology stack matches (10 pts each, max 100 total).\n\nFor architecture diagrams, TypeScript implementations, and ICP scoring code, load the reference guide:\n`Read(${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation-guide.md)`\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Enrichment credits exhausted | Too many lookups | Use waterfall pattern, set daily limits |\n| Duplicate records | Re-importing same list | Deduplicate on domain + contact name |\n| Webhook timeout | Processing too slow | Acknowledge immediately, process async |\n| Low email find rate | Bad input data | Validate domains before enrichment |\n\n## Resources\n\n- [Clay API Documentation](https:\u002F\u002Fdocs.clay.com\u002Fapi)\n- [Clay Enrichment Providers](https:\u002F\u002Fdocs.clay.com\u002Fenrichments)\n- [Clay Formulas Guide](https:\u002F\u002Fdocs.clay.com\u002Fformulas)\n\n## Output\n\n- Configuration files or code changes applied to the project\n- Validation report confirming correct implementation\n- Summary of changes made and their rationale\n\nSee [design implementation details](${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md) for output format specifications.\n\n## Examples\n\n**Basic usage**: Apply clay reference architecture to a standard project setup with default configuration options.\n\n**Advanced scenario**: Customize clay reference architecture for production environments with multiple constraints and team-specific requirements.",{"name":5,"author":43,"license":14,"version":44,"description":45,"allowed-tools":46,"compatible-with":47},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Implement Clay reference architecture with best-practice project layout.\nUse when designing new Clay integrations, reviewing project structure,\nor establishing architecture standards for Clay applications.\nTrigger with phrases like \"clay architecture\", \"clay best practices\",\n\"clay project structure\", \"how to organize clay\", \"clay layout\".\n","Read, Grep","claude-code, codex, openclaw","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fclay-pack\u002Fskills\u002Fclay-reference-architecture",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add micsapp\u002Fmicstec-skills --skill clay-reference-architecture",{"tool":61,"command":62},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill clay-reference-architecture",{"tool":64,"command":65},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill clay-reference-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fclay-pack\u002Fskills\u002Fclay-reference-architecture\u002FSKILL.md",true,[69,75],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Fimplementation-guide.md","REFERENCE","参考文档",5989,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fclay-pack\u002Fskills\u002Fclay-reference-architecture\u002Freferences\u002Fimplementation-guide.md",{"path":76,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fimplementation.md",4783,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fclay-pack\u002Fskills\u002Fclay-reference-architecture\u002Freferences\u002Fimplementation.md",[80,115,144,165,185,209],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":96,"publishedAt":38},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[86,91],{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[18,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,22],"azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":129,"publishedAt":38},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[121,122,125,128],{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},{"categoryNo":123,"categoryName":124,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":126,"categoryName":127,"taxonomyType":89,"taxonomyTypeDesc":90},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},[130,131,132,133,97,134,36,135,136,137,138,139,105,106,112,140,141,113,142,143],"deployment","apiops deployment","workflows","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD","implementing",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":151,"publishedAt":38},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[150],{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},[152,153,154,155,97,100,105,106,156,157,158,159,160,161,162,113,163,164,143,22],"policy","authoring","apim policy authoring","security","access","use","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":173,"publishedAt":38},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[171,172],{"categoryNo":87,"categoryName":88,"taxonomyType":89,"taxonomyTypeDesc":90},{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},[174,155,175,105,159,176,97,130,177,178,179,180,106,181,113,182,183,184,114,22],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":186,"name":187,"nameZh":6,"description":188,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":189,"categories":190,"keywords":191,"publishedAt":38},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[192,193,194,132,195,196,197,198,105,199,200,201,202,203,204,28,205,206,207,208],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project work","token","line","sprints",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":215,"publishedAt":38},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[211,216,217,218,219,220,221,157,222,223],"npm","js","calculate","node","math","user","compute","errors"]