[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79F6XDB0Q5X93VYC4R5885E":3,"skill-same:01M79F6XDB0Q5X93VYC4R5885E":45},{"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":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M79F6XDB0Q5X93VYC4R5885E","segment-automation",null,"\"Automate Segment tasks via Rube MCP (Composio): track events, identify users, manage groups, page views, aliases, batch operations. Always search tools first for current schemas.\"\nrequires:\n  mcp: [rube]","sharepointoscar\u002Fagent-workflow-skills","sharepointoscar","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1544014?v=4","01M79DYNNSWKW6C81A3C9QF0FQ","Oscar Medina","01M79DYNPDXTKQ5RFX4071RBM8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-integrations\u002Fskills\u002Fsegment-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: segment-automation\ndescription: |-\n  \"Automate Segment tasks via Rube MCP (Composio): track events, identify users, manage groups, page views, aliases, batch operations. Always search tools first for current schemas.\"\n  requires:\n    mcp: [rube]\n---\n\n# Segment Automation via Rube MCP\n\nAutomate Segment customer data platform operations through Composio's Segment toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Segment connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `segment`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `segment`\n3. If connection is not ACTIVE, follow the returned auth link to complete Segment authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Track Events\n\n**When to use**: User wants to send event data to Segment for downstream destinations\n\n**Tool sequence**:\n1. `SEGMENT_TRACK` - Send a single track event [Required]\n\n**Key parameters**:\n- `userId`: User identifier (required if no `anonymousId`)\n- `anonymousId`: Anonymous identifier (required if no `userId`)\n- `event`: Event name (e.g., 'Order Completed', 'Button Clicked')\n- `properties`: Object with event-specific properties\n- `timestamp`: ISO 8601 timestamp (optional; defaults to server time)\n- `context`: Object with contextual metadata (IP, user agent, etc.)\n\n**Pitfalls**:\n- At least one of `userId` or `anonymousId` is required\n- `event` name is required and should follow consistent naming conventions\n- Properties are freeform objects; ensure consistent schema across events\n- Timestamp must be ISO 8601 format (e.g., '2024-01-15T10:30:00Z')\n- Events are processed asynchronously; successful API response means accepted, not delivered\n\n### 2. Identify Users\n\n**When to use**: User wants to associate traits with a user profile in Segment\n\n**Tool sequence**:\n1. `SEGMENT_IDENTIFY` - Set user traits and identity [Required]\n\n**Key parameters**:\n- `userId`: User identifier (required if no `anonymousId`)\n- `anonymousId`: Anonymous identifier\n- `traits`: Object with user properties (email, name, plan, etc.)\n- `timestamp`: ISO 8601 timestamp\n- `context`: Contextual metadata\n\n**Pitfalls**:\n- At least one of `userId` or `anonymousId` is required\n- Traits are merged with existing traits, not replaced\n- To remove a trait, set it to `null`\n- Identify calls should be made before track calls for new users\n- Avoid sending PII in traits unless destinations are configured for it\n\n### 3. Batch Operations\n\n**When to use**: User wants to send multiple events, identifies, or other calls in a single request\n\n**Tool sequence**:\n1. `SEGMENT_BATCH` - Send multiple Segment calls in one request [Required]\n\n**Key parameters**:\n- `batch`: Array of message objects, each with:\n  - `type`: Message type ('track', 'identify', 'group', 'page', 'alias')\n  - `userId` \u002F `anonymousId`: User identifier\n  - Additional fields based on type (event, properties, traits, etc.)\n\n**Pitfalls**:\n- Each message in the batch must have a valid `type` field\n- Maximum batch size limit applies; check schema for current limit\n- All messages in a batch are processed independently; one failure does not affect others\n- Each message must independently satisfy its type's requirements (e.g., track needs event name)\n- Batch is the most efficient way to send multiple calls; prefer over individual calls\n\n### 4. Group Users\n\n**When to use**: User wants to associate a user with a company, team, or organization\n\n**Tool sequence**:\n1. `SEGMENT_GROUP` - Associate user with a group [Required]\n\n**Key parameters**:\n- `userId`: User identifier (required if no `anonymousId`)\n- `anonymousId`: Anonymous identifier\n- `groupId`: Group\u002Forganization identifier (required)\n- `traits`: Object with group properties (name, industry, size, plan)\n- `timestamp`: ISO 8601 timestamp\n\n**Pitfalls**:\n- `groupId` is required; it identifies the company or organization\n- Group traits are merged with existing traits for that group\n- A user can belong to multiple groups\n- Group traits update the group profile, not the user profile\n\n### 5. Track Page Views\n\n**When to use**: User wants to record page view events in Segment\n\n**Tool sequence**:\n1. `SEGMENT_PAGE` - Send a page view event [Required]\n\n**Key parameters**:\n- `userId`: User identifier (required if no `anonymousId`)\n- `anonymousId`: Anonymous identifier\n- `name`: Page name (e.g., 'Home', 'Pricing', 'Dashboard')\n- `category`: Page category (e.g., 'Docs', 'Marketing')\n- `properties`: Object with page-specific properties (url, title, referrer)\n\n**Pitfalls**:\n- At least one of `userId` or `anonymousId` is required\n- `name` and `category` are optional but recommended for proper analytics\n- Standard properties include `url`, `title`, `referrer`, `path`, `search`\n- Page calls are often automated; manual use is for server-side page tracking\n\n### 6. Alias Users and Manage Sources\n\n**When to use**: User wants to merge anonymous and identified users, or manage source configuration\n\n**Tool sequence**:\n1. `SEGMENT_ALIAS` - Link two user identities together [Optional]\n2. `SEGMENT_LIST_SCHEMA_SETTINGS_IN_SOURCE` - View source schema settings [Optional]\n3. `SEGMENT_UPDATE_SOURCE` - Update source configuration [Optional]\n\n**Key parameters**:\n- For ALIAS:\n  - `userId`: New user identifier (the identified ID)\n  - `previousId`: Old user identifier (the anonymous ID)\n- For source operations:\n  - `sourceId`: Source identifier\n\n**Pitfalls**:\n- ALIAS is a one-way operation; cannot be undone\n- `previousId` is the anonymous\u002Fold ID, `userId` is the new\u002Fidentified ID\n- Not all destinations support alias calls; check destination documentation\n- ALIAS should be called once when a user first identifies (e.g., signs up)\n- Source updates may affect data collection; review changes carefully\n\n## Common Patterns\n\n### User Lifecycle\n\nStandard Segment user lifecycle:\n```\n1. Anonymous user visits -> PAGE call with anonymousId\n2. User interacts -> TRACK call with anonymousId\n3. User signs up -> ALIAS (anonymousId -> userId), then IDENTIFY with traits\n4. User takes action -> TRACK call with userId\n5. User joins org -> GROUP call linking userId to groupId\n```\n\n### Batch Optimization\n\nFor bulk data ingestion:\n```\n1. Collect events in memory (array of message objects)\n2. Each message includes type, userId\u002FanonymousId, and type-specific fields\n3. Call SEGMENT_BATCH with the collected messages\n4. Check response for any individual message errors\n```\n\n### Naming Conventions\n\nSegment recommends consistent event naming:\n- **Events**: Use \"Object Action\" format (e.g., 'Order Completed', 'Article Viewed')\n- **Properties**: Use snake_case (e.g., 'order_total', 'product_name')\n- **Traits**: Use snake_case (e.g., 'first_name', 'plan_type')\n\n## Known Pitfalls\n\n**Identity Resolution**:\n- Always include `userId` or `anonymousId` on every call\n- Use ALIAS only once per user identity merge\n- Identify before tracking to ensure proper user association\n\n**Data Quality**:\n- Event names should be consistent across all sources\n- Properties should follow a defined schema for downstream compatibility\n- Avoid sending sensitive PII unless destinations are configured for it\n\n**Rate Limits**:\n- Use BATCH for bulk operations to stay within rate limits\n- Individual calls are rate-limited per source\n- Batch calls are more efficient and less likely to be throttled\n\n**Response Parsing**:\n- Successful responses indicate acceptance, not delivery to destinations\n- Response data may be nested under `data` key\n- Check for error fields in batch responses for individual message failures\n\n**Timestamps**:\n- Must be ISO 8601 format with timezone (e.g., '2024-01-15T10:30:00Z')\n- Omitting timestamp uses server receive time\n- Historical data imports should include explicit timestamps\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Track event | SEGMENT_TRACK | userId, event, properties |\n| Identify user | SEGMENT_IDENTIFY | userId, traits |\n| Batch calls | SEGMENT_BATCH | batch (array of messages) |\n| Group user | SEGMENT_GROUP | userId, groupId, traits |\n| Page view | SEGMENT_PAGE | userId, name, properties |\n| Alias identity | SEGMENT_ALIAS | userId, previousId |\n| Source schema | SEGMENT_LIST_SCHEMA_SETTINGS_IN_SOURCE | sourceId |\n| Update source | SEGMENT_UPDATE_SOURCE | sourceId |\n| Warehouses | SEGMENT_LIST_CONNECTED_WAREHOUSES_FROM_SOURCE | sourceId |\n","# Segment Automation via Rube MCP\n\nAutomate Segment customer data platform operations through Composio's Segment toolkit via Rube MCP.\n\n## Prerequisites\n\n- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)\n- Active Segment connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `segment`\n- Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas\n\n## Setup\n\n**Get Rube MCP**: Add `https:\u002F\u002Frube.app\u002Fmcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.\n\n\n1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds\n2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `segment`\n3. If connection is not ACTIVE, follow the returned auth link to complete Segment authentication\n4. Confirm connection status shows ACTIVE before running any workflows\n\n## Core Workflows\n\n### 1. Track Events\n\n**When to use**: User wants to send event data to Segment for downstream destinations\n\n**Tool sequence**:\n1. `SEGMENT_TRACK` - Send a single track event [Required]\n\n**Key parameters**:\n- `userId`: User identifier (required if no `anonymousId`)\n- `anonymousId`: Anonymous identifier (required if no `userId`)\n- `event`: Event name (e.g., 'Order Completed', 'Button Clicked')\n- `properties`: Object with event-specific properties\n- `timestamp`: ISO 8601 timestamp (optional; defaults to server time)\n- `context`: Object with contextual metadata (IP, user agent, etc.)\n\n**Pitfalls**:\n- At least one of `userId` or `anonymousId` is required\n- `event` name is required and should follow consistent naming conventions\n- Properties are freeform objects; ensure consistent schema across events\n- Timestamp must be ISO 8601 format (e.g., '2024-01-15T10:30:00Z')\n- Events are processed asynchronously; successful API response means accepted, not delivered\n\n### 2. Identify Users\n\n**When to use**: User wants to associate traits with a user profile in Segment\n\n**Tool sequence**:\n1. `SEGMENT_IDENTIFY` - Set user traits and identity [Required]\n\n**Key parameters**:\n- `userId`: User identifier (required if no `anonymousId`)\n- `anonymousId`: Anonymous identifier\n- `traits`: Object with user properties (email, name, plan, etc.)\n- `timestamp`: ISO 8601 timestamp\n- `context`: Contextual metadata\n\n**Pitfalls**:\n- At least one of `userId` or `anonymousId` is required\n- Traits are merged with existing traits, not replaced\n- To remove a trait, set it to `null`\n- Identify calls should be made before track calls for new users\n- Avoid sending PII in traits unless destinations are configured for it\n\n### 3. Batch Operations\n\n**When to use**: User wants to send multiple events, identifies, or other calls in a single request\n\n**Tool sequence**:\n1. `SEGMENT_BATCH` - Send multiple Segment calls in one request [Required]\n\n**Key parameters**:\n- `batch`: Array of message objects, each with:\n  - `type`: Message type ('track', 'identify', 'group', 'page', 'alias')\n  - `userId` \u002F `anonymousId`: User identifier\n  - Additional fields based on type (event, properties, traits, etc.)\n\n**Pitfalls**:\n- Each message in the batch must have a valid `type` field\n- Maximum batch size limit applies; check schema for current limit\n- All messages in a batch are processed independently; one failure does not affect others\n- Each message must independently satisfy its type's requirements (e.g., track needs event name)\n- Batch is the most efficient way to send multiple calls; prefer over individual calls\n\n### 4. Group Users\n\n**When to use**: User wants to associate a user with a company, team, or organization\n\n**Tool sequence**:\n1. `SEGMENT_GROUP` - Associate user with a group [Required]\n\n**Key parameters**:\n- `userId`: User identifier (required if no `anonymousId`)\n- `anonymousId`: Anonymous identifier\n- `groupId`: Group\u002Forganization identifier (required)\n- `traits`: Object with group properties (name, industry, size, plan)\n- `timestamp`: ISO 8601 timestamp\n\n**Pitfalls**:\n- `groupId` is required; it identifies the company or organization\n- Group traits are merged with existing traits for that group\n- A user can belong to multiple groups\n- Group traits update the group profile, not the user profile\n\n### 5. Track Page Views\n\n**When to use**: User wants to record page view events in Segment\n\n**Tool sequence**:\n1. `SEGMENT_PAGE` - Send a page view event [Required]\n\n**Key parameters**:\n- `userId`: User identifier (required if no `anonymousId`)\n- `anonymousId`: Anonymous identifier\n- `name`: Page name (e.g., 'Home', 'Pricing', 'Dashboard')\n- `category`: Page category (e.g., 'Docs', 'Marketing')\n- `properties`: Object with page-specific properties (url, title, referrer)\n\n**Pitfalls**:\n- At least one of `userId` or `anonymousId` is required\n- `name` and `category` are optional but recommended for proper analytics\n- Standard properties include `url`, `title`, `referrer`, `path`, `search`\n- Page calls are often automated; manual use is for server-side page tracking\n\n### 6. Alias Users and Manage Sources\n\n**When to use**: User wants to merge anonymous and identified users, or manage source configuration\n\n**Tool sequence**:\n1. `SEGMENT_ALIAS` - Link two user identities together [Optional]\n2. `SEGMENT_LIST_SCHEMA_SETTINGS_IN_SOURCE` - View source schema settings [Optional]\n3. `SEGMENT_UPDATE_SOURCE` - Update source configuration [Optional]\n\n**Key parameters**:\n- For ALIAS:\n  - `userId`: New user identifier (the identified ID)\n  - `previousId`: Old user identifier (the anonymous ID)\n- For source operations:\n  - `sourceId`: Source identifier\n\n**Pitfalls**:\n- ALIAS is a one-way operation; cannot be undone\n- `previousId` is the anonymous\u002Fold ID, `userId` is the new\u002Fidentified ID\n- Not all destinations support alias calls; check destination documentation\n- ALIAS should be called once when a user first identifies (e.g., signs up)\n- Source updates may affect data collection; review changes carefully\n\n## Common Patterns\n\n### User Lifecycle\n\nStandard Segment user lifecycle:\n```\n1. Anonymous user visits -> PAGE call with anonymousId\n2. User interacts -> TRACK call with anonymousId\n3. User signs up -> ALIAS (anonymousId -> userId), then IDENTIFY with traits\n4. User takes action -> TRACK call with userId\n5. User joins org -> GROUP call linking userId to groupId\n```\n\n### Batch Optimization\n\nFor bulk data ingestion:\n```\n1. Collect events in memory (array of message objects)\n2. Each message includes type, userId\u002FanonymousId, and type-specific fields\n3. Call SEGMENT_BATCH with the collected messages\n4. Check response for any individual message errors\n```\n\n### Naming Conventions\n\nSegment recommends consistent event naming:\n- **Events**: Use \"Object Action\" format (e.g., 'Order Completed', 'Article Viewed')\n- **Properties**: Use snake_case (e.g., 'order_total', 'product_name')\n- **Traits**: Use snake_case (e.g., 'first_name', 'plan_type')\n\n## Known Pitfalls\n\n**Identity Resolution**:\n- Always include `userId` or `anonymousId` on every call\n- Use ALIAS only once per user identity merge\n- Identify before tracking to ensure proper user association\n\n**Data Quality**:\n- Event names should be consistent across all sources\n- Properties should follow a defined schema for downstream compatibility\n- Avoid sending sensitive PII unless destinations are configured for it\n\n**Rate Limits**:\n- Use BATCH for bulk operations to stay within rate limits\n- Individual calls are rate-limited per source\n- Batch calls are more efficient and less likely to be throttled\n\n**Response Parsing**:\n- Successful responses indicate acceptance, not delivery to destinations\n- Response data may be nested under `data` key\n- Check for error fields in batch responses for individual message failures\n\n**Timestamps**:\n- Must be ISO 8601 format with timezone (e.g., '2024-01-15T10:30:00Z')\n- Omitting timestamp uses server receive time\n- Historical data imports should include explicit timestamps\n\n## Quick Reference\n\n| Task | Tool Slug | Key Params |\n|------|-----------|------------|\n| Track event | SEGMENT_TRACK | userId, event, properties |\n| Identify user | SEGMENT_IDENTIFY | userId, traits |\n| Batch calls | SEGMENT_BATCH | batch (array of messages) |\n| Group user | SEGMENT_GROUP | userId, groupId, traits |\n| Page view | SEGMENT_PAGE | userId, name, properties |\n| Alias identity | SEGMENT_ALIAS | userId, previousId |\n| Source schema | SEGMENT_LIST_SCHEMA_SETTINGS_IN_SOURCE | sourceId |\n| Update source | SEGMENT_UPDATE_SOURCE | sourceId |\n| Warehouses | SEGMENT_LIST_CONNECTED_WAREHOUSES_FROM_SOURCE | sourceId |\n",{"name":5,"description":7},"main","f27dd0e6c87efa56cfdea304aa3e89e63c02711b","plugins\u002Fskills-integrations\u002Fskills\u002Fsegment-automation","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills","https:\u002F\u002Fgithub.com\u002Fsharepointoscar","Author | DevOps Practitioner | Docker | Terraform | Kubernetes | Jenkins X  | AWS | GCP | Azure and SP Veteran (since code-name Tahoe)","2026-11-11 12:44:52",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add sharepointoscar\u002Fagent-workflow-skills --skill segment-automation",{"tool":37,"command":38},"bunx","bunx skills add sharepointoscar\u002Fagent-workflow-skills --skill segment-automation",{"tool":40,"command":41},"pnpm","pnpm dlx skills add sharepointoscar\u002Fagent-workflow-skills --skill segment-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-integrations\u002Fskills\u002Fsegment-automation\u002FSKILL.md",true,[],[46,53,60,67,74,81],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":19},"01M79FQNYDNR7TYQAM5061GVKR","web-performance-optimization","Optimize website and web application performance including loading speed, Core Web Vitals, bundle size, caching strategies, and runtime performance","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fweb-performance-optimization\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M79FQK396EEGX40QA7B9S404","web-design-guidelines","Review UI code for Web Interface Guidelines compliance. Use when asked to \"review my UI\", \"check accessibility\", \"audit design\", \"review UX\", or \"check my site against best practices\".","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fweb-design-guidelines\u002FSKILL.md",[],[],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M79FQFK4GJCG8HVRG8JQF4QH","wcag-audit-patterns","Conduct WCAG 2.2 accessibility audits with automated testing, manual verification, and remediation guidance. Use when auditing websites for accessibility, fixing WCAG violations, or implementing accessible design patterns.","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fwcag-audit-patterns\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M79FQ7WRQXC4D20Q2HTBMDG7","ui-ux-pro-max","UI\u002FUX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 9 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind, shadcn\u002Fui). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI\u002FUX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient. Integrations: shadcn\u002Fui MCP for component search and examples.","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fui-ux-pro-max\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M79FPZC11BPBWDCVK2TER0RC","stitch-ui-design","Expert guide for creating effective prompts for Google Stitch AI UI design tool. Use when user wants to design UI\u002FUX in Stitch, create app interfaces, generate mobile\u002Fweb designs, or needs help crafting Stitch prompts. Covers prompt structure, specificity techniques, iteration strategies, and design-to-code workflows for Stitch by Google.","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fstitch-ui-design\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":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M79FPTMMM3C57JN25RTRX2HR","scroll-experience","Expert in building immersive scroll-driven experiences - parallax storytelling, scroll animations, interactive narratives, and cinematic web experiences. Like NY Times interactives, Apple product pages, and award-winning web experiences. Makes websites feel like experiences, not just pages. Use when: scroll animation, parallax, scroll storytelling, interactive story, cinematic website.","https:\u002F\u002Fgithub.com\u002Fsharepointoscar\u002Fagent-workflow-skills\u002Fblob\u002Fmain\u002Fplugins\u002Fskills-web-frontend\u002Fskills\u002Fscroll-experience\u002FSKILL.md",[],[]]