[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M792P5M37VNCPRKFS5B0Q6MD":3,"skill-same:01M792P5M37VNCPRKFS5B0Q6MD":56},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M792P5M37VNCPRKFS5B0Q6MD","lindy-reference-architecture",null,"Reference architectures for Lindy AI agent integrations.\nUse when designing systems, planning multi-agent architectures,\nor implementing production integration patterns.\nTrigger with phrases like \"lindy architecture\", \"lindy design\",\n\"lindy system design\", \"lindy patterns\", \"lindy multi-agent\".","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--lindy-pack--lindy-reference-architecture\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: lindy-reference-architecture\ndescription: |\n  Reference architectures for Lindy AI agent integrations.\n  Use when designing systems, planning multi-agent architectures,\n  or implementing production integration patterns.\n  Trigger with phrases like \"lindy architecture\", \"lindy design\",\n  \"lindy system design\", \"lindy patterns\", \"lindy multi-agent\".\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, lindy, lindy-reference]\n---\n# Lindy Reference Architecture\n\n## Overview\nProduction-ready architecture patterns for integrating Lindy AI agents into\napplications. Covers webhook integration, multi-agent societies, event-driven\npipelines, and high-availability patterns.\n\n## Prerequisites\n- Understanding of Lindy agent model (triggers, actions, skills)\n- Familiarity with webhook-based architectures\n- Production requirements defined (throughput, latency, reliability)\n\n## Architecture 1: Simple Webhook Integration\nSingle agent triggered by your application, results sent via callback.\n\n```\n┌─────────────┐       POST (webhook)       ┌──────────────┐\n│  Your App   │ ─────────────────────────→  │ Lindy Agent  │\n│             │                             │              │\n│  \u002Fcallback  │ ←─────────────────────────  │ HTTP Request │\n│             │       POST (callback)       │   Action     │\n└─────────────┘                             └──────────────┘\n```\n\n**Implementation**:\n- Your app sends webhook with `callbackUrl` field\n- Lindy agent processes and responds via Send POST Request to Callback\n- Your app receives results asynchronously\n\n**Best for**: Simple automations (email triage, lead scoring, content generation)\n\n## Architecture 2: Event-Driven Pipeline\nMultiple event sources feed agents through a central webhook router.\n\n```\n┌──────────┐\n│ Stripe   │──webhook──┐\n└──────────┘           │\n                       ▼\n┌──────────┐     ┌───────────┐     ┌──────────────┐\n│ Shopify  │──→  │  Router   │──→  │ Lindy Agents │\n└──────────┘     │  Service  │     │              │\n                 └───────────┘     │ • Order Bot  │\n┌──────────┐           ▲          │ • Support Bot│\n│ Your App │──webhook──┘          │ • Analytics  │\n└──────────┘                      └──────────────┘\n```\n\n**Implementation**:\n```typescript\n\u002F\u002F Event router — maps events to specific Lindy agents\nconst agentWebhooks: Record\u003Cstring, string> = {\n  'order.created': process.env.LINDY_ORDER_AGENT_WEBHOOK!,\n  'customer.support_request': process.env.LINDY_SUPPORT_AGENT_WEBHOOK!,\n  'analytics.daily_report': process.env.LINDY_ANALYTICS_AGENT_WEBHOOK!,\n};\n\napp.post('\u002Fevents', async (req, res) => {\n  const { event, data } = req.body;\n  const webhookUrl = agentWebhooks[event];\n\n  if (!webhookUrl) {\n    return res.status(400).json({ error: `Unknown event: ${event}` });\n  }\n\n  await fetch(webhookUrl, {\n    method: 'POST',\n    headers: {\n      'Authorization': `Bearer ${process.env.LINDY_WEBHOOK_SECRET}`,\n      'Content-Type': 'application\u002Fjson',\n    },\n    body: JSON.stringify({ event, data, callbackUrl: `${BASE_URL}\u002Fcallback` }),\n  });\n\n  res.json({ routed: true, agent: event });\n});\n```\n\n**Best for**: Multiple event sources, different agents per event type\n\n## Architecture 3: Multi-Agent Society (Delegation)\nSpecialized agents collaborate through Lindy's built-in delegation system.\n\n```\n┌─────────────────┐\n│ Orchestrator    │\n│ Lindy           │\n│ (receives       │\n│  initial task)  │\n└───┬────────┬────┘\n    │        │\n    ▼        ▼\n┌────────┐ ┌────────┐\n│Research│ │Analysis│\n│ Lindy  │ │ Lindy  │\n└───┬────┘ └───┬────┘\n    │          │\n    ▼          ▼\n┌─────────────────┐\n│ Writer Lindy    │\n│ (synthesizes    │\n│  final output)  │\n└─────────────────┘\n```\n\n**Setup in Lindy**:\n1. Create specialized agents with **Agent Message Received** triggers\n2. Orchestrator uses **Agent Send Message** action to delegate\n3. Each agent completes its specialty and sends results forward\n4. Writer agent synthesizes and delivers final output\n\n**Key decisions**:\n| Decision | Option A | Option B |\n|----------|---------|---------|\n| Context passing | Full context (accurate, expensive) | Selective context (cheap, focused) |\n| Error handling | Agent retries | Orchestrator retry logic |\n| Parallelism | Sequential delegation | Parallel delegation with merge |\n\n**Best for**: Complex tasks requiring multiple specialties (research + analysis + writing)\n\n## Architecture 4: Scheduled Pipeline\nAgents run on schedules, each feeding data to the next.\n\n```\n                    Schedule: Daily 6 AM\n                         │\n                         ▼\n                  ┌──────────────┐\n                  │ Data Fetch   │ Pulls from APIs\u002Fdatabases\n                  │ Lindy        │\n                  └──────┬───────┘\n                         │ Agent Send Message\n                         ▼\n                  ┌──────────────┐\n                  │ Analysis     │ Processes & summarizes\n                  │ Lindy        │\n                  └──────┬───────┘\n                         │ Agent Send Message\n                         ▼\n                  ┌──────────────┐\n                  │ Report       │ Formats & delivers\n                  │ Lindy        │\n                  │  → Slack     │\n                  │  → Email     │\n                  └──────────────┘\n```\n\n**Best for**: Daily reports, weekly digests, scheduled data processing\n\n## Architecture 5: Chat + Knowledge Base\nAgent deployed as customer-facing chatbot with RAG-powered responses.\n\n```\n┌──────────────┐     ┌──────────────┐     ┌──────────────┐\n│  Website     │     │ Lindy Agent  │     │ Knowledge    │\n│  (Embed      │◀──▶ │              │◀──▶ │ Base         │\n│   Widget)    │     │ Chat Trigger │     │ PDFs, Docs,  │\n└──────────────┘     │ + KB Search  │     │ Websites     │\n                     │ + Condition  │     └──────────────┘\n                     │ + Escalate   │\n                     └──────────────┘\n                            │\n                            ▼ (if escalation needed)\n                     ┌──────────────┐\n                     │ Slack DM to  │\n                     │ human agent  │\n                     └──────────────┘\n```\n\n**Deploy the embed widget**:\n```html\n\u003C!-- Paste near end of \u003Cbody> tag -->\n\u003Cscript src=\"https:\u002F\u002Fembed.lindy.ai\u002Fwidget.js\"\n  data-lindy-id=\"YOUR_AGENT_ID\">\u003C\u002Fscript>\n```\n\n**KB configuration**:\n- Sources: Product docs, FAQ PDFs, knowledge articles\n- Fuzziness: 100 (semantic search)\n- Max Results: 5 (balance relevance vs context size)\n- Auto-resync: every 24 hours\n\n**Best for**: Customer support, FAQ bots, internal knowledge assistants\n\n## Architecture Decision Matrix\n\n| Pattern | Throughput | Latency | Complexity | Cost |\n|---------|-----------|---------|-----------|------|\n| Simple webhook | Low-Med | 2-15s | Low | Low |\n| Event-driven pipeline | High | 5-30s | Medium | Medium |\n| Multi-agent society | Low-Med | 30-120s | High | High |\n| Scheduled pipeline | Batch | N\u002FA | Medium | Predictable |\n| Chat + KB | Interactive | 2-10s | Low-Med | Per-message |\n\n## Error Handling\n\n| Pattern | Failure Mode | Recovery |\n|---------|-------------|----------|\n| Simple webhook | Agent fails | Retry webhook with backoff |\n| Event-driven | Router crash | Queue events, replay on recovery |\n| Multi-agent | Delegation fails | Orchestrator retries or skips |\n| Scheduled | Missed schedule | Next run catches up |\n| Chat + KB | KB empty | Fallback to generic response + escalate |\n\n## Resources\n- [Lindy Introduction](https:\u002F\u002Fdocs.lindy.ai\u002Ffundamentals\u002Flindy-101\u002Fintroduction)\n- [Delegation 101](https:\u002F\u002Fwww.lindy.ai\u002Facademy-lessons\u002Fdelegation-101)\n- [Building a Chatbot](https:\u002F\u002Fwww.lindy.ai\u002Facademy-lessons\u002Fbuilding-a-chatbot-101)\n- [Lindy Embed](https:\u002F\u002Fwww.lindy.ai\u002Fintegrations\u002Flindy-embed)\n\n## Next Steps\nProceed to Flagship tier skills for enterprise features: multi-env, observability,\nincident response, data handling, RBAC, and migration.\n","# Lindy Reference Architecture\n\n## Overview\nProduction-ready architecture patterns for integrating Lindy AI agents into\napplications. Covers webhook integration, multi-agent societies, event-driven\npipelines, and high-availability patterns.\n\n## Prerequisites\n- Understanding of Lindy agent model (triggers, actions, skills)\n- Familiarity with webhook-based architectures\n- Production requirements defined (throughput, latency, reliability)\n\n## Architecture 1: Simple Webhook Integration\nSingle agent triggered by your application, results sent via callback.\n\n```\n┌─────────────┐       POST (webhook)       ┌──────────────┐\n│  Your App   │ ─────────────────────────→  │ Lindy Agent  │\n│             │                             │              │\n│  \u002Fcallback  │ ←─────────────────────────  │ HTTP Request │\n│             │       POST (callback)       │   Action     │\n└─────────────┘                             └──────────────┘\n```\n\n**Implementation**:\n- Your app sends webhook with `callbackUrl` field\n- Lindy agent processes and responds via Send POST Request to Callback\n- Your app receives results asynchronously\n\n**Best for**: Simple automations (email triage, lead scoring, content generation)\n\n## Architecture 2: Event-Driven Pipeline\nMultiple event sources feed agents through a central webhook router.\n\n```\n┌──────────┐\n│ Stripe   │──webhook──┐\n└──────────┘           │\n                       ▼\n┌──────────┐     ┌───────────┐     ┌──────────────┐\n│ Shopify  │──→  │  Router   │──→  │ Lindy Agents │\n└──────────┘     │  Service  │     │              │\n                 └───────────┘     │ • Order Bot  │\n┌──────────┐           ▲          │ • Support Bot│\n│ Your App │──webhook──┘          │ • Analytics  │\n└──────────┘                      └──────────────┘\n```\n\n**Implementation**:\n```typescript\n\u002F\u002F Event router — maps events to specific Lindy agents\nconst agentWebhooks: Record\u003Cstring, string> = {\n  'order.created': process.env.LINDY_ORDER_AGENT_WEBHOOK!,\n  'customer.support_request': process.env.LINDY_SUPPORT_AGENT_WEBHOOK!,\n  'analytics.daily_report': process.env.LINDY_ANALYTICS_AGENT_WEBHOOK!,\n};\n\napp.post('\u002Fevents', async (req, res) => {\n  const { event, data } = req.body;\n  const webhookUrl = agentWebhooks[event];\n\n  if (!webhookUrl) {\n    return res.status(400).json({ error: `Unknown event: ${event}` });\n  }\n\n  await fetch(webhookUrl, {\n    method: 'POST',\n    headers: {\n      'Authorization': `Bearer ${process.env.LINDY_WEBHOOK_SECRET}`,\n      'Content-Type': 'application\u002Fjson',\n    },\n    body: JSON.stringify({ event, data, callbackUrl: `${BASE_URL}\u002Fcallback` }),\n  });\n\n  res.json({ routed: true, agent: event });\n});\n```\n\n**Best for**: Multiple event sources, different agents per event type\n\n## Architecture 3: Multi-Agent Society (Delegation)\nSpecialized agents collaborate through Lindy's built-in delegation system.\n\n```\n┌─────────────────┐\n│ Orchestrator    │\n│ Lindy           │\n│ (receives       │\n│  initial task)  │\n└───┬────────┬────┘\n    │        │\n    ▼        ▼\n┌────────┐ ┌────────┐\n│Research│ │Analysis│\n│ Lindy  │ │ Lindy  │\n└───┬────┘ └───┬────┘\n    │          │\n    ▼          ▼\n┌─────────────────┐\n│ Writer Lindy    │\n│ (synthesizes    │\n│  final output)  │\n└─────────────────┘\n```\n\n**Setup in Lindy**:\n1. Create specialized agents with **Agent Message Received** triggers\n2. Orchestrator uses **Agent Send Message** action to delegate\n3. Each agent completes its specialty and sends results forward\n4. Writer agent synthesizes and delivers final output\n\n**Key decisions**:\n| Decision | Option A | Option B |\n|----------|---------|---------|\n| Context passing | Full context (accurate, expensive) | Selective context (cheap, focused) |\n| Error handling | Agent retries | Orchestrator retry logic |\n| Parallelism | Sequential delegation | Parallel delegation with merge |\n\n**Best for**: Complex tasks requiring multiple specialties (research + analysis + writing)\n\n## Architecture 4: Scheduled Pipeline\nAgents run on schedules, each feeding data to the next.\n\n```\n                    Schedule: Daily 6 AM\n                         │\n                         ▼\n                  ┌──────────────┐\n                  │ Data Fetch   │ Pulls from APIs\u002Fdatabases\n                  │ Lindy        │\n                  └──────┬───────┘\n                         │ Agent Send Message\n                         ▼\n                  ┌──────────────┐\n                  │ Analysis     │ Processes & summarizes\n                  │ Lindy        │\n                  └──────┬───────┘\n                         │ Agent Send Message\n                         ▼\n                  ┌──────────────┐\n                  │ Report       │ Formats & delivers\n                  │ Lindy        │\n                  │  → Slack     │\n                  │  → Email     │\n                  └──────────────┘\n```\n\n**Best for**: Daily reports, weekly digests, scheduled data processing\n\n## Architecture 5: Chat + Knowledge Base\nAgent deployed as customer-facing chatbot with RAG-powered responses.\n\n```\n┌──────────────┐     ┌──────────────┐     ┌──────────────┐\n│  Website     │     │ Lindy Agent  │     │ Knowledge    │\n│  (Embed      │◀──▶ │              │◀──▶ │ Base         │\n│   Widget)    │     │ Chat Trigger │     │ PDFs, Docs,  │\n└──────────────┘     │ + KB Search  │     │ Websites     │\n                     │ + Condition  │     └──────────────┘\n                     │ + Escalate   │\n                     └──────────────┘\n                            │\n                            ▼ (if escalation needed)\n                     ┌──────────────┐\n                     │ Slack DM to  │\n                     │ human agent  │\n                     └──────────────┘\n```\n\n**Deploy the embed widget**:\n```html\n\u003C!-- Paste near end of \u003Cbody> tag -->\n\u003Cscript src=\"https:\u002F\u002Fembed.lindy.ai\u002Fwidget.js\"\n  data-lindy-id=\"YOUR_AGENT_ID\">\u003C\u002Fscript>\n```\n\n**KB configuration**:\n- Sources: Product docs, FAQ PDFs, knowledge articles\n- Fuzziness: 100 (semantic search)\n- Max Results: 5 (balance relevance vs context size)\n- Auto-resync: every 24 hours\n\n**Best for**: Customer support, FAQ bots, internal knowledge assistants\n\n## Architecture Decision Matrix\n\n| Pattern | Throughput | Latency | Complexity | Cost |\n|---------|-----------|---------|-----------|------|\n| Simple webhook | Low-Med | 2-15s | Low | Low |\n| Event-driven pipeline | High | 5-30s | Medium | Medium |\n| Multi-agent society | Low-Med | 30-120s | High | High |\n| Scheduled pipeline | Batch | N\u002FA | Medium | Predictable |\n| Chat + KB | Interactive | 2-10s | Low-Med | Per-message |\n\n## Error Handling\n\n| Pattern | Failure Mode | Recovery |\n|---------|-------------|----------|\n| Simple webhook | Agent fails | Retry webhook with backoff |\n| Event-driven | Router crash | Queue events, replay on recovery |\n| Multi-agent | Delegation fails | Orchestrator retries or skips |\n| Scheduled | Missed schedule | Next run catches up |\n| Chat + KB | KB empty | Fallback to generic response + escalate |\n\n## Resources\n- [Lindy Introduction](https:\u002F\u002Fdocs.lindy.ai\u002Ffundamentals\u002Flindy-101\u002Fintroduction)\n- [Delegation 101](https:\u002F\u002Fwww.lindy.ai\u002Facademy-lessons\u002Fdelegation-101)\n- [Building a Chatbot](https:\u002F\u002Fwww.lindy.ai\u002Facademy-lessons\u002Fbuilding-a-chatbot-101)\n- [Lindy Embed](https:\u002F\u002Fwww.lindy.ai\u002Fintegrations\u002Flindy-embed)\n\n## Next Steps\nProceed to Flagship tier skills for enterprise features: multi-env, observability,\nincident response, data handling, RBAC, and migration.\n",{"name":5,"tags":24,"author":28,"license":15,"version":29,"description":30,"allowed-tools":31,"compatible-with":32},[25,26,27],"saas","lindy","lindy-reference","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Reference architectures for Lindy AI agent integrations.\nUse when designing systems, planning multi-agent architectures,\nor implementing production integration patterns.\nTrigger with phrases like \"lindy architecture\", \"lindy design\",\n\"lindy system design\", \"lindy patterns\", \"lindy multi-agent\".\n","Read, Write, Edit","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--lindy-pack--lindy-reference-architecture",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":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill lindy-reference-architecture",{"tool":48,"command":49},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill lindy-reference-architecture",{"tool":51,"command":52},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill lindy-reference-architecture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--lindy-pack--lindy-reference-architecture\u002FSKILL.md",true,[],[57,64,71,78,85,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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",[],[]]