[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72BCDFQFJJF8K9Y5VMQ3GPR":3,"skill-same:01M72BCDFQFJJF8K9Y5VMQ3GPR":71},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":13,"repositoryHtmlUrl":26,"repositoryHomepageUrl":6,"ownerHtmlUrl":27,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":28,"install":29,"resources":42},"01M72BCDFQFJJF8K9Y5VMQ3GPR","design-mirror",null,"Replicate the visual style of any website and apply it to your existing codebase. Use this skill whenever the user wants to match a site's design, mirror a UI aesthetic, make their app look like another site, or replicate a specific visual style from a URL. Trigger on phrases like 'make it look like', 'match the design of', 'copy the style from', 'I want my app to look like X', 'mirror this design', 'inspired by [url]', or any time the user points at a website and says they want their frontend to match it.","Sansar35\u002Fclaude-agent","Sansar35","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F145020281?v=4","01M724CQ2SCC86MGNSD87D0D4K","01M724CQ3965G9WJ3QXE3AJ5YY",1,"MIT","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fdesign-mirror\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: design-mirror\ndescription: \"Replicate the visual style of any website and apply it to your existing codebase. Use this skill whenever the user wants to match a site's design, mirror a UI aesthetic, make their app look like another site, or replicate a specific visual style from a URL. Trigger on phrases like 'make it look like', 'match the design of', 'copy the style from', 'I want my app to look like X', 'mirror this design', 'inspired by [url]', or any time the user points at a website and says they want their frontend to match it.\"\n---\n\n# Design Mirror\n\nCapture the visual design language of any website and apply it to your existing codebase — colors, typography, spacing, layout rhythm, component shapes, and overall aesthetic — all extracted live via Bright Data's Web Unlocker.\n\n## What This Skill Does\n\n1. **Capture** — Screenshot + HTML scrape the inspiration site via Bright Data\n2. **Extract** — Identify the full design system: colors, fonts, spacing scale, border radii, shadows, component patterns\n3. **Analyze** — Study the screenshot visually and the CSS structurally to understand the design language\n4. **Apply** — Translate that design system into the user's existing codebase (their framework, their components)\n\nYou are not copying content or functionality. You're understanding the *design language* — the palette, the type scale, the card shapes, the hover states, the overall aesthetic feel.\n\n> **Important:** This skill is for design inspiration and learning — extracting publicly visible design tokens (colors, fonts, spacing) to inform your own UI work. Always use it respectfully and in accordance with the terms of service of the sites you reference.\n\n## Setup\n\nRequires:\n- `BRIGHTDATA_API_KEY` — from [brightdata.com\u002Fcp](https:\u002F\u002Fbrightdata.com\u002Fcp) → Account Settings\n- `BRIGHTDATA_UNLOCKER_ZONE` — create an Unlocker zone at brightdata.com\u002Fcp\n\n```bash\nexport BRIGHTDATA_API_KEY=\"your-api-key\"\nexport BRIGHTDATA_UNLOCKER_ZONE=\"your-zone-name\"\n```\n\n## Step-by-Step Process\n\n### Step 1: Capture the Inspiration Site\n\nRun both captures in parallel — screenshot (for visual analysis) and HTML scrape (for CSS extraction):\n\n```bash\n# Screenshot (save as PNG)\nbash scripts\u002Fscreenshot.sh \"https:\u002F\u002Finspiration-site.com\" \"\u002Ftmp\u002Ftarget_screenshot.png\"\n\n# HTML + CSS scrape\nbash scripts\u002Fscrape_html.sh \"https:\u002F\u002Finspiration-site.com\" \"\u002Ftmp\u002Ftarget_page.html\"\n```\n\nRead `references\u002Fcapture-guide.md` for how to extract CSS from the raw HTML and handle common issues.\n\n### Step 2: Analyze the Design System\n\nAfter capturing, analyze both in parallel:\n\n**Visual analysis (screenshot):** Read the PNG image and identify:\n- Primary, secondary, accent colors\n- Background colors (page bg, card bg, surface hierarchy)\n- Typography: font families visible, size hierarchy (h1 → body → caption)\n- Layout: is it centered\u002Fconstrained-width? Grid? Sidebar?\n- Card\u002Fcontainer shapes: border radius size, shadow style (hard, soft, none, colored)\n- Button styles: pill, rectangle, ghost, gradient?\n- Navigation: sticky? Glass\u002Fblur effect? Dark or light?\n- Overall mood: dark, light, minimal, brutalist, glassmorphism, corporate, startup?\n\n**CSS analysis (HTML):** Extract from `\u003Cstyle>` tags and inline styles:\n- CSS custom properties (`:root { --color-... }`) — publicly declared design tokens\n- Font imports (`@import` from Google Fonts, etc.)\n- Tailwind config if present\n- Repeated class patterns that reveal the spacing scale\n\nRead `references\u002Fcss-extraction.md` for the extraction playbook.\n\n### Step 3: Build the Design Token Map\n\nProduce a structured design token map before touching any code:\n\n```\nDESIGN TOKENS FROM [site]\n==========================\nColors:\n  --bg-primary: #0a0a0f      (page background)\n  --bg-surface: #13131a      (card\u002Fpanel background)\n  --text-primary: #ffffff\n  --text-muted: #8888aa\n  --accent: #7c3aed          (primary CTA color)\n  --accent-hover: #6d28d9\n  --border: rgba(255,255,255,0.08)\n\nTypography:\n  --font-heading: 'Inter', sans-serif\n  --font-body: 'Inter', sans-serif\n  font-scale: 12\u002F14\u002F16\u002F20\u002F24\u002F32\u002F48px\n  heading-weight: 700\n  body-weight: 400\n\nSpacing:\n  base-unit: 8px\n  scale: 4\u002F8\u002F12\u002F16\u002F24\u002F32\u002F48\u002F64px\n\nBorders & Shadows:\n  --radius-sm: 6px\n  --radius-md: 12px\n  --radius-lg: 20px\n  --shadow: 0 4px 24px rgba(0,0,0,0.4)\n\nSpecial effects:\n  glass-blur: backdrop-filter: blur(16px)\n  gradient: linear-gradient(135deg, #7c3aed, #2563eb)\n```\n\nShow this token map to the user before proceeding. It's the foundation — if it's wrong, the output will be wrong.\n\n### Step 4: Understand the User's Codebase\n\nBefore writing any code, read the relevant parts of their codebase:\n\n- What framework? (React, Vue, Next.js, plain HTML?)\n- What styling approach? (Tailwind, CSS modules, styled-components, plain CSS?)\n- Where are global styles defined? (globals.css, theme.ts, tailwind.config.js?)\n- What components need restyling? (ask the user if unclear)\n\nDo not rewrite everything — surgical precision. Apply the design tokens to the existing structure.\n\n### Step 5: Apply the Design\n\nThe application strategy depends on their stack:\n\n**If Tailwind:** Update `tailwind.config.js` with the new color palette, font family, border radius scale. Add custom CSS variables for anything Tailwind can't handle natively.\n\n**If CSS\u002FCSS Modules:** Create or update a `:root` variables block in globals.css. Update component stylesheets to use the new variables.\n\n**If styled-components\u002FEmotion:** Update the theme object. Replace hardcoded color\u002Fspacing values with theme tokens.\n\n**In all cases:**\n- Apply colors, typography, and spacing globally first\n- Then tackle component-level details (buttons, cards, nav) one at a time\n- Preserve all existing functionality and layout structure — only visual properties change\n- Add any special effects (glass blur, gradients, animations) that define the inspiration site's character\n\nRead `references\u002Fapply-guide.md` for framework-specific implementation patterns.\n\n### Step 6: Show the Before\u002FAfter\n\nAfter applying changes, clearly present:\n- Which files were modified\n- The design token mapping (source → what you set it to)\n- Any special effects added\n- What the user should check visually (hover states, dark\u002Flight mode, mobile)\n\nIf the user has a dev server running, remind them to check it. Offer to iterate on specific components.\n\n## Key Principles\n\n**Design language, not markup.** The inspiration site's HTML structure and content are theirs. You're extracting the *design language* — how colors relate, how spacing flows, what gives the site its character — to apply as your own creative foundation.\n\n**Design tokens first, code second.** Rushing to apply colors before understanding the full system leads to inconsistent results. Always build the token map first.\n\n**Ask about scope.** \"Apply the design everywhere\" vs \"just make the homepage feel like it\" vs \"only restyle the navbar\" are very different jobs. Clarify before proceeding.\n\n**Don't break what works.** The user's components work. Only change visual properties. If you're uncertain whether a change might break layout, err on the side of caution and flag it.\n\n**Iterative is fine.** It's often better to get the foundation right (colors, type, spacing) and let the user review before tackling component-level details.\n\n## What to Do When...\n\n**The site uses a design system (Material, shadcn, etc.):** Identify it, tell the user, and ask if they want to adopt the same system or just extract the visual tokens.\n\n**The CSS is minified\u002Fobfuscated:** Fall back to the screenshot + visual analysis. You can still extract colors, spacing, and shapes from visual inspection.\n\n**The inspiration site is JS-rendered and the HTML scrape comes back mostly empty:** Note this to the user — the screenshot will still work for visual analysis, but CSS extraction will be limited. You can still infer most tokens visually.\n\n**The user's codebase uses a component library (shadcn, Chakra, MUI):** Apply the design by customizing the library's theme\u002Fconfig rather than overriding individual components.\n\n**Multiple pages need to match:** Use the homepage for overall design tokens, but offer to check inner pages (e.g., `\u002Fpricing`, `\u002Fdocs`) if the user wants to match a specific page's look.\n","# Design Mirror\n\nCapture the visual design language of any website and apply it to your existing codebase — colors, typography, spacing, layout rhythm, component shapes, and overall aesthetic — all extracted live via Bright Data's Web Unlocker.\n\n## What This Skill Does\n\n1. **Capture** — Screenshot + HTML scrape the inspiration site via Bright Data\n2. **Extract** — Identify the full design system: colors, fonts, spacing scale, border radii, shadows, component patterns\n3. **Analyze** — Study the screenshot visually and the CSS structurally to understand the design language\n4. **Apply** — Translate that design system into the user's existing codebase (their framework, their components)\n\nYou are not copying content or functionality. You're understanding the *design language* — the palette, the type scale, the card shapes, the hover states, the overall aesthetic feel.\n\n> **Important:** This skill is for design inspiration and learning — extracting publicly visible design tokens (colors, fonts, spacing) to inform your own UI work. Always use it respectfully and in accordance with the terms of service of the sites you reference.\n\n## Setup\n\nRequires:\n- `BRIGHTDATA_API_KEY` — from [brightdata.com\u002Fcp](https:\u002F\u002Fbrightdata.com\u002Fcp) → Account Settings\n- `BRIGHTDATA_UNLOCKER_ZONE` — create an Unlocker zone at brightdata.com\u002Fcp\n\n```bash\nexport BRIGHTDATA_API_KEY=\"your-api-key\"\nexport BRIGHTDATA_UNLOCKER_ZONE=\"your-zone-name\"\n```\n\n## Step-by-Step Process\n\n### Step 1: Capture the Inspiration Site\n\nRun both captures in parallel — screenshot (for visual analysis) and HTML scrape (for CSS extraction):\n\n```bash\n# Screenshot (save as PNG)\nbash scripts\u002Fscreenshot.sh \"https:\u002F\u002Finspiration-site.com\" \"\u002Ftmp\u002Ftarget_screenshot.png\"\n\n# HTML + CSS scrape\nbash scripts\u002Fscrape_html.sh \"https:\u002F\u002Finspiration-site.com\" \"\u002Ftmp\u002Ftarget_page.html\"\n```\n\nRead `references\u002Fcapture-guide.md` for how to extract CSS from the raw HTML and handle common issues.\n\n### Step 2: Analyze the Design System\n\nAfter capturing, analyze both in parallel:\n\n**Visual analysis (screenshot):** Read the PNG image and identify:\n- Primary, secondary, accent colors\n- Background colors (page bg, card bg, surface hierarchy)\n- Typography: font families visible, size hierarchy (h1 → body → caption)\n- Layout: is it centered\u002Fconstrained-width? Grid? Sidebar?\n- Card\u002Fcontainer shapes: border radius size, shadow style (hard, soft, none, colored)\n- Button styles: pill, rectangle, ghost, gradient?\n- Navigation: sticky? Glass\u002Fblur effect? Dark or light?\n- Overall mood: dark, light, minimal, brutalist, glassmorphism, corporate, startup?\n\n**CSS analysis (HTML):** Extract from `\u003Cstyle>` tags and inline styles:\n- CSS custom properties (`:root { --color-... }`) — publicly declared design tokens\n- Font imports (`@import` from Google Fonts, etc.)\n- Tailwind config if present\n- Repeated class patterns that reveal the spacing scale\n\nRead `references\u002Fcss-extraction.md` for the extraction playbook.\n\n### Step 3: Build the Design Token Map\n\nProduce a structured design token map before touching any code:\n\n```\nDESIGN TOKENS FROM [site]\n==========================\nColors:\n  --bg-primary: #0a0a0f      (page background)\n  --bg-surface: #13131a      (card\u002Fpanel background)\n  --text-primary: #ffffff\n  --text-muted: #8888aa\n  --accent: #7c3aed          (primary CTA color)\n  --accent-hover: #6d28d9\n  --border: rgba(255,255,255,0.08)\n\nTypography:\n  --font-heading: 'Inter', sans-serif\n  --font-body: 'Inter', sans-serif\n  font-scale: 12\u002F14\u002F16\u002F20\u002F24\u002F32\u002F48px\n  heading-weight: 700\n  body-weight: 400\n\nSpacing:\n  base-unit: 8px\n  scale: 4\u002F8\u002F12\u002F16\u002F24\u002F32\u002F48\u002F64px\n\nBorders & Shadows:\n  --radius-sm: 6px\n  --radius-md: 12px\n  --radius-lg: 20px\n  --shadow: 0 4px 24px rgba(0,0,0,0.4)\n\nSpecial effects:\n  glass-blur: backdrop-filter: blur(16px)\n  gradient: linear-gradient(135deg, #7c3aed, #2563eb)\n```\n\nShow this token map to the user before proceeding. It's the foundation — if it's wrong, the output will be wrong.\n\n### Step 4: Understand the User's Codebase\n\nBefore writing any code, read the relevant parts of their codebase:\n\n- What framework? (React, Vue, Next.js, plain HTML?)\n- What styling approach? (Tailwind, CSS modules, styled-components, plain CSS?)\n- Where are global styles defined? (globals.css, theme.ts, tailwind.config.js?)\n- What components need restyling? (ask the user if unclear)\n\nDo not rewrite everything — surgical precision. Apply the design tokens to the existing structure.\n\n### Step 5: Apply the Design\n\nThe application strategy depends on their stack:\n\n**If Tailwind:** Update `tailwind.config.js` with the new color palette, font family, border radius scale. Add custom CSS variables for anything Tailwind can't handle natively.\n\n**If CSS\u002FCSS Modules:** Create or update a `:root` variables block in globals.css. Update component stylesheets to use the new variables.\n\n**If styled-components\u002FEmotion:** Update the theme object. Replace hardcoded color\u002Fspacing values with theme tokens.\n\n**In all cases:**\n- Apply colors, typography, and spacing globally first\n- Then tackle component-level details (buttons, cards, nav) one at a time\n- Preserve all existing functionality and layout structure — only visual properties change\n- Add any special effects (glass blur, gradients, animations) that define the inspiration site's character\n\nRead `references\u002Fapply-guide.md` for framework-specific implementation patterns.\n\n### Step 6: Show the Before\u002FAfter\n\nAfter applying changes, clearly present:\n- Which files were modified\n- The design token mapping (source → what you set it to)\n- Any special effects added\n- What the user should check visually (hover states, dark\u002Flight mode, mobile)\n\nIf the user has a dev server running, remind them to check it. Offer to iterate on specific components.\n\n## Key Principles\n\n**Design language, not markup.** The inspiration site's HTML structure and content are theirs. You're extracting the *design language* — how colors relate, how spacing flows, what gives the site its character — to apply as your own creative foundation.\n\n**Design tokens first, code second.** Rushing to apply colors before understanding the full system leads to inconsistent results. Always build the token map first.\n\n**Ask about scope.** \"Apply the design everywhere\" vs \"just make the homepage feel like it\" vs \"only restyle the navbar\" are very different jobs. Clarify before proceeding.\n\n**Don't break what works.** The user's components work. Only change visual properties. If you're uncertain whether a change might break layout, err on the side of caution and flag it.\n\n**Iterative is fine.** It's often better to get the foundation right (colors, type, spacing) and let the user review before tackling component-level details.\n\n## What to Do When...\n\n**The site uses a design system (Material, shadcn, etc.):** Identify it, tell the user, and ask if they want to adopt the same system or just extract the visual tokens.\n\n**The CSS is minified\u002Fobfuscated:** Fall back to the screenshot + visual analysis. You can still extract colors, spacing, and shapes from visual inspection.\n\n**The inspiration site is JS-rendered and the HTML scrape comes back mostly empty:** Note this to the user — the screenshot will still work for visual analysis, but CSS extraction will be limited. You can still infer most tokens visually.\n\n**The user's codebase uses a component library (shadcn, Chakra, MUI):** Apply the design by customizing the library's theme\u002Fconfig rather than overriding individual components.\n\n**Multiple pages need to match:** Use the homepage for overall design tokens, but offer to check inner pages (e.g., `\u002Fpricing`, `\u002Fdocs`) if the user wants to match a specific page's look.\n",{"name":5,"description":7},"main","d046d088ce5a79a083f0abc0fe1b7ded73bc5b1f","claude-config\u002Fskills\u002Fdesign-mirror","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent","https:\u002F\u002Fgithub.com\u002FSansar35","2026-05-10 16:04:53",{"source":8,"skillName":5,"commands":30,"prompt":40,"zipAvailable":41},[31,34,37],{"tool":32,"command":33},"npx","npx skills add Sansar35\u002Fclaude-agent --skill design-mirror",{"tool":35,"command":36},"bunx","bunx skills add Sansar35\u002Fclaude-agent --skill design-mirror",{"tool":38,"command":39},"pnpm","pnpm dlx skills add Sansar35\u002Fclaude-agent --skill design-mirror","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fdesign-mirror\u002FSKILL.md",true,[43,49,53,57,61,67],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},".skill-source.json","REFERENCE","参考文档",803,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fdesign-mirror\u002F.skill-source.json",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"references\u002Fapply-guide.md",6526,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fdesign-mirror\u002Freferences\u002Fapply-guide.md",{"path":54,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":55,"sourceHtmlUrl":56},"references\u002Fcapture-guide.md",3020,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fdesign-mirror\u002Freferences\u002Fcapture-guide.md",{"path":58,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fcss-extraction.md",4682,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fdesign-mirror\u002Freferences\u002Fcss-extraction.md",{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":66},"scripts\u002Fscrape_html.sh","SCRIPT","脚本",999,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fdesign-mirror\u002Fscripts\u002Fscrape_html.sh",{"path":68,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":69,"sourceHtmlUrl":70},"scripts\u002Fscreenshot.sh",1030,"https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fdesign-mirror\u002Fscripts\u002Fscreenshot.sh",[72,79,86,93,100,108],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M72DVAN1JYEA302MT0C5MGD6","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M72DV8J5NBRRM4RPDFRV95N7","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\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M72DV5EMHW0BHP9BZ167MDCB","zinc-database","Access ZINC (230M+ purchasable compounds). Search by ZINC ID\u002FSMILES, similarity searches, 3D-ready structures for docking, analog discovery, for virtual screening and drug discovery.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzinc-database\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":18},"01M72DV216QY0E693ZPEVQ0DBS","zarr-python","Chunked N-D arrays for cloud storage. Compressed arrays, parallel I\u002FO, S3\u002FGCS integration, NumPy\u002FDask\u002FXarray compatible, for large-scale scientific computing pipelines.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzarr-python\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":18},"01M72DTXQREMCRKA8NHCVKHN4W","zapier-workflows","Manage and trigger pre-built Zapier workflows and MCP tool orchestration. Use when user mentions workflows, Zaps, automations, daily digest, research, search, lead tracking, expenses, or asks to \"run\" any process. Also handles Perplexity-based research and Google Sheets data tracking.","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-workflows\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":18},"01M72DTT17TBSJ0Y8J2XZ4C9TZ","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FSansar35\u002Fclaude-agent\u002Fblob\u002Fmain\u002Fclaude-config\u002Fskills\u002Fzapier-make-patterns\u002FSKILL.md",[],[]]