[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M736JBGD5QNFARBHSF8B0XZ1":3,"skill-same:01M736JBGD5QNFARBHSF8B0XZ1":62},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M736JBGD5QNFARBHSF8B0XZ1","page-decomposition",null,"Analyze content sequences within a section and provide neutral descriptions for AEM Edge Delivery Services. Invoked per section during page import to identify breaking points between default content and blocks.","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-page-decomposition\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: page-decomposition\ndescription: Analyze content sequences within a section and provide neutral descriptions for AEM Edge Delivery Services. Invoked per section during page import to identify breaking points between default content and blocks.\nlicense: Apache-2.0\nmetadata:\n  version: \"1.0.0\"\n---\n\n# Page Decomposition\n\nAnalyze content sequences within a section and provide neutral descriptions without assigning block names.\n\n## When to Use This Skill\n\nThis skill is called by **identify-page-structure** for EACH section to:\n- Identify content sequences within that section\n- Provide neutral descriptions (NO block names yet)\n- Identify breaking points between sequences\n- Enable authoring-focused decisions later\n\n**IMPORTANT:** This skill analyzes ONE section at a time, not the whole page.\n\n## Input Required\n\nFrom the calling skill (identify-page-structure), you need:\n- Section visual description and boundaries\n- Screenshot showing the section\n- Cleaned HTML content for the section\n\n## Related Skills\n\n- **page-import** - Top-level orchestrator\n- **identify-page-structure** - Invokes this skill for each section (Step 2b)\n- **block-inventory** - Provides available blocks AFTER decomposition\n- **content-modeling** - Makes authoring decisions AFTER decomposition\n- **content-driven-development** - References section structure in html-structure.md\n\n## Key Concepts\n\n**Content Hierarchy:**\n```\nDOCUMENT\n├── SECTION (top-level, analyzed by identify-page-structure Step 2a)\n│   ├── Content Sequence 1 ← THIS SKILL IDENTIFIES THESE\n│   ├── Content Sequence 2 ← THIS SKILL IDENTIFIES THESE\n│   └── ...\n└── SECTION\n    └── Content Sequence 1\n```\n\n**What is a \"content sequence\"?**\nA vertical flow of related content that will eventually become:\n- Default content (headings, paragraphs, lists, inline images), OR\n- A block (structured, repeating, or interactive component)\n\n**Breaking points between sequences:**\n- Visual\u002Fsemantic shift in content type\n- Change from prose → structured pattern\n- Change from one pattern → different pattern\n\n**Philosophy:**\n- Describe WHAT you see, not WHAT it should be\n- \"Two images side-by-side\" not \"Columns block\"\n- \"Grid of 8 items with icons\" not \"Cards block\"\n- Stay neutral - authoring decisions come later\n\n## Decomposition Workflow\n\n**Context:** identify-page-structure has already identified section boundaries (Step 2a). This skill is invoked FOR ONE SECTION to analyze its internal content sequences.\n\n---\n\n### Step 1: Examine the Section\n\nLook at the screenshot and HTML for THIS section only.\n\n**What to observe:**\n- Vertical flow of content from top to bottom\n- Where content changes type or pattern\n- Visual groupings or breaks\n\n**Ignore:**\n- Other sections (out of scope)\n- Section styling (already identified by page-import)\n- Block names (stay neutral)\n\n**Output:** Mental model of content flow within this section\n\n---\n\n### Step 2: Identify Breaking Points\n\nFind where content shifts from one type\u002Fpattern to another.\n\n**Breaking point indicators:**\n- Prose text → Structured grid\n- Heading\u002Fparagraph → Side-by-side images\n- One repeating pattern → Different repeating pattern\n- Structured content → Prose text\n\n**Example within a section:**\n```\nContent flows top to bottom:\n- Large heading\n- Paragraph\n- Two buttons\n[BREAK] ← Visual\u002Fsemantic shift\n- Two images displayed side-by-side\n```\n\n**Output:** List of breaking points\n\n---\n\n### Step 3: Define Content Sequences\n\nBetween each breaking point is a content sequence.\n\n**For each sequence, describe:**\n- What elements it contains (heading, paragraph, images, etc.)\n- How they're arranged (stacked, side-by-side, in a grid)\n- Quantity (one heading, two images, grid of 8 items)\n\n**Use neutral language:**\n- ✅ \"Two images displayed side-by-side\"\n- ❌ \"Columns block with two images\"\n- ✅ \"Grid of 8 items, each with icon and short text\"\n- ❌ \"Cards block\"\n- ✅ \"Large centered heading, paragraph, two buttons stacked vertically\"\n- ❌ \"Hero block\"\n\n**Output:** Neutral descriptions for each sequence\n\n---\n\n### Step 4: Return Structured Output\n\nProvide content sequences for this section in structured format.\n\n**Output format:**\n```javascript\n{\n  sectionNumber: 1,  \u002F\u002F From identify-page-structure\n  sequences: [\n    {\n      sequenceNumber: 1,\n      description: \"Large centered heading, paragraph, two buttons stacked vertically\"\n    },\n    {\n      sequenceNumber: 2,\n      description: \"Two images displayed side-by-side\"\n    }\n  ]\n}\n```\n\n**This enables:**\n- Clear understanding of section's internal structure\n- Neutral foundation for authoring decisions\n- Separation of description from implementation\n\n---\n\n## Section Metadata Format\n\n**Table format:**\n```markdown\n+------------------------------+\n| Section Metadata             |\n+------------------+-----------+\n| style            | light     |\n+------------------+-----------+\n```\n\n**Placement:** At the start of each section, before content\n\n**Usage:** Applied by generate-import-html skill when generating final HTML\n\n---\n\n## Examples\n\n### Example 1: Hero Section\n\n**Input:** \"Section 1 (light background): Large prominent content at top of page\"\n\n**Visual observation:**\n- Large centered heading\n- Paragraph text below it\n- Two call-to-action buttons\n[BREAK - visual shift]\n- Two large images displayed next to each other\n\n**Output:**\n```javascript\n{\n  sectionNumber: 1,\n  sequences: [\n    {\n      sequenceNumber: 1,\n      description: \"Large centered heading, paragraph, two call-to-action buttons stacked vertically\"\n    },\n    {\n      sequenceNumber: 2,\n      description: \"Two large images displayed side-by-side\"\n    }\n  ]\n}\n```\n\n---\n\n### Example 2: Features Section\n\n**Input:** \"Section 2 (light background): Grid of feature items\"\n\n**Visual observation:**\n- Centered heading\n[BREAK - shift to structured pattern]\n- Grid of 8 items\n- Each item has: small icon, short text description\n[BREAK - shift back to simple elements]\n- Two centered buttons\n\n**Output:**\n```javascript\n{\n  sectionNumber: 2,\n  sequences: [\n    {\n      sequenceNumber: 1,\n      description: \"Single centered heading\"\n    },\n    {\n      sequenceNumber: 2,\n      description: \"Grid of 8 items, each with small icon and short text description\"\n    },\n    {\n      sequenceNumber: 3,\n      description: \"Two centered buttons\"\n    }\n  ]\n}\n```\n\n---\n\n### Example 3: Article Cards Section\n\n**Input:** \"Section 3 (grey background): Blog articles\"\n\n**Visual observation:**\n- Eyebrow text \"Latest Articles\"\n- Large heading\n- Paragraph description\n- Browse button\n[BREAK - shift to repeating pattern]\n- 4 items in grid\n- Each item: image, category tag, heading, short description, read link\n\n**Output:**\n```javascript\n{\n  sectionNumber: 3,\n  sequences: [\n    {\n      sequenceNumber: 1,\n      description: \"Eyebrow text, large heading, paragraph description, browse button - all stacked vertically\"\n    },\n    {\n      sequenceNumber: 2,\n      description: \"Grid of 4 items, each with image, category tag, heading, description, and read link\"\n    }\n  ]\n}\n```\n\n---\n\n### Example 4: Simple Content Section\n\n**Input:** \"Section 4 (light background): Body content\"\n\n**Visual observation:**\n- Multiple paragraphs of text\n- Some inline images within the text\n- Headings interspersed (H2, H3)\n- No clear breaking points - content flows naturally\n\n**Output:**\n```javascript\n{\n  sectionNumber: 4,\n  sequences: [\n    {\n      sequenceNumber: 1,\n      description: \"Flowing prose content: multiple paragraphs with inline images and headings (H2, H3)\"\n    }\n  ]\n}\n```\n\n**Note:** This entire section is one sequence because content flows naturally without structural breaks.\n\n---\n\n## Common Mistakes to Avoid\n\n**Using block names in descriptions:**\n❌ \"Hero block with heading and buttons\"\n✓ \"Large centered heading, paragraph, two buttons stacked vertically\"\n\n**Not identifying breaking points:**\n❌ Describing entire section as one sequence when there are clear shifts\n✓ Identifying where content type changes and breaking into sequences\n\n**Being too granular:**\n❌ Each element as separate sequence: \"Heading\", \"Paragraph\", \"Button\"\n✓ Related elements together: \"Heading, paragraph, two buttons stacked vertically\"\n\n**Mixing analysis levels:**\n❌ Analyzing multiple sections at once\n✓ Focus on ONE section at a time (per invocation)\n\n**Making authoring decisions:**\n❌ \"This should be a cards block because...\"\n✓ \"Grid of 4 items with images and text\" (neutral description)\n","# Page Decomposition\n\nAnalyze content sequences within a section and provide neutral descriptions without assigning block names.\n\n## When to Use This Skill\n\nThis skill is called by **identify-page-structure** for EACH section to:\n- Identify content sequences within that section\n- Provide neutral descriptions (NO block names yet)\n- Identify breaking points between sequences\n- Enable authoring-focused decisions later\n\n**IMPORTANT:** This skill analyzes ONE section at a time, not the whole page.\n\n## Input Required\n\nFrom the calling skill (identify-page-structure), you need:\n- Section visual description and boundaries\n- Screenshot showing the section\n- Cleaned HTML content for the section\n\n## Related Skills\n\n- **page-import** - Top-level orchestrator\n- **identify-page-structure** - Invokes this skill for each section (Step 2b)\n- **block-inventory** - Provides available blocks AFTER decomposition\n- **content-modeling** - Makes authoring decisions AFTER decomposition\n- **content-driven-development** - References section structure in html-structure.md\n\n## Key Concepts\n\n**Content Hierarchy:**\n```\nDOCUMENT\n├── SECTION (top-level, analyzed by identify-page-structure Step 2a)\n│   ├── Content Sequence 1 ← THIS SKILL IDENTIFIES THESE\n│   ├── Content Sequence 2 ← THIS SKILL IDENTIFIES THESE\n│   └── ...\n└── SECTION\n    └── Content Sequence 1\n```\n\n**What is a \"content sequence\"?**\nA vertical flow of related content that will eventually become:\n- Default content (headings, paragraphs, lists, inline images), OR\n- A block (structured, repeating, or interactive component)\n\n**Breaking points between sequences:**\n- Visual\u002Fsemantic shift in content type\n- Change from prose → structured pattern\n- Change from one pattern → different pattern\n\n**Philosophy:**\n- Describe WHAT you see, not WHAT it should be\n- \"Two images side-by-side\" not \"Columns block\"\n- \"Grid of 8 items with icons\" not \"Cards block\"\n- Stay neutral - authoring decisions come later\n\n## Decomposition Workflow\n\n**Context:** identify-page-structure has already identified section boundaries (Step 2a). This skill is invoked FOR ONE SECTION to analyze its internal content sequences.\n\n---\n\n### Step 1: Examine the Section\n\nLook at the screenshot and HTML for THIS section only.\n\n**What to observe:**\n- Vertical flow of content from top to bottom\n- Where content changes type or pattern\n- Visual groupings or breaks\n\n**Ignore:**\n- Other sections (out of scope)\n- Section styling (already identified by page-import)\n- Block names (stay neutral)\n\n**Output:** Mental model of content flow within this section\n\n---\n\n### Step 2: Identify Breaking Points\n\nFind where content shifts from one type\u002Fpattern to another.\n\n**Breaking point indicators:**\n- Prose text → Structured grid\n- Heading\u002Fparagraph → Side-by-side images\n- One repeating pattern → Different repeating pattern\n- Structured content → Prose text\n\n**Example within a section:**\n```\nContent flows top to bottom:\n- Large heading\n- Paragraph\n- Two buttons\n[BREAK] ← Visual\u002Fsemantic shift\n- Two images displayed side-by-side\n```\n\n**Output:** List of breaking points\n\n---\n\n### Step 3: Define Content Sequences\n\nBetween each breaking point is a content sequence.\n\n**For each sequence, describe:**\n- What elements it contains (heading, paragraph, images, etc.)\n- How they're arranged (stacked, side-by-side, in a grid)\n- Quantity (one heading, two images, grid of 8 items)\n\n**Use neutral language:**\n- ✅ \"Two images displayed side-by-side\"\n- ❌ \"Columns block with two images\"\n- ✅ \"Grid of 8 items, each with icon and short text\"\n- ❌ \"Cards block\"\n- ✅ \"Large centered heading, paragraph, two buttons stacked vertically\"\n- ❌ \"Hero block\"\n\n**Output:** Neutral descriptions for each sequence\n\n---\n\n### Step 4: Return Structured Output\n\nProvide content sequences for this section in structured format.\n\n**Output format:**\n```javascript\n{\n  sectionNumber: 1,  \u002F\u002F From identify-page-structure\n  sequences: [\n    {\n      sequenceNumber: 1,\n      description: \"Large centered heading, paragraph, two buttons stacked vertically\"\n    },\n    {\n      sequenceNumber: 2,\n      description: \"Two images displayed side-by-side\"\n    }\n  ]\n}\n```\n\n**This enables:**\n- Clear understanding of section's internal structure\n- Neutral foundation for authoring decisions\n- Separation of description from implementation\n\n---\n\n## Section Metadata Format\n\n**Table format:**\n```markdown\n+------------------------------+\n| Section Metadata             |\n+------------------+-----------+\n| style            | light     |\n+------------------+-----------+\n```\n\n**Placement:** At the start of each section, before content\n\n**Usage:** Applied by generate-import-html skill when generating final HTML\n\n---\n\n## Examples\n\n### Example 1: Hero Section\n\n**Input:** \"Section 1 (light background): Large prominent content at top of page\"\n\n**Visual observation:**\n- Large centered heading\n- Paragraph text below it\n- Two call-to-action buttons\n[BREAK - visual shift]\n- Two large images displayed next to each other\n\n**Output:**\n```javascript\n{\n  sectionNumber: 1,\n  sequences: [\n    {\n      sequenceNumber: 1,\n      description: \"Large centered heading, paragraph, two call-to-action buttons stacked vertically\"\n    },\n    {\n      sequenceNumber: 2,\n      description: \"Two large images displayed side-by-side\"\n    }\n  ]\n}\n```\n\n---\n\n### Example 2: Features Section\n\n**Input:** \"Section 2 (light background): Grid of feature items\"\n\n**Visual observation:**\n- Centered heading\n[BREAK - shift to structured pattern]\n- Grid of 8 items\n- Each item has: small icon, short text description\n[BREAK - shift back to simple elements]\n- Two centered buttons\n\n**Output:**\n```javascript\n{\n  sectionNumber: 2,\n  sequences: [\n    {\n      sequenceNumber: 1,\n      description: \"Single centered heading\"\n    },\n    {\n      sequenceNumber: 2,\n      description: \"Grid of 8 items, each with small icon and short text description\"\n    },\n    {\n      sequenceNumber: 3,\n      description: \"Two centered buttons\"\n    }\n  ]\n}\n```\n\n---\n\n### Example 3: Article Cards Section\n\n**Input:** \"Section 3 (grey background): Blog articles\"\n\n**Visual observation:**\n- Eyebrow text \"Latest Articles\"\n- Large heading\n- Paragraph description\n- Browse button\n[BREAK - shift to repeating pattern]\n- 4 items in grid\n- Each item: image, category tag, heading, short description, read link\n\n**Output:**\n```javascript\n{\n  sectionNumber: 3,\n  sequences: [\n    {\n      sequenceNumber: 1,\n      description: \"Eyebrow text, large heading, paragraph description, browse button - all stacked vertically\"\n    },\n    {\n      sequenceNumber: 2,\n      description: \"Grid of 4 items, each with image, category tag, heading, description, and read link\"\n    }\n  ]\n}\n```\n\n---\n\n### Example 4: Simple Content Section\n\n**Input:** \"Section 4 (light background): Body content\"\n\n**Visual observation:**\n- Multiple paragraphs of text\n- Some inline images within the text\n- Headings interspersed (H2, H3)\n- No clear breaking points - content flows naturally\n\n**Output:**\n```javascript\n{\n  sectionNumber: 4,\n  sequences: [\n    {\n      sequenceNumber: 1,\n      description: \"Flowing prose content: multiple paragraphs with inline images and headings (H2, H3)\"\n    }\n  ]\n}\n```\n\n**Note:** This entire section is one sequence because content flows naturally without structural breaks.\n\n---\n\n## Common Mistakes to Avoid\n\n**Using block names in descriptions:**\n❌ \"Hero block with heading and buttons\"\n✓ \"Large centered heading, paragraph, two buttons stacked vertically\"\n\n**Not identifying breaking points:**\n❌ Describing entire section as one sequence when there are clear shifts\n✓ Identifying where content type changes and breaking into sequences\n\n**Being too granular:**\n❌ Each element as separate sequence: \"Heading\", \"Paragraph\", \"Button\"\n✓ Related elements together: \"Heading, paragraph, two buttons stacked vertically\"\n\n**Mixing analysis levels:**\n❌ Analyzing multiple sections at once\n✓ Focus on ONE section at a time (per invocation)\n\n**Making authoring decisions:**\n❌ \"This should be a cards block because...\"\n✓ \"Grid of 4 items with images and text\" (neutral description)\n",{"name":5,"license":15,"metadata":24,"description":7},{"version":25},"1.0.0","main","b30820b3248f6676d5389f0ccabd4e5250c9c536","skills\u002Fadobe-page-decomposition","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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add kalash33\u002Fkstack --skill page-decomposition",{"tool":40,"command":41},"bunx","bunx skills add kalash33\u002Fkstack --skill page-decomposition",{"tool":43,"command":44},"pnpm","pnpm dlx skills add kalash33\u002Fkstack --skill page-decomposition","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-page-decomposition\u002FSKILL.md",true,[48,54,58],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},".releaserc.json","REFERENCE","参考文档",49,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-page-decomposition\u002F.releaserc.json",{"path":55,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":56,"sourceHtmlUrl":57},"CHANGELOG.md",5882,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-page-decomposition\u002FCHANGELOG.md",{"path":59,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":60,"sourceHtmlUrl":61},"package.json",98,"https:\u002F\u002Fgithub.com\u002Fkalash33\u002Fkstack\u002Fblob\u002Fmain\u002Fskills\u002Fadobe-page-decomposition\u002Fpackage.json",[63,71,78,85,92,99],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":67,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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",[],[]]