[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M736C30G4JH3GAPQ14XNJG5C":3,"skill-same:01M736C30G4JH3GAPQ14XNJG5C":72},{"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},"01M736C30G4JH3GAPQ14XNJG5C","workflow-orchestrator",null,"Master entry point for all AEM Workflow tasks on Cloud Service spanning development and production support","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-orchestrator\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: workflow-orchestrator\ndescription: Master entry point for all AEM Workflow tasks on Cloud Service spanning development and production support\nlicense: Apache-2.0\n---\n\n# Workflow Orchestrator — AEM as a Cloud Service\n\n## Purpose\n\nThis is the **master entry point** for all AEM Workflow tasks on Cloud Service — spanning both **development** (building workflows) and **production support** (debugging and triaging workflow issues). Read this skill first. It classifies the user's request and routes to the right sub-skill.\n\n## How to Use This Skill\n\n1. Read the user's request carefully\n2. Classify it using the **Task Classifier** table below\n3. Load the identified sub-skill's `SKILL.md` and its references\n4. For development tasks, always load the `workflow-foundation` references alongside the sub-skill references\n5. For production-support tasks, the debugging and triaging skills are self-contained\n\n---\n\n## Task Classifier\n\n### Development Skills\n\n| User Says \u002F Asks | Sub-Skill to Load |\n|---|---|\n| \"Create a workflow model\", \"Add steps to a workflow\", \"Design an OR split\", \"I need a parallel review\" | `workflow-model-design` |\n| \"Implement a custom process step\", \"Write a WorkflowProcess\", \"Create a ParticipantStepChooser\", \"Dynamic participant\" | `workflow-development` |\n| \"Start a workflow from code\", \"Trigger a workflow via API\", \"Use Manage Publication with a workflow\", \"HTTP REST API to start a workflow\" | `workflow-triggering` |\n| \"Configure a launcher\", \"Auto-start on asset upload\", \"Launcher not firing\", \"cq:WorkflowLauncher\", \"Overlay an OOTB launcher\" | `workflow-launchers` |\n| \"How do workflows work?\", \"Explain workflow architecture\" | Load `workflow-foundation` references only |\n\n### Production Support Skills\n\n| User Says \u002F Asks | Sub-Skill to Load |\n|---|---|\n| \"Workflow is stuck\", \"Why isn't my workflow advancing?\", \"No work item\", \"Workflow failed\", \"Step shows error\" | `workflow-debugging` |\n| \"Task not in Inbox\", \"User can't see work item\", \"Permissions error on workflow\" | `workflow-debugging` |\n| \"Thread pool exhausted\", \"Auto-advancement not working\", \"Queue backlog\", \"Sling Jobs stuck\" | `workflow-debugging` |\n| \"Repository bloat\", \"Too many workflow instances\", \"Purge not working\", \"Stale workflows\" | `workflow-debugging` |\n| \"What workflow errors on host X?\", \"Workflow activity for the past N hours\", \"What should I collect?\" | `workflow-triaging` |\n| \"Classify this workflow ticket\", \"What Splunk query should I use?\", \"What logs do I need?\" | `workflow-triaging` |\n| \"Why did workflow X fail? Show me the error.\", \"Failure details for model Y\" | `workflow-triaging` |\n\n**Routing heuristic:**\n- Building\u002Fimplementing workflows → development skills (`workflow-model-design`, `workflow-development`, `workflow-triggering`, `workflow-launchers`)\n- Deep troubleshooting (decision trees, config checks, thread analysis, remediation) → `workflow-debugging`\n- Incident classification (symptom → runbook, log patterns, Splunk, data gathering) → `workflow-triaging`\n- When both debugging and triaging apply, start with `workflow-triaging` to classify, then `workflow-debugging` for resolution\n\n---\n\n## Reference Loading Order\n\nFor every workflow task on Cloud Service, load in this order:\n\n### Step 1: Always load these foundation references\n\n```\nworkflow-orchestrator\u002Freferences\u002Fworkflow-foundation\u002Farchitecture-overview.md\nworkflow-orchestrator\u002Freferences\u002Fworkflow-foundation\u002Fapi-reference.md\nworkflow-orchestrator\u002Freferences\u002Fworkflow-foundation\u002Fjcr-paths-reference.md\nworkflow-orchestrator\u002Freferences\u002Fworkflow-foundation\u002Fcloud-service-guardrails.md\nworkflow-orchestrator\u002Freferences\u002Fworkflow-foundation\u002Fquick-start-guide.md\n```\n\n### Step 2: Load the sub-skill's SKILL.md\n\n```\nworkflow-model-design\u002FSKILL.md         ← for model design tasks\nworkflow-development\u002FSKILL.md          ← for Java implementation tasks\nworkflow-triggering\u002FSKILL.md           ← for start\u002Ftrigger tasks\nworkflow-launchers\u002FSKILL.md            ← for launcher config tasks\nworkflow-debugging\u002FSKILL.md            ← for production debugging tasks\nworkflow-triaging\u002FSKILL.md             ← for incident triage tasks\n```\n\n### Step 3: Load the sub-skill's topic references\n\n**workflow-model-design:**\n```\nworkflow-model-design\u002Freferences\u002Fworkflow-model-design\u002Fstep-types-catalog.md\nworkflow-model-design\u002Freferences\u002Fworkflow-model-design\u002Fmodel-xml-reference.md\nworkflow-model-design\u002Freferences\u002Fworkflow-model-design\u002Fmodel-design-patterns.md\n```\n\n**workflow-development:**\n```\nworkflow-development\u002Freferences\u002Fworkflow-development\u002Fprocess-step-patterns.md\nworkflow-development\u002Freferences\u002Fworkflow-development\u002Fparticipant-step-patterns.md\nworkflow-development\u002Freferences\u002Fworkflow-development\u002Fvariables-and-metadata.md\n```\n\n**workflow-triggering:**\n```\nworkflow-triggering\u002Freferences\u002Fworkflow-triggering\u002Ftriggering-mechanisms.md\nworkflow-triggering\u002Freferences\u002Fworkflow-triggering\u002Fprogrammatic-api.md\n```\n\n**workflow-launchers:**\n```\nworkflow-launchers\u002Freferences\u002Fworkflow-launchers\u002Flauncher-config-reference.md\nworkflow-launchers\u002Freferences\u002Fworkflow-launchers\u002Fcondition-patterns.md\n```\n\n**workflow-debugging:**\n```\nworkflow-debugging\u002FSKILL.md\nworkflow-debugging\u002Freference.md\n```\n\n**workflow-triaging:**\n```\nworkflow-triaging\u002FSKILL.md\n```\n\n---\n\n## Cloud Service Production Support Constraints\n\n| Constraint | Detail |\n|---|---|\n| No JMX | No `retryFailedWorkItems`, `countStaleWorkflows`, `restartStaleWorkflows`, `purgeCompleted` via JMX |\n| Retry failed items | Inbox Retry only |\n| Stale detection | Custom API\u002Fscript only |\n| Purge | Purge Scheduler (OSGi config in Git) |\n| Log access | Cloud Manager → Environments → Logs (download \u002F streaming) |\n| Thread dumps | Developer Console or support request |\n| Config changes | Code in Git + Cloud Manager pipeline deploy |\n\n---\n\n## AEM Cloud Service Guardrails Summary\n\nBefore doing anything, apply these non-negotiable constraints:\n\n| Rule | Detail |\n|---|---|\n| `\u002Flibs` is immutable | Never write to `\u002Flibs`; use `\u002Fconf\u002Fglobal\u002F` or `\u002Fapps\u002F` overlays |\n| Model design-time path | `\u002Fconf\u002Fglobal\u002Fsettings\u002Fworkflow\u002Fmodels\u002F\u003Cid>` |\n| Model runtime path (for API calls) | `\u002Fvar\u002Fworkflow\u002Fmodels\u002F\u003Cid>` |\n| Launcher config path | `\u002Fconf\u002Fglobal\u002Fsettings\u002Fworkflow\u002Flauncher\u002Fconfig\u002F` |\n| Service users | Always use `workflow-process-service` sub-service; never admin credentials |\n| OSGi annotations | Use DS R6 (`@Component`, `@Reference` from `org.osgi.service.component.annotations`) |\n| Deploy via | Cloud Manager pipeline — no Package Manager in production |\n| No `javax.jcr.Session.loginAdministrative` | Use `ResourceResolverFactory.getServiceResourceResolver()` |\n\nFull detail: `references\u002Fworkflow-foundation\u002Fcloud-service-guardrails.md`\n\n---\n\n## Quick Architecture Recap\n\n```\nAuthor tier\n  │\n  ├── Content Author\n  │     └── triggers via: Timeline UI \u002F Manage Publication\n  │\n  ├── Custom code (OSGi service \u002F event handler \u002F scheduler)\n  │     └── triggers via: WorkflowSession.startWorkflow()\n  │\n  └── Workflow Launcher (cq:WorkflowLauncher)\n        └── triggers via: JCR observation events\n              ↓\n        Granite Workflow Engine\n              ↓\n        Workflow Instance (\u002Fvar\u002Fworkflow\u002Finstances\u002F)\n              ↓\n        Steps executed as Sling Jobs:\n          - PROCESS step  → WorkflowProcess.execute()\n          - PARTICIPANT step → inbox task for user\u002Fgroup\n          - DYNAMIC_PARTICIPANT → ParticipantStepChooser.getParticipant()\n          - OR_SPLIT → route expression evaluates to true\u002Ffalse\n          - AND_SPLIT → parallel branches, AND_JOIN waits for all\n```\n\n---\n\n## Common Task Patterns (End-to-End)\n\n### Pattern A: New custom approval workflow\n\n1. Load `workflow-model-design` + `workflow-development` sub-skills\n2. Design model: START → PARTICIPANT (reviewer) → PROCESS (approve\u002Freject logic) → END\n3. Implement `WorkflowProcess` for the approve\u002Freject step\n4. Deploy model XML to `\u002Fconf\u002Fglobal\u002Fsettings\u002Fworkflow\u002Fmodels\u002F`\n5. Deploy OSGi bundle with the process step\n\n### Pattern B: Auto-process content on upload\n\n1. Load `workflow-launchers` sub-skill\n2. Configure a `cq:WorkflowLauncher` for `NODE_ADDED` on the DAM path\n3. Point it to your workflow model at `\u002Fvar\u002Fworkflow\u002Fmodels\u002F`\n4. Deploy launcher config to `\u002Fconf\u002Fglobal\u002Fsettings\u002Fworkflow\u002Flauncher\u002Fconfig\u002F`\n\n### Pattern C: Programmatically batch-start workflows\n\n1. Load `workflow-triggering` sub-skill\n2. Implement `WorkflowStarterService` using `ResourceResolverFactory` + `WorkflowSession`\n3. Map sub-service `workflow-starter` to `workflow-process-service`\n4. Deploy and trigger from a Sling Scheduler or Servlet\n\n### Pattern D: \"Workflow errors on host X for the past 4 hours\"\n\n1. Load `workflow-triaging` → classify as `workflow_fails_or_shows_error`\n2. Suggest Splunk \u002F Cloud Manager log search for `Error executing workflow step` on host + time range\n3. If errors found, load `workflow-debugging` → map to runbook, walk decision tree\n4. Return: symptom_id, runbook, evidence, remediation\n\n### Pattern E: \"Workflow stuck — not advancing\"\n\n1. Load `workflow-debugging` → classify as `workflow_stuck_not_progressing`\n2. Follow decision tree: check for work item → step type → specific checks\n3. If thread pool suspected, guide thread dump analysis (Developer Console)\n4. Return: root cause, config fix (via Git), remediation steps\n\n---\n\n## References in This Skill\n\n```\nreferences\u002Fworkflow-foundation\u002Farchitecture-overview.md\nreferences\u002Fworkflow-foundation\u002Fapi-reference.md\nreferences\u002Fworkflow-foundation\u002Fjcr-paths-reference.md\nreferences\u002Fworkflow-foundation\u002Fcloud-service-guardrails.md\nreferences\u002Fworkflow-foundation\u002Fquick-start-guide.md\n```\n","# Workflow Orchestrator — AEM as a Cloud Service\n\n## Purpose\n\nThis is the **master entry point** for all AEM Workflow tasks on Cloud Service — spanning both **development** (building workflows) and **production support** (debugging and triaging workflow issues). Read this skill first. It classifies the user's request and routes to the right sub-skill.\n\n## How to Use This Skill\n\n1. Read the user's request carefully\n2. Classify it using the **Task Classifier** table below\n3. Load the identified sub-skill's `SKILL.md` and its references\n4. For development tasks, always load the `workflow-foundation` references alongside the sub-skill references\n5. For production-support tasks, the debugging and triaging skills are self-contained\n\n---\n\n## Task Classifier\n\n### Development Skills\n\n| User Says \u002F Asks | Sub-Skill to Load |\n|---|---|\n| \"Create a workflow model\", \"Add steps to a workflow\", \"Design an OR split\", \"I need a parallel review\" | `workflow-model-design` |\n| \"Implement a custom process step\", \"Write a WorkflowProcess\", \"Create a ParticipantStepChooser\", \"Dynamic participant\" | `workflow-development` |\n| \"Start a workflow from code\", \"Trigger a workflow via API\", \"Use Manage Publication with a workflow\", \"HTTP REST API to start a workflow\" | `workflow-triggering` |\n| \"Configure a launcher\", \"Auto-start on asset upload\", \"Launcher not firing\", \"cq:WorkflowLauncher\", \"Overlay an OOTB launcher\" | `workflow-launchers` |\n| \"How do workflows work?\", \"Explain workflow architecture\" | Load `workflow-foundation` references only |\n\n### Production Support Skills\n\n| User Says \u002F Asks | Sub-Skill to Load |\n|---|---|\n| \"Workflow is stuck\", \"Why isn't my workflow advancing?\", \"No work item\", \"Workflow failed\", \"Step shows error\" | `workflow-debugging` |\n| \"Task not in Inbox\", \"User can't see work item\", \"Permissions error on workflow\" | `workflow-debugging` |\n| \"Thread pool exhausted\", \"Auto-advancement not working\", \"Queue backlog\", \"Sling Jobs stuck\" | `workflow-debugging` |\n| \"Repository bloat\", \"Too many workflow instances\", \"Purge not working\", \"Stale workflows\" | `workflow-debugging` |\n| \"What workflow errors on host X?\", \"Workflow activity for the past N hours\", \"What should I collect?\" | `workflow-triaging` |\n| \"Classify this workflow ticket\", \"What Splunk query should I use?\", \"What logs do I need?\" | `workflow-triaging` |\n| \"Why did workflow X fail? Show me the error.\", \"Failure details for model Y\" | `workflow-triaging` |\n\n**Routing heuristic:**\n- Building\u002Fimplementing workflows → development skills (`workflow-model-design`, `workflow-development`, `workflow-triggering`, `workflow-launchers`)\n- Deep troubleshooting (decision trees, config checks, thread analysis, remediation) → `workflow-debugging`\n- Incident classification (symptom → runbook, log patterns, Splunk, data gathering) → `workflow-triaging`\n- When both debugging and triaging apply, start with `workflow-triaging` to classify, then `workflow-debugging` for resolution\n\n---\n\n## Reference Loading Order\n\nFor every workflow task on Cloud Service, load in this order:\n\n### Step 1: Always load these foundation references\n\n```\nworkflow-orchestrator\u002Freferences\u002Fworkflow-foundation\u002Farchitecture-overview.md\nworkflow-orchestrator\u002Freferences\u002Fworkflow-foundation\u002Fapi-reference.md\nworkflow-orchestrator\u002Freferences\u002Fworkflow-foundation\u002Fjcr-paths-reference.md\nworkflow-orchestrator\u002Freferences\u002Fworkflow-foundation\u002Fcloud-service-guardrails.md\nworkflow-orchestrator\u002Freferences\u002Fworkflow-foundation\u002Fquick-start-guide.md\n```\n\n### Step 2: Load the sub-skill's SKILL.md\n\n```\nworkflow-model-design\u002FSKILL.md         ← for model design tasks\nworkflow-development\u002FSKILL.md          ← for Java implementation tasks\nworkflow-triggering\u002FSKILL.md           ← for start\u002Ftrigger tasks\nworkflow-launchers\u002FSKILL.md            ← for launcher config tasks\nworkflow-debugging\u002FSKILL.md            ← for production debugging tasks\nworkflow-triaging\u002FSKILL.md             ← for incident triage tasks\n```\n\n### Step 3: Load the sub-skill's topic references\n\n**workflow-model-design:**\n```\nworkflow-model-design\u002Freferences\u002Fworkflow-model-design\u002Fstep-types-catalog.md\nworkflow-model-design\u002Freferences\u002Fworkflow-model-design\u002Fmodel-xml-reference.md\nworkflow-model-design\u002Freferences\u002Fworkflow-model-design\u002Fmodel-design-patterns.md\n```\n\n**workflow-development:**\n```\nworkflow-development\u002Freferences\u002Fworkflow-development\u002Fprocess-step-patterns.md\nworkflow-development\u002Freferences\u002Fworkflow-development\u002Fparticipant-step-patterns.md\nworkflow-development\u002Freferences\u002Fworkflow-development\u002Fvariables-and-metadata.md\n```\n\n**workflow-triggering:**\n```\nworkflow-triggering\u002Freferences\u002Fworkflow-triggering\u002Ftriggering-mechanisms.md\nworkflow-triggering\u002Freferences\u002Fworkflow-triggering\u002Fprogrammatic-api.md\n```\n\n**workflow-launchers:**\n```\nworkflow-launchers\u002Freferences\u002Fworkflow-launchers\u002Flauncher-config-reference.md\nworkflow-launchers\u002Freferences\u002Fworkflow-launchers\u002Fcondition-patterns.md\n```\n\n**workflow-debugging:**\n```\nworkflow-debugging\u002FSKILL.md\nworkflow-debugging\u002Freference.md\n```\n\n**workflow-triaging:**\n```\nworkflow-triaging\u002FSKILL.md\n```\n\n---\n\n## Cloud Service Production Support Constraints\n\n| Constraint | Detail |\n|---|---|\n| No JMX | No `retryFailedWorkItems`, `countStaleWorkflows`, `restartStaleWorkflows`, `purgeCompleted` via JMX |\n| Retry failed items | Inbox Retry only |\n| Stale detection | Custom API\u002Fscript only |\n| Purge | Purge Scheduler (OSGi config in Git) |\n| Log access | Cloud Manager → Environments → Logs (download \u002F streaming) |\n| Thread dumps | Developer Console or support request |\n| Config changes | Code in Git + Cloud Manager pipeline deploy |\n\n---\n\n## AEM Cloud Service Guardrails Summary\n\nBefore doing anything, apply these non-negotiable constraints:\n\n| Rule | Detail |\n|---|---|\n| `\u002Flibs` is immutable | Never write to `\u002Flibs`; use `\u002Fconf\u002Fglobal\u002F` or `\u002Fapps\u002F` overlays |\n| Model design-time path | `\u002Fconf\u002Fglobal\u002Fsettings\u002Fworkflow\u002Fmodels\u002F\u003Cid>` |\n| Model runtime path (for API calls) | `\u002Fvar\u002Fworkflow\u002Fmodels\u002F\u003Cid>` |\n| Launcher config path | `\u002Fconf\u002Fglobal\u002Fsettings\u002Fworkflow\u002Flauncher\u002Fconfig\u002F` |\n| Service users | Always use `workflow-process-service` sub-service; never admin credentials |\n| OSGi annotations | Use DS R6 (`@Component`, `@Reference` from `org.osgi.service.component.annotations`) |\n| Deploy via | Cloud Manager pipeline — no Package Manager in production |\n| No `javax.jcr.Session.loginAdministrative` | Use `ResourceResolverFactory.getServiceResourceResolver()` |\n\nFull detail: `references\u002Fworkflow-foundation\u002Fcloud-service-guardrails.md`\n\n---\n\n## Quick Architecture Recap\n\n```\nAuthor tier\n  │\n  ├── Content Author\n  │     └── triggers via: Timeline UI \u002F Manage Publication\n  │\n  ├── Custom code (OSGi service \u002F event handler \u002F scheduler)\n  │     └── triggers via: WorkflowSession.startWorkflow()\n  │\n  └── Workflow Launcher (cq:WorkflowLauncher)\n        └── triggers via: JCR observation events\n              ↓\n        Granite Workflow Engine\n              ↓\n        Workflow Instance (\u002Fvar\u002Fworkflow\u002Finstances\u002F)\n              ↓\n        Steps executed as Sling Jobs:\n          - PROCESS step  → WorkflowProcess.execute()\n          - PARTICIPANT step → inbox task for user\u002Fgroup\n          - DYNAMIC_PARTICIPANT → ParticipantStepChooser.getParticipant()\n          - OR_SPLIT → route expression evaluates to true\u002Ffalse\n          - AND_SPLIT → parallel branches, AND_JOIN waits for all\n```\n\n---\n\n## Common Task Patterns (End-to-End)\n\n### Pattern A: New custom approval workflow\n\n1. Load `workflow-model-design` + `workflow-development` sub-skills\n2. Design model: START → PARTICIPANT (reviewer) → PROCESS (approve\u002Freject logic) → END\n3. Implement `WorkflowProcess` for the approve\u002Freject step\n4. Deploy model XML to `\u002Fconf\u002Fglobal\u002Fsettings\u002Fworkflow\u002Fmodels\u002F`\n5. Deploy OSGi bundle with the process step\n\n### Pattern B: Auto-process content on upload\n\n1. Load `workflow-launchers` sub-skill\n2. Configure a `cq:WorkflowLauncher` for `NODE_ADDED` on the DAM path\n3. Point it to your workflow model at `\u002Fvar\u002Fworkflow\u002Fmodels\u002F`\n4. Deploy launcher config to `\u002Fconf\u002Fglobal\u002Fsettings\u002Fworkflow\u002Flauncher\u002Fconfig\u002F`\n\n### Pattern C: Programmatically batch-start workflows\n\n1. Load `workflow-triggering` sub-skill\n2. Implement `WorkflowStarterService` using `ResourceResolverFactory` + `WorkflowSession`\n3. Map sub-service `workflow-starter` to `workflow-process-service`\n4. Deploy and trigger from a Sling Scheduler or Servlet\n\n### Pattern D: \"Workflow errors on host X for the past 4 hours\"\n\n1. Load `workflow-triaging` → classify as `workflow_fails_or_shows_error`\n2. Suggest Splunk \u002F Cloud Manager log search for `Error executing workflow step` on host + time range\n3. If errors found, load `workflow-debugging` → map to runbook, walk decision tree\n4. Return: symptom_id, runbook, evidence, remediation\n\n### Pattern E: \"Workflow stuck — not advancing\"\n\n1. Load `workflow-debugging` → classify as `workflow_stuck_not_progressing`\n2. Follow decision tree: check for work item → step type → specific checks\n3. If thread pool suspected, guide thread dump analysis (Developer Console)\n4. Return: root cause, config fix (via Git), remediation steps\n\n---\n\n## References in This Skill\n\n```\nreferences\u002Fworkflow-foundation\u002Farchitecture-overview.md\nreferences\u002Fworkflow-foundation\u002Fapi-reference.md\nreferences\u002Fworkflow-foundation\u002Fjcr-paths-reference.md\nreferences\u002Fworkflow-foundation\u002Fcloud-service-guardrails.md\nreferences\u002Fworkflow-foundation\u002Fquick-start-guide.md\n```\n",{"name":5,"license":15,"description":7},"main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fadobe-aem-workflow\u002Fworkflow-orchestrator","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-orchestrator",{"tool":38,"command":39},"bunx","bunx skills add kalash33\u002Fkstack --skill workflow-orchestrator",{"tool":41,"command":42},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill workflow-orchestrator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-aem-workflow\u002Fworkflow-orchestrator\u002FSKILL.md",true,[46,52,56,60,64,68],{"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-orchestrator\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-orchestrator\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-orchestrator\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-orchestrator\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-orchestrator\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-orchestrator\u002Freferences\u002Fworkflow-foundation\u002FREADME.md",[73,81,88,95,102,109],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"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":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":77,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"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",[],[]]