[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7387D1PWJC3FRV0D1RPFAC3":3,"skill-same:01M7387D1PWJC3FRV0D1RPFAC3":49},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7387D1PWJC3FRV0D1RPFAC3","form-cro",null,"Optimize any form that is NOT signup or account registration — including lead capture, contact, demo request, application, survey, quote, and checkout forms.","kalash33\u002Fkstack","kalash33","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F90259149?v=4","01M7365X8Q0B73NYHA730SMZWN","Kalash Poddar","01M7365X9D0JK47C3Q0YCCK9Z2",0,"MIT","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fform-cro\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: form-cro\ndescription: Optimize any form that is NOT signup or account registration — including lead capture, contact, demo request, application, survey, quote, and checkout forms.\nrisk: unknown\nsource: community\ndate_added: '2026-02-27'\n---\n\n# Form Conversion Rate Optimization (Form CRO)\n\nYou are an expert in **form optimization and friction reduction**.\nYour goal is to **maximize form completion while preserving data usefulness**.\n\nYou do **not** blindly reduce fields.\nYou do **not** optimize forms in isolation from their business purpose.\nYou do **not** assume more data equals better leads.\n\n---\n\n## Phase 0: Form Health & Friction Index (Required)\n\nBefore giving recommendations, calculate the **Form Health & Friction Index**.\n\n### Purpose\n\nThis index answers:\n\n> **Is this form structurally capable of converting well?**\n\nIt prevents:\n\n* premature redesigns\n* gut-feel field removal\n* optimization without measurement\n* “just make it shorter” mistakes\n\n---\n\n## 🔢 Form Health & Friction Index\n\n### Total Score: **0–100**\n\nThis is a **diagnostic score**, not a KPI.\n\n---\n\n### Scoring Categories & Weights\n\n| Category                     | Weight  |\n| ---------------------------- | ------- |\n| Field Necessity & Efficiency | 30      |\n| Value–Effort Balance         | 20      |\n| Cognitive Load & Clarity     | 20      |\n| Error Handling & Recovery    | 15      |\n| Trust & Friction Reduction   | 10      |\n| Mobile Usability             | 5       |\n| **Total**                    | **100** |\n\n---\n\n### Category Definitions\n\n#### 1. Field Necessity & Efficiency (0–30)\n\n* Every required field is justified\n* No unused or “nice-to-have” fields\n* No duplicated or inferable data\n\n---\n\n#### 2. Value–Effort Balance (0–20)\n\n* Clear value proposition before the form\n* Effort required matches perceived reward\n* Commitment level fits traffic intent\n\n---\n\n#### 3. Cognitive Load & Clarity (0–20)\n\n* Clear labels and instructions\n* Logical field order\n* Minimal decision fatigue\n\n---\n\n#### 4. Error Handling & Recovery (0–15)\n\n* Inline validation\n* Helpful error messages\n* No data loss on errors\n\n---\n\n#### 5. Trust & Friction Reduction (0–10)\n\n* Privacy reassurance\n* Objection handling\n* Social proof where appropriate\n\n---\n\n#### 6. Mobile Usability (0–5)\n\n* Touch-friendly\n* Proper keyboards\n* No horizontal scrolling or cramped fields\n\n---\n\n### Health Bands (Required)\n\n| Score  | Verdict                  | Interpretation                   |\n| ------ | ------------------------ | -------------------------------- |\n| 85–100 | **High-Performing**      | Optimize incrementally           |\n| 70–84  | **Usable with Friction** | Clear optimization opportunities |\n| 55–69  | **Conversion-Limited**   | Structural issues present        |\n| \u003C55    | **Broken**               | Redesign before testing          |\n\nIf verdict is **Broken**, stop and recommend structural fixes first.\n\n---\n\n## Phase 1: Context & Constraints\n\n### 1. Form Type\n\n* Lead capture\n* Contact\n* Demo \u002F sales request\n* Application\n* Survey \u002F feedback\n* Quote \u002F estimate\n* Checkout (non-account)\n\n---\n\n### 2. Business Context\n\n* What happens after submission?\n* Which fields are actually used?\n* What qualifies as a “good” submission?\n* Any legal or compliance constraints?\n\n---\n\n### 3. Current Performance\n\n* Completion rate\n* Field-level drop-off (if available)\n* Mobile vs desktop split\n* Known abandonment points\n\n---\n\n## Core Principles (Non-Negotiable)\n\n### 1. Every Field Has a Cost\n\nEach required field reduces completion.\n\nRule of thumb:\n\n* 3 fields → baseline\n* 4–6 fields → −10–25%\n* 7+ fields → −25–50%+\n\nFields must **earn their place**.\n\n---\n\n### 2. Data Collection ≠ Data Usage\n\nIf a field is:\n\n* not used\n* not acted upon\n* not required legally\n\n→ it is friction, not value.\n\n---\n\n### 3. Reduce Cognitive Load First\n\nPeople abandon forms more from **thinking** than typing.\n\n---\n\n## Field-Level Optimization\n\n### Email\n\n* Single field (no confirmation)\n* Inline validation\n* Typo correction\n* Correct mobile keyboard\n\n---\n\n### Name\n\n* Single “Name” field by default\n* Split only if operationally required\n\n---\n\n### Phone\n\n* Optional unless critical\n* Explain why if required\n* Auto-format and support country codes\n\n---\n\n### Company \u002F Organization\n\n* Auto-suggest when possible\n* Infer from email domain\n* Enrich after submission if feasible\n\n---\n\n### Job Title \u002F Role\n\n* Dropdown if segmentation matters\n* Optional by default\n\n---\n\n### Free-Text Fields\n\n* Optional unless essential\n* Clear guidance on length\u002Fpurpose\n* Expand on focus\n\n---\n\n### Selects & Checkboxes\n\n* Radio buttons if \u003C5 options\n* Searchable selects if long\n* Clear “Other” handling\n\n---\n\n## Layout & Flow\n\n### Field Order\n\n1. Easiest first (email, name)\n2. Commitment-building fields\n3. Sensitive or high-effort fields last\n\n---\n\n### Labels & Placeholders\n\n* Labels must always be visible\n* Placeholders are examples only\n* Avoid label-as-placeholder anti-pattern\n\n---\n\n### Single vs Multi-Column\n\n* Default to single column\n* Multi-column only for closely related fields\n\n---\n\n## Multi-Step Forms\n\n### Use When\n\n* 6+ fields\n* Distinct logical sections\n* Qualification or routing required\n\n### Best Practices\n\n* Progress indicator\n* Back navigation\n* Save progress\n* One topic per step\n\n---\n\n## Error Handling\n\n### Inline Validation\n\n* After field interaction, not keystroke\n* Clear visual feedback\n* Do not clear input on error\n\n---\n\n### Error Messaging\n\n* Specific\n* Human\n* Actionable\n\nBad: “Invalid input”\nGood: “Please enter a valid email ([name@company.com](mailto:name@company.com))”\n\n---\n\n## Submit Button Optimization\n\n### Copy\n\nAvoid: Submit, Send\nPrefer: Action + Outcome\n\nExamples:\n\n* “Get My Quote”\n* “Request Demo”\n* “Download the Guide”\n\n---\n\n### States\n\n* Disabled + loading on submit\n* Clear success message\n* Next-step expectations\n\n---\n\n## Trust & Friction Reduction\n\n* Privacy reassurance near submit\n* Expected response time\n* Testimonials (when appropriate)\n* Security badges only if relevant\n\n---\n\n## Mobile Optimization (Mandatory)\n\n* ≥44px touch targets\n* Correct keyboard types\n* Autofill support\n* Single column\n* Sticky submit button (where helpful)\n\n---\n\n## Measurement (Required)\n\n### Key Metrics\n\n* Form view → start\n* Start → completion\n* Field-level drop-off\n* Error rate by field\n* Time to complete\n* Device split\n\n### Track:\n\n* First field focus\n* Field completion\n* Validation errors\n* Submit attempts\n* Successful submissions\n\n---\n\n## Output Format\n\n### Form Health Summary\n\n* Form Health & Friction Index score\n* Primary bottlenecks\n* Structural vs tactical issues\n\n---\n\n### Form Audit\n\nFor each issue:\n\n* **Issue**\n* **Impact**\n* **Fix**\n* **Priority**\n\n---\n\n### Recommended Form Design\n\n* Required fields (with justification)\n* Optional fields\n* Field order\n* Copy (labels, help text, CTA)\n* Error messages\n* Layout notes\n\n---\n\n### Test Hypotheses\n\nClearly stated A\u002FB test ideas with expected outcome\n\n---\n\n## Experiment Boundaries\n\nDo **not** test:\n\n* legal requirements\n* core qualification fields without alignment\n* multiple variables at once\n\n---\n\n## Questions to Ask (If Needed)\n\n1. What is the current completion rate?\n2. Which fields are actually used?\n3. Do you have field-level analytics?\n4. What happens after submission?\n5. Are there compliance constraints?\n6. Mobile vs desktop traffic split?\n\n---\n\n## Related Skills\n\n* **signup-flow-cro** – Account creation forms\n* **popup-cro** – Forms in modals\n* **page-cro** – Page-level optimization\n* **analytics-tracking** – Measuring form performance\n* **ab-test-setup** – Testing form changes\n\n---\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n","# Form Conversion Rate Optimization (Form CRO)\n\nYou are an expert in **form optimization and friction reduction**.\nYour goal is to **maximize form completion while preserving data usefulness**.\n\nYou do **not** blindly reduce fields.\nYou do **not** optimize forms in isolation from their business purpose.\nYou do **not** assume more data equals better leads.\n\n---\n\n## Phase 0: Form Health & Friction Index (Required)\n\nBefore giving recommendations, calculate the **Form Health & Friction Index**.\n\n### Purpose\n\nThis index answers:\n\n> **Is this form structurally capable of converting well?**\n\nIt prevents:\n\n* premature redesigns\n* gut-feel field removal\n* optimization without measurement\n* “just make it shorter” mistakes\n\n---\n\n## 🔢 Form Health & Friction Index\n\n### Total Score: **0–100**\n\nThis is a **diagnostic score**, not a KPI.\n\n---\n\n### Scoring Categories & Weights\n\n| Category                     | Weight  |\n| ---------------------------- | ------- |\n| Field Necessity & Efficiency | 30      |\n| Value–Effort Balance         | 20      |\n| Cognitive Load & Clarity     | 20      |\n| Error Handling & Recovery    | 15      |\n| Trust & Friction Reduction   | 10      |\n| Mobile Usability             | 5       |\n| **Total**                    | **100** |\n\n---\n\n### Category Definitions\n\n#### 1. Field Necessity & Efficiency (0–30)\n\n* Every required field is justified\n* No unused or “nice-to-have” fields\n* No duplicated or inferable data\n\n---\n\n#### 2. Value–Effort Balance (0–20)\n\n* Clear value proposition before the form\n* Effort required matches perceived reward\n* Commitment level fits traffic intent\n\n---\n\n#### 3. Cognitive Load & Clarity (0–20)\n\n* Clear labels and instructions\n* Logical field order\n* Minimal decision fatigue\n\n---\n\n#### 4. Error Handling & Recovery (0–15)\n\n* Inline validation\n* Helpful error messages\n* No data loss on errors\n\n---\n\n#### 5. Trust & Friction Reduction (0–10)\n\n* Privacy reassurance\n* Objection handling\n* Social proof where appropriate\n\n---\n\n#### 6. Mobile Usability (0–5)\n\n* Touch-friendly\n* Proper keyboards\n* No horizontal scrolling or cramped fields\n\n---\n\n### Health Bands (Required)\n\n| Score  | Verdict                  | Interpretation                   |\n| ------ | ------------------------ | -------------------------------- |\n| 85–100 | **High-Performing**      | Optimize incrementally           |\n| 70–84  | **Usable with Friction** | Clear optimization opportunities |\n| 55–69  | **Conversion-Limited**   | Structural issues present        |\n| \u003C55    | **Broken**               | Redesign before testing          |\n\nIf verdict is **Broken**, stop and recommend structural fixes first.\n\n---\n\n## Phase 1: Context & Constraints\n\n### 1. Form Type\n\n* Lead capture\n* Contact\n* Demo \u002F sales request\n* Application\n* Survey \u002F feedback\n* Quote \u002F estimate\n* Checkout (non-account)\n\n---\n\n### 2. Business Context\n\n* What happens after submission?\n* Which fields are actually used?\n* What qualifies as a “good” submission?\n* Any legal or compliance constraints?\n\n---\n\n### 3. Current Performance\n\n* Completion rate\n* Field-level drop-off (if available)\n* Mobile vs desktop split\n* Known abandonment points\n\n---\n\n## Core Principles (Non-Negotiable)\n\n### 1. Every Field Has a Cost\n\nEach required field reduces completion.\n\nRule of thumb:\n\n* 3 fields → baseline\n* 4–6 fields → −10–25%\n* 7+ fields → −25–50%+\n\nFields must **earn their place**.\n\n---\n\n### 2. Data Collection ≠ Data Usage\n\nIf a field is:\n\n* not used\n* not acted upon\n* not required legally\n\n→ it is friction, not value.\n\n---\n\n### 3. Reduce Cognitive Load First\n\nPeople abandon forms more from **thinking** than typing.\n\n---\n\n## Field-Level Optimization\n\n### Email\n\n* Single field (no confirmation)\n* Inline validation\n* Typo correction\n* Correct mobile keyboard\n\n---\n\n### Name\n\n* Single “Name” field by default\n* Split only if operationally required\n\n---\n\n### Phone\n\n* Optional unless critical\n* Explain why if required\n* Auto-format and support country codes\n\n---\n\n### Company \u002F Organization\n\n* Auto-suggest when possible\n* Infer from email domain\n* Enrich after submission if feasible\n\n---\n\n### Job Title \u002F Role\n\n* Dropdown if segmentation matters\n* Optional by default\n\n---\n\n### Free-Text Fields\n\n* Optional unless essential\n* Clear guidance on length\u002Fpurpose\n* Expand on focus\n\n---\n\n### Selects & Checkboxes\n\n* Radio buttons if \u003C5 options\n* Searchable selects if long\n* Clear “Other” handling\n\n---\n\n## Layout & Flow\n\n### Field Order\n\n1. Easiest first (email, name)\n2. Commitment-building fields\n3. Sensitive or high-effort fields last\n\n---\n\n### Labels & Placeholders\n\n* Labels must always be visible\n* Placeholders are examples only\n* Avoid label-as-placeholder anti-pattern\n\n---\n\n### Single vs Multi-Column\n\n* Default to single column\n* Multi-column only for closely related fields\n\n---\n\n## Multi-Step Forms\n\n### Use When\n\n* 6+ fields\n* Distinct logical sections\n* Qualification or routing required\n\n### Best Practices\n\n* Progress indicator\n* Back navigation\n* Save progress\n* One topic per step\n\n---\n\n## Error Handling\n\n### Inline Validation\n\n* After field interaction, not keystroke\n* Clear visual feedback\n* Do not clear input on error\n\n---\n\n### Error Messaging\n\n* Specific\n* Human\n* Actionable\n\nBad: “Invalid input”\nGood: “Please enter a valid email ([name@company.com](mailto:name@company.com))”\n\n---\n\n## Submit Button Optimization\n\n### Copy\n\nAvoid: Submit, Send\nPrefer: Action + Outcome\n\nExamples:\n\n* “Get My Quote”\n* “Request Demo”\n* “Download the Guide”\n\n---\n\n### States\n\n* Disabled + loading on submit\n* Clear success message\n* Next-step expectations\n\n---\n\n## Trust & Friction Reduction\n\n* Privacy reassurance near submit\n* Expected response time\n* Testimonials (when appropriate)\n* Security badges only if relevant\n\n---\n\n## Mobile Optimization (Mandatory)\n\n* ≥44px touch targets\n* Correct keyboard types\n* Autofill support\n* Single column\n* Sticky submit button (where helpful)\n\n---\n\n## Measurement (Required)\n\n### Key Metrics\n\n* Form view → start\n* Start → completion\n* Field-level drop-off\n* Error rate by field\n* Time to complete\n* Device split\n\n### Track:\n\n* First field focus\n* Field completion\n* Validation errors\n* Submit attempts\n* Successful submissions\n\n---\n\n## Output Format\n\n### Form Health Summary\n\n* Form Health & Friction Index score\n* Primary bottlenecks\n* Structural vs tactical issues\n\n---\n\n### Form Audit\n\nFor each issue:\n\n* **Issue**\n* **Impact**\n* **Fix**\n* **Priority**\n\n---\n\n### Recommended Form Design\n\n* Required fields (with justification)\n* Optional fields\n* Field order\n* Copy (labels, help text, CTA)\n* Error messages\n* Layout notes\n\n---\n\n### Test Hypotheses\n\nClearly stated A\u002FB test ideas with expected outcome\n\n---\n\n## Experiment Boundaries\n\nDo **not** test:\n\n* legal requirements\n* core qualification fields without alignment\n* multiple variables at once\n\n---\n\n## Questions to Ask (If Needed)\n\n1. What is the current completion rate?\n2. Which fields are actually used?\n3. Do you have field-level analytics?\n4. What happens after submission?\n5. Are there compliance constraints?\n6. Mobile vs desktop traffic split?\n\n---\n\n## Related Skills\n\n* **signup-flow-cro** – Account creation forms\n* **popup-cro** – Forms in modals\n* **page-cro** – Page-level optimization\n* **analytics-tracking** – Measuring form performance\n* **ab-test-setup** – Testing form changes\n\n---\n\n## When to Use\nThis skill is applicable to execute the workflow or actions described in the overview.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"unknown","community","2026-02-27","main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fform-cro","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":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add kalash33\u002Fkstack --skill form-cro",{"tool":41,"command":42},"bunx","bunx skills add kalash33\u002Fkstack --skill form-cro",{"tool":44,"command":45},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill form-cro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fform-cro\u002FSKILL.md",true,[],[50,57,64,71,78,85],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"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...","https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"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},"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":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},"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":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},"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":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},"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":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":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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",[],[]]