[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H5J3VGCTNQSSRNEPPFQN95":3,"skill-same:01M6H5J3VGCTNQSSRNEPPFQN95":69},{"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},"01M6H5J3VGCTNQSSRNEPPFQN95","clay-observability",null,"Set up comprehensive observability for Clay integrations with metrics, traces, and alerts.\nUse when implementing monitoring for Clay operations, setting up dashboards,\nor configuring alerting for Clay integration health.\nTrigger with phrases like \"clay monitoring\", \"clay metrics\",\n\"clay observability\", \"monitor clay\", \"clay alerts\", \"clay tracing\".","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-observability\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"observability","clay","clay observability","use","for","implementing","with","trigger","io","alerts","up","codex","operations","integrations","health","SET","monitoring","alerting","code","monitor","2026-11-10 10:12:30",false,"---\nname: clay-observability\ndescription: |\n  Set up comprehensive observability for Clay integrations with metrics, traces, and alerts.\n  Use when implementing monitoring for Clay operations, setting up dashboards,\n  or configuring alerting for Clay integration health.\n  Trigger with phrases like \"clay monitoring\", \"clay metrics\",\n  \"clay observability\", \"monitor clay\", \"clay alerts\", \"clay tracing\".\nallowed-tools: Read, Write, Edit\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# Clay Observability\n\n## Overview\nMonitor Clay data enrichment pipeline health, credit consumption velocity, and enrichment success rates. Clay's credit-based pricing model means observability must track per-enrichment costs (email lookup: ~1 credit, company enrichment: ~5 credits, waterfall enrichment: variable).\n\n## Prerequisites\n- Clay Team or Enterprise plan\n- API access for usage queries\n- External metrics\u002Falerting system\n\n## Instructions\n\n### Step 1: Track Credit Consumption in Real Time\n```bash\nset -euo pipefail\n# Query current credit usage by table\ncurl \"https:\u002F\u002Fapi.clay.com\u002Fv1\u002Fworkspace\u002Fusage?group_by=table&period=today\" \\\n  -H \"Authorization: Bearer $CLAY_API_KEY\" | \\\n  jq '.usage[] | {table_name, credits_used, rows_enriched, avg_credits_per_row: (.credits_used \u002F (.rows_enriched + 0.01))}'\n```\n\n### Step 2: Monitor Enrichment Hit Rates\n```typescript\n\u002F\u002F clay-enrichment-monitor.ts\nasync function monitorEnrichments() {\n  const tables = await clayApi.listTables();\n  for (const table of tables) {\n    const stats = await clayApi.getTableStats(table.id);\n    const hitRate = stats.rows_with_data \u002F Math.max(stats.total_rows, 1) * 100;\n    emitGauge('clay_enrichment_hit_rate_pct', hitRate, { table: table.name, enrichment: stats.enrichment_type });\n    emitCounter('clay_credits_consumed', stats.credits_used, { table: table.name });\n\n    if (hitRate \u003C 30) {\n      console.warn(`Low hit rate on ${table.name}: ${hitRate.toFixed(1)}% (check enrichment config)`);\n    }\n  }\n}\n```\n\n### Step 3: Set Up Credit Burn Alerts\n```yaml\ngroups:\n  - name: clay\n    rules:\n      - alert: ClayCreditBurnHigh\n        expr: rate(clay_credits_consumed[1h]) > 500  # HTTP 500 Internal Server Error\n        annotations: { summary: \"Clay burning >500 credits\u002Fhour (projected monthly: {{ $value * 720 }})\" }  # 720: HTTP 500 Internal Server Error\n      - alert: ClayLowHitRate\n        expr: clay_enrichment_hit_rate_pct \u003C 20\n        for: 30m\n        annotations: { summary: \"Clay enrichment hit rate below 20% on {{ $labels.table }}\" }\n      - alert: ClayCreditBalance\n        expr: clay_credits_remaining \u003C 1000  # 1000: 1 second in ms\n        annotations: { summary: \"Clay credit balance below 1,000 -- refill needed\" }\n```\n\n### Step 4: Log Enrichment Results for Audit\n```json\n{\"ts\":\"2026-03-10T14:30:00Z\",\"table\":\"outbound-leads\",\"enrichment\":\"email_finder\",\"rows_attempted\":100,\"rows_enriched\":72,\"credits_used\":100,\"hit_rate\":72.0,\"duration_ms\":4500}  # 2026: 4500 = configured value\n```\n\n### Step 5: Build a Credit Efficiency Dashboard\nKey panels: credit consumption by table (bar chart), enrichment hit rate by provider, daily\u002Fweekly credit burn trend, credits remaining gauge, and cost-per-enriched-row (credits used \u002F rows with actual data returned). Tables with low hit rates and high credit burn are optimization targets.\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Credits depleting fast | Waterfall enrichment trying all providers | Limit waterfall steps or set credit cap per row |\n| Hit rate near 0% | Bad input data (invalid emails\u002Fdomains) | Clean input data before enrichment |\n| API timeout on enrichment | Provider rate limit | Reduce table auto-enrich concurrency |\n| Usage API returning stale data | Caching lag | Wait 5 minutes for usage data to update |\n\n## Examples\n\n**Basic usage**: Apply clay observability to a standard project setup with default configuration options.\n\n**Advanced scenario**: Customize clay observability for production environments with multiple constraints and team-specific requirements.\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\n## Resources\n\n- Official monitoring documentation\n- Community best practices and patterns\n- Related skills in this plugin pack","# Clay Observability\n\n## Overview\nMonitor Clay data enrichment pipeline health, credit consumption velocity, and enrichment success rates. Clay's credit-based pricing model means observability must track per-enrichment costs (email lookup: ~1 credit, company enrichment: ~5 credits, waterfall enrichment: variable).\n\n## Prerequisites\n- Clay Team or Enterprise plan\n- API access for usage queries\n- External metrics\u002Falerting system\n\n## Instructions\n\n### Step 1: Track Credit Consumption in Real Time\n```bash\nset -euo pipefail\n# Query current credit usage by table\ncurl \"https:\u002F\u002Fapi.clay.com\u002Fv1\u002Fworkspace\u002Fusage?group_by=table&period=today\" \\\n  -H \"Authorization: Bearer $CLAY_API_KEY\" | \\\n  jq '.usage[] | {table_name, credits_used, rows_enriched, avg_credits_per_row: (.credits_used \u002F (.rows_enriched + 0.01))}'\n```\n\n### Step 2: Monitor Enrichment Hit Rates\n```typescript\n\u002F\u002F clay-enrichment-monitor.ts\nasync function monitorEnrichments() {\n  const tables = await clayApi.listTables();\n  for (const table of tables) {\n    const stats = await clayApi.getTableStats(table.id);\n    const hitRate = stats.rows_with_data \u002F Math.max(stats.total_rows, 1) * 100;\n    emitGauge('clay_enrichment_hit_rate_pct', hitRate, { table: table.name, enrichment: stats.enrichment_type });\n    emitCounter('clay_credits_consumed', stats.credits_used, { table: table.name });\n\n    if (hitRate \u003C 30) {\n      console.warn(`Low hit rate on ${table.name}: ${hitRate.toFixed(1)}% (check enrichment config)`);\n    }\n  }\n}\n```\n\n### Step 3: Set Up Credit Burn Alerts\n```yaml\ngroups:\n  - name: clay\n    rules:\n      - alert: ClayCreditBurnHigh\n        expr: rate(clay_credits_consumed[1h]) > 500  # HTTP 500 Internal Server Error\n        annotations: { summary: \"Clay burning >500 credits\u002Fhour (projected monthly: {{ $value * 720 }})\" }  # 720: HTTP 500 Internal Server Error\n      - alert: ClayLowHitRate\n        expr: clay_enrichment_hit_rate_pct \u003C 20\n        for: 30m\n        annotations: { summary: \"Clay enrichment hit rate below 20% on {{ $labels.table }}\" }\n      - alert: ClayCreditBalance\n        expr: clay_credits_remaining \u003C 1000  # 1000: 1 second in ms\n        annotations: { summary: \"Clay credit balance below 1,000 -- refill needed\" }\n```\n\n### Step 4: Log Enrichment Results for Audit\n```json\n{\"ts\":\"2026-03-10T14:30:00Z\",\"table\":\"outbound-leads\",\"enrichment\":\"email_finder\",\"rows_attempted\":100,\"rows_enriched\":72,\"credits_used\":100,\"hit_rate\":72.0,\"duration_ms\":4500}  # 2026: 4500 = configured value\n```\n\n### Step 5: Build a Credit Efficiency Dashboard\nKey panels: credit consumption by table (bar chart), enrichment hit rate by provider, daily\u002Fweekly credit burn trend, credits remaining gauge, and cost-per-enriched-row (credits used \u002F rows with actual data returned). Tables with low hit rates and high credit burn are optimization targets.\n\n## Error Handling\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Credits depleting fast | Waterfall enrichment trying all providers | Limit waterfall steps or set credit cap per row |\n| Hit rate near 0% | Bad input data (invalid emails\u002Fdomains) | Clean input data before enrichment |\n| API timeout on enrichment | Provider rate limit | Reduce table auto-enrich concurrency |\n| Usage API returning stale data | Caching lag | Wait 5 minutes for usage data to update |\n\n## Examples\n\n**Basic usage**: Apply clay observability to a standard project setup with default configuration options.\n\n**Advanced scenario**: Customize clay observability for production environments with multiple constraints and team-specific requirements.\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\n## Resources\n\n- Official monitoring documentation\n- Community best practices and patterns\n- Related skills in this plugin pack",{"name":5,"author":43,"license":14,"version":44,"description":45,"allowed-tools":46,"compatible-with":47},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Set up comprehensive observability for Clay integrations with metrics, traces, and alerts.\nUse when implementing monitoring for Clay operations, setting up dashboards,\nor configuring alerting for Clay integration health.\nTrigger with phrases like \"clay monitoring\", \"clay metrics\",\n\"clay observability\", \"monitor clay\", \"clay alerts\", \"clay tracing\".\n","Read, Write, Edit","claude-code, codex, openclaw","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fclay-pack\u002Fskills\u002Fclay-observability",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-observability",{"tool":61,"command":62},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill clay-observability",{"tool":64,"command":65},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill clay-observability","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Fclay-pack\u002Fskills\u002Fclay-observability\u002FSKILL.md",true,[],[70,106,134,154,174,199],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":86,"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",[76,81],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,22],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":120,"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",[112,113,116,119],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},{"categoryNo":114,"categoryName":115,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":117,"categoryName":118,"taxonomyType":79,"taxonomyTypeDesc":80},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[121,122,123,124,88,125,36,126,127,128,129,130,96,97,103,131,132,104,133,23],"deployment","apiops deployment","workflows","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD",{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":141,"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",[140],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},[142,143,144,145,88,91,96,97,146,21,147,148,149,150,151,104,152,153,23,22],"policy","authoring","apim policy authoring","security","access","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":162,"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",[160,161],{"categoryNo":77,"categoryName":78,"taxonomyType":79,"taxonomyTypeDesc":80},{"categoryNo":82,"categoryName":83,"taxonomyType":84,"taxonomyTypeDesc":85},[163,145,164,96,148,165,88,121,166,167,168,169,97,170,104,171,172,173,105,22],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":175,"name":176,"nameZh":6,"description":177,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":178,"categories":179,"keywords":180,"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",[],[181,182,183,123,184,185,186,187,96,188,189,190,191,192,193,194,195,196,197,198],"cli","jira","jira cli","init","tasks","create","issues","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":200,"name":201,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":205,"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",[],[201,206,207,208,209,210,211,21,212,213],"npm","js","calculate","node","math","user","compute","errors"]