[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M736BWZQV5S74JBVR4R73FSZ":3,"skill-same:01M736BWZQV5S74JBVR4R73FSZ":80},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M736BWZQV5S74JBVR4R73FSZ","workflow-launchers",null,"Configure and deploy Workflow Launchers that automatically start workflows in response to JCR content changes on AEM as a Cloud Service","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-launchers\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: workflow-launchers\ndescription: Configure and deploy Workflow Launchers that automatically start workflows in response to JCR content changes on AEM as a Cloud Service\nlicense: Apache-2.0\n---\n\n# Workflow Launchers Skill — AEM as a Cloud Service\n\n## Purpose\n\nThis skill teaches you how to configure and deploy Workflow Launchers that automatically start workflows in response to JCR content changes on AEM as a Cloud Service.\n\n## When to Use This Skill\n\n- A workflow must start automatically when an asset is uploaded to DAM\n- A review workflow should trigger whenever an author modifies content under a specific path\n- You need to replicate or replace an OOTB launcher behavior without editing `\u002Flibs`\n- You want to enable, disable, or restrict a launcher to specific run modes\n\n## Core Concept: What Is a Workflow Launcher?\n\nA **Workflow Launcher** (`cq:WorkflowLauncher`) is a JCR node that registers a JCR event listener. When a node event occurs at a path matching the launcher's glob pattern, node type, and conditions, the Granite Workflow Engine enqueues a workflow start.\n\nThe listener is managed by `WorkflowLauncherListener` (an OSGi service). It reads all active launcher configurations at startup and re-evaluates them when configurations change.\n\n## Architecture at a Glance\n\n```\nJCR Event (NODE_ADDED \u002F NODE_MODIFIED \u002F NODE_REMOVED)\n    ↓\nWorkflowLauncherListener (OSGi EventListener)\n    ↓ matches: glob, nodetype, event type, conditions\nWorkflow Engine: enqueue WorkflowData\n    ↓\nWorkflow Instance created at \u002Fvar\u002Fworkflow\u002Finstances\u002F\n```\n\n## Launcher Configuration Properties\n\n| Property | Type | Description |\n|---|---|---|\n| `eventType` | Long | `1` = NODE_ADDED, `2` = NODE_MODIFIED, `4` = NODE_REMOVED, `8` = PROPERTY_ADDED, `16` = PROPERTY_CHANGED, `32` = PROPERTY_REMOVED |\n| `glob` | String | Glob pattern matched against the event node path (e.g., `\u002Fcontent\u002Fdam(\u002F.*)?`) |\n| `nodetype` | String | JCR node type the event node must be (e.g., `dam:AssetContent`) |\n| `conditions` | String[] | Additional JCR property conditions on the event node |\n| `workflow` | String | Runtime path of the workflow model `\u002Fvar\u002Fworkflow\u002Fmodels\u002F\u003Cid>` |\n| `enabled` | Boolean | Whether the launcher is active |\n| `description` | String | Human-readable description |\n| `excludeList` | String[] | Workflow model IDs to exclude |\n| `runModes` | String[] | Restrict to specific run modes (e.g., `author`) |\n\n## Deploying a Custom Launcher on Cloud Service\n\nOn Cloud Service, `\u002Flibs` is immutable. Store launcher configurations at:\n```\n\u002Fconf\u002Fglobal\u002Fsettings\u002Fworkflow\u002Flauncher\u002Fconfig\u002F\u003Clauncher-name>\n```\n\nMaven project location:\n```\nui.content\u002Fsrc\u002Fmain\u002Fcontent\u002Fjcr_root\u002Fconf\u002Fglobal\u002Fsettings\u002Fworkflow\u002Flauncher\u002Fconfig\u002F\n    my-custom-launcher\u002F\n        .content.xml\n```\n\nFilter in `filter.xml`:\n```xml\n\u003Cfilter root=\"\u002Fconf\u002Fglobal\u002Fsettings\u002Fworkflow\u002Flauncher\u002Fconfig\u002Fmy-custom-launcher\"\u002F>\n```\n\nNode structure (`.content.xml`):\n```xml\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\"?>\n\u003Cjcr:root\n    xmlns:jcr=\"http:\u002F\u002Fwww.jcp.org\u002Fjcr\u002F1.0\"\n    xmlns:cq=\"http:\u002F\u002Fwww.day.com\u002Fjcr\u002Fcq\u002F1.0\"\n    jcr:primaryType=\"cq:WorkflowLauncher\"\n    eventType=\"{Long}1\"\n    glob=\"\u002Fcontent\u002Fdam(\u002F.*)?\u002Fjcr:content\u002Frenditions\u002Foriginal\"\n    nodetype=\"nt:file\"\n    workflow=\"\u002Fvar\u002Fworkflow\u002Fmodels\u002Fdam\u002Fupdate_asset\"\n    enabled=\"{Boolean}true\"\n    description=\"Start DAM update workflow on new original rendition upload\"\n    runModes=\"[author]\"\u002F>\n```\n\n## Overlaying an OOTB Launcher\n\nTo disable or modify an OOTB launcher (e.g., `dam_update_asset_create`):\n\n1. Copy the node from `\u002Flibs\u002Fsettings\u002Fworkflow\u002Flauncher\u002Fconfig\u002Fdam_update_asset_create` to `\u002Fconf\u002Fglobal\u002Fsettings\u002Fworkflow\u002Flauncher\u002Fconfig\u002Fdam_update_asset_create`\n2. Modify the property (e.g., set `enabled=\"{Boolean}false\"` to disable it)\n3. Deploy as a content package via Cloud Manager\n\n## Common OOTB Launchers (Cloud Service)\n\n| Launcher | Trigger | Workflow |\n|---|---|---|\n| `dam_update_asset_create` | NODE_ADDED on `dam:AssetContent` under `\u002Fcontent\u002Fdam` | DAM Update Asset |\n| `dam_update_asset_modify` | NODE_MODIFIED on asset properties | DAM Update Asset |\n| `dam_xmp_writeback` | NODE_MODIFIED on rendition | DAM Writeback |\n| `update_page_version_*` | Node events on cq:Page jcr:content | Page Version Create |\n\n## Event Type Combinations\n\nTo listen for both ADD and MODIFY, combine event types:\n```xml\neventType=\"{Long}3\"  \u003C!-- 1 (ADD) + 2 (MODIFY) = 3 -->\n```\n\n## Where-Clause Conditions\n\nThe `conditions` array lets you add JCR property conditions on the triggering node:\n\n```xml\nconditions=\"[property=cq:type,value=publicationevent,type=STRING]\"\n```\n\nCondition format: `property=\u003Cname>,value=\u003Cvalue>,type=\u003CJCR_TYPE>` (type is optional, defaults to STRING).\n\n## Disabling a Launcher for a Run Mode\n\nUse `runModes` to restrict:\n```xml\nrunModes=\"[author]\"   \u003C!-- only fires on Author -->\nrunModes=\"[publish]\"  \u003C!-- only fires on Publish -->\n```\n\nOmit `runModes` to fire on all run modes.\n\n## Debugging Launchers\n\n- **Tools → Workflow → Launchers** UI — lists all active launchers, you can enable\u002Fdisable interactively\n- Check `\u002Fconf\u002Fglobal\u002Fsettings\u002Fworkflow\u002Flauncher\u002Fconfig\u002F` in CRXDE Lite for your deployed configs\n- Check OSGi console → `WorkflowLauncherListener` service properties\n- After deployment, verify via: `curl -u admin:admin http:\u002F\u002Flocalhost:4502\u002Fetc\u002Fworkflow\u002Flauncher.json`\n\n## References in This Skill\n\n| Reference | What It Covers |\n|---|---|\n| `references\u002Fworkflow-launchers\u002Flauncher-config-reference.md` | Full property spec and XML templates |\n| `references\u002Fworkflow-launchers\u002Fcondition-patterns.md` | Common condition patterns, glob syntax, event type codes |\n| `references\u002Fworkflow-foundation\u002Farchitecture-overview.md` | Granite Workflow Engine overview |\n| `references\u002Fworkflow-foundation\u002Fcloud-service-guardrails.md` | Cloud Service constraints for config paths |\n| `references\u002Fworkflow-foundation\u002Fjcr-paths-reference.md` | Where launchers live in the JCR |\n","# Workflow Launchers Skill — AEM as a Cloud Service\n\n## Purpose\n\nThis skill teaches you how to configure and deploy Workflow Launchers that automatically start workflows in response to JCR content changes on AEM as a Cloud Service.\n\n## When to Use This Skill\n\n- A workflow must start automatically when an asset is uploaded to DAM\n- A review workflow should trigger whenever an author modifies content under a specific path\n- You need to replicate or replace an OOTB launcher behavior without editing `\u002Flibs`\n- You want to enable, disable, or restrict a launcher to specific run modes\n\n## Core Concept: What Is a Workflow Launcher?\n\nA **Workflow Launcher** (`cq:WorkflowLauncher`) is a JCR node that registers a JCR event listener. When a node event occurs at a path matching the launcher's glob pattern, node type, and conditions, the Granite Workflow Engine enqueues a workflow start.\n\nThe listener is managed by `WorkflowLauncherListener` (an OSGi service). It reads all active launcher configurations at startup and re-evaluates them when configurations change.\n\n## Architecture at a Glance\n\n```\nJCR Event (NODE_ADDED \u002F NODE_MODIFIED \u002F NODE_REMOVED)\n    ↓\nWorkflowLauncherListener (OSGi EventListener)\n    ↓ matches: glob, nodetype, event type, conditions\nWorkflow Engine: enqueue WorkflowData\n    ↓\nWorkflow Instance created at \u002Fvar\u002Fworkflow\u002Finstances\u002F\n```\n\n## Launcher Configuration Properties\n\n| Property | Type | Description |\n|---|---|---|\n| `eventType` | Long | `1` = NODE_ADDED, `2` = NODE_MODIFIED, `4` = NODE_REMOVED, `8` = PROPERTY_ADDED, `16` = PROPERTY_CHANGED, `32` = PROPERTY_REMOVED |\n| `glob` | String | Glob pattern matched against the event node path (e.g., `\u002Fcontent\u002Fdam(\u002F.*)?`) |\n| `nodetype` | String | JCR node type the event node must be (e.g., `dam:AssetContent`) |\n| `conditions` | String[] | Additional JCR property conditions on the event node |\n| `workflow` | String | Runtime path of the workflow model `\u002Fvar\u002Fworkflow\u002Fmodels\u002F\u003Cid>` |\n| `enabled` | Boolean | Whether the launcher is active |\n| `description` | String | Human-readable description |\n| `excludeList` | String[] | Workflow model IDs to exclude |\n| `runModes` | String[] | Restrict to specific run modes (e.g., `author`) |\n\n## Deploying a Custom Launcher on Cloud Service\n\nOn Cloud Service, `\u002Flibs` is immutable. Store launcher configurations at:\n```\n\u002Fconf\u002Fglobal\u002Fsettings\u002Fworkflow\u002Flauncher\u002Fconfig\u002F\u003Clauncher-name>\n```\n\nMaven project location:\n```\nui.content\u002Fsrc\u002Fmain\u002Fcontent\u002Fjcr_root\u002Fconf\u002Fglobal\u002Fsettings\u002Fworkflow\u002Flauncher\u002Fconfig\u002F\n    my-custom-launcher\u002F\n        .content.xml\n```\n\nFilter in `filter.xml`:\n```xml\n\u003Cfilter root=\"\u002Fconf\u002Fglobal\u002Fsettings\u002Fworkflow\u002Flauncher\u002Fconfig\u002Fmy-custom-launcher\"\u002F>\n```\n\nNode structure (`.content.xml`):\n```xml\n\u003C?xml version=\"1.0\" encoding=\"UTF-8\"?>\n\u003Cjcr:root\n    xmlns:jcr=\"http:\u002F\u002Fwww.jcp.org\u002Fjcr\u002F1.0\"\n    xmlns:cq=\"http:\u002F\u002Fwww.day.com\u002Fjcr\u002Fcq\u002F1.0\"\n    jcr:primaryType=\"cq:WorkflowLauncher\"\n    eventType=\"{Long}1\"\n    glob=\"\u002Fcontent\u002Fdam(\u002F.*)?\u002Fjcr:content\u002Frenditions\u002Foriginal\"\n    nodetype=\"nt:file\"\n    workflow=\"\u002Fvar\u002Fworkflow\u002Fmodels\u002Fdam\u002Fupdate_asset\"\n    enabled=\"{Boolean}true\"\n    description=\"Start DAM update workflow on new original rendition upload\"\n    runModes=\"[author]\"\u002F>\n```\n\n## Overlaying an OOTB Launcher\n\nTo disable or modify an OOTB launcher (e.g., `dam_update_asset_create`):\n\n1. Copy the node from `\u002Flibs\u002Fsettings\u002Fworkflow\u002Flauncher\u002Fconfig\u002Fdam_update_asset_create` to `\u002Fconf\u002Fglobal\u002Fsettings\u002Fworkflow\u002Flauncher\u002Fconfig\u002Fdam_update_asset_create`\n2. Modify the property (e.g., set `enabled=\"{Boolean}false\"` to disable it)\n3. Deploy as a content package via Cloud Manager\n\n## Common OOTB Launchers (Cloud Service)\n\n| Launcher | Trigger | Workflow |\n|---|---|---|\n| `dam_update_asset_create` | NODE_ADDED on `dam:AssetContent` under `\u002Fcontent\u002Fdam` | DAM Update Asset |\n| `dam_update_asset_modify` | NODE_MODIFIED on asset properties | DAM Update Asset |\n| `dam_xmp_writeback` | NODE_MODIFIED on rendition | DAM Writeback |\n| `update_page_version_*` | Node events on cq:Page jcr:content | Page Version Create |\n\n## Event Type Combinations\n\nTo listen for both ADD and MODIFY, combine event types:\n```xml\neventType=\"{Long}3\"  \u003C!-- 1 (ADD) + 2 (MODIFY) = 3 -->\n```\n\n## Where-Clause Conditions\n\nThe `conditions` array lets you add JCR property conditions on the triggering node:\n\n```xml\nconditions=\"[property=cq:type,value=publicationevent,type=STRING]\"\n```\n\nCondition format: `property=\u003Cname>,value=\u003Cvalue>,type=\u003CJCR_TYPE>` (type is optional, defaults to STRING).\n\n## Disabling a Launcher for a Run Mode\n\nUse `runModes` to restrict:\n```xml\nrunModes=\"[author]\"   \u003C!-- only fires on Author -->\nrunModes=\"[publish]\"  \u003C!-- only fires on Publish -->\n```\n\nOmit `runModes` to fire on all run modes.\n\n## Debugging Launchers\n\n- **Tools → Workflow → Launchers** UI — lists all active launchers, you can enable\u002Fdisable interactively\n- Check `\u002Fconf\u002Fglobal\u002Fsettings\u002Fworkflow\u002Flauncher\u002Fconfig\u002F` in CRXDE Lite for your deployed configs\n- Check OSGi console → `WorkflowLauncherListener` service properties\n- After deployment, verify via: `curl -u admin:admin http:\u002F\u002Flocalhost:4502\u002Fetc\u002Fworkflow\u002Flauncher.json`\n\n## References in This Skill\n\n| Reference | What It Covers |\n|---|---|\n| `references\u002Fworkflow-launchers\u002Flauncher-config-reference.md` | Full property spec and XML templates |\n| `references\u002Fworkflow-launchers\u002Fcondition-patterns.md` | Common condition patterns, glob syntax, event type codes |\n| `references\u002Fworkflow-foundation\u002Farchitecture-overview.md` | Granite Workflow Engine overview |\n| `references\u002Fworkflow-foundation\u002Fcloud-service-guardrails.md` | Cloud Service constraints for config paths |\n| `references\u002Fworkflow-foundation\u002Fjcr-paths-reference.md` | Where launchers live in the JCR |\n",{"name":5,"license":15,"description":7},"main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fadobe-aem-workflow\u002Fworkflow-launchers","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack","https:\u002F\u002Fgithub.com\u002Fkalash33","kalashpoddar.me","Tech-savvy Full Stack Developer 🚀 | Cybersecurity enthusiast 🔒 | Passionate about innovation and securing the digital world 🌐 | Let's code securely! 💻🔐","2026-05-20 04:11:22",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add kalash33\u002Fkstack --skill workflow-launchers",{"tool":38,"command":39},"bunx","bunx skills add kalash33\u002Fkstack --skill workflow-launchers",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill workflow-launchers","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-launchers\u002FSKILL.md",true,[46,52,56,60,64,68,72,76],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"references\u002Fworkflow-foundation\u002Fapi-reference.md","REFERENCE","参考文档",3606,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-launchers\u002Freferences\u002Fworkflow-foundation\u002Fapi-reference.md",{"path":53,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fworkflow-foundation\u002Farchitecture-overview.md",2363,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-launchers\u002Freferences\u002Fworkflow-foundation\u002Farchitecture-overview.md",{"path":57,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fworkflow-foundation\u002Fcloud-service-guardrails.md",2724,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-launchers\u002Freferences\u002Fworkflow-foundation\u002Fcloud-service-guardrails.md",{"path":61,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fworkflow-foundation\u002Fjcr-paths-reference.md",2481,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-launchers\u002Freferences\u002Fworkflow-foundation\u002Fjcr-paths-reference.md",{"path":65,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Fworkflow-foundation\u002Fquick-start-guide.md",2038,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-launchers\u002Freferences\u002Fworkflow-foundation\u002Fquick-start-guide.md",{"path":69,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":70,"sourceHtmlUrl":71},"references\u002Fworkflow-foundation\u002FREADME.md",826,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-launchers\u002Freferences\u002Fworkflow-foundation\u002FREADME.md",{"path":73,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fworkflow-launchers\u002Fcondition-patterns.md",4202,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-launchers\u002Freferences\u002Fworkflow-launchers\u002Fcondition-patterns.md",{"path":77,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fworkflow-launchers\u002Flauncher-config-reference.md",5093,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-launchers\u002Freferences\u002Fworkflow-launchers\u002Flauncher-config-reference.md",[81,89,96,103,110,117],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M73CFERCR43JCAP606E41EFB","zustand-store-ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reacti...","MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M73CFCMFVTAQEMTZ5HR10X8V","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M73CFAA7EBWXJVXDQ1X555MB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M73CF80XCM9K81567MJ8QZFW","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M73CF4YPMF3RA8ZJDXZSMD93","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":85,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":19},"01M73CF2S25EN3XNAMKY47XHPS","zendesk-automation","Automate Zendesk tasks via Rube MCP (Composio): tickets, users, organizations, replies. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzendesk-automation\u002FSKILL.md",[],[]]